-current host, 10.1 client loops

[Poul-Henning Kamp]

--------
In message <570B3604.8020500 at freebsd.org>, Peter Grehan writes:


Ok, host is:
	11.0-CURRENT #0 r297514M: Sun Apr  3 13:11:49 UTC 2016

	CPU: AMD Athlon(tm) II X3 455 Processor (3311.19-MHz K8-class CPU)
	  Origin="AuthenticAMD"  Id=0x100f53  Family=0x10  Model=0x5  Stepping=3
	  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
	  Features2=0x802009<SSE3,MON,CX16,POPCNT>
	  AMD Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!>
	  AMD Features2=0x837ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,NodeId>
	  SVM: NP,NRIP,NAsids=64
	  TSC: P-state invariant
	real memory  = 17179869184 (16384 MB)
	avail memory = 16573874176 (15806 MB)
	Event timer "LAPIC" quality 400
	ACPI APIC Table: <090712 APIC1033>
	FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs
	FreeBSD/SMP: 1 package(s) x 3 core(s)
	 cpu0 (BSP): APIC ID:  0
	 cpu1 (AP): APIC ID:  1
	 cpu2 (AP): APIC ID:  2


Guest is (still) 10.1-R

Running with:

	sed 's/virtio-blk/ahci-hd/' \
	    /usr/share/examples/bhyve/vmrun.sh \
	    > vmrun_ada.sh

        sh vmrun_ada.sh \
                -m 1G \
                -c 3 \
                -t ${VMN} \
                -d ${P}.root.dd \
                -d ${P}.swap.dd \
                -d ${P}.tami_install.dd \
                vm${VMU} || true

Hanging now, trying to build some port.

I may be able to find out which exact port later, but for now I'll
leave it hanging, in case you have any ideas for pulling out more info.

CTRL-T in the console works

	load: 10.99  cmd: sh 43413 [running] 22940.67r 0.00u 0.00s 100% 228k
	load: 10.99  cmd: sh 43413 [running] 22940.88r 0.00u 0.00s 100% 228k
	load: 10.99  cmd: sh 43413 [running] 22941.08r 0.00u 0.00s 100% 228k
	load: 10.99  cmd: sh 43413 [running] 22941.28r 0.00u 0.00s 100% 228k
	load: 10.99  cmd: sh 43413 [running] 22941.49r 0.00u 0.00s 100% 228k
	^Z
	^Z
	load: 10.29  cmd: sh 43413 [running] 22957.30r 0.00u 0.00s 100% 228k
	load: 10.29  cmd: sh 43413 [running] 22957.49r 0.00u 0.00s 100% 228k
	load: 10.29  cmd: sh 43413 [running] 22957.66r 0.00u 0.00s 100% 228k
	load: 10.29  cmd: sh 43413 [running] 22957.83r 0.00u 0.00s 100% 228k
	^Z


	Suspended 
	root@:~ # 
	root@:~ # 
	root@:~ # 
	root@:~ # ps -axlwH
	load: 10.53  cmd: csh 669 [runnable] 29867.68r 0.02u 107.86s 0% 2392k
	load: 10.53  cmd: csh 669 [runnable] 29868.27r 0.02u 107.86s 0% 2392k
	load: 10.53  cmd: csh 669 [runnable] 29868.52r 0.02u 107.86s 0% 2392k
	[... 3 hours later still the same ...]


>  Also, if the guest looks like it hangs, you can extract the RIPs with
>   bhyvectl --get-rip --cpu=0 --vm=<vmname>
>   bhyvectl --get-rip --cpu=1 --vm=<vmname>
>
>  This might give a hint as to where the guest is spinning.

	==> _cpu_0 <==
	rip[0]          0x00000000c0b14780
	rip[0]          0x00000000c0b14782
	rip[0]          0x00000000c0b14780
	rip[0]          0x00000000c0b14780
	rip[0]          0x00000000c0b14780
	rip[0]          0x00000000c0b14780

	==> _cpu_1 <==
	rip[1]          0x00000000c0b14780
	rip[1]          0x00000000c0b14782
	rip[1]          0x00000000c0b14780
	rip[1]          0x00000000c0b14780
	rip[1]          0x00000000c0b14780
	rip[1]          0x00000000c0b14780

	==> _cpu_2 <==
	rip[2]          0x00000000c100feb0
	rip[2]          0x00000000c100feb0
	rip[2]          0x00000000c100feb0
	rip[2]          0x00000000c100feb0
	rip[2]          0x00000000c100feb0
	rip[2]          0x00000000c100feb2

Any ideas ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.