-current host, 10.1 client loops

Poul-Henning Kamp phk at phk.freebsd.dk
Tue Mar 15 15:16:43 UTC 2016


I'm seing bhyve go into some kind of endless loop while trying to
compile the gcc port on 10.1 as guest.

In one case CTRL-T on the console kept working, but showed an rm(1)
process raking up CPU time.

Are there known bogon in current/bhyve or using 10.1-R/i386 as a guest
I have not spotted ?

How does one debug stuff like this ?

Poul-Henning

Bhyve started with:

        sh /usr/share/examples/bhyve/vmrun.sh \
                -m 1G \
                -t ${VMN} \
                -d ${P}.root.dd \
                -d ${P}.swap.dd \
                -d ${P}.tami_install.dd \
                -d ${P}.tami_git.dd \
                vm${VMU} || true

Host:
	11.0-CURRENT #4 r296808: Sun Mar 13 22:39:59 UTC 2016

	CPU: AMD Athlon(tm) II X3 455 Processor (3311.18-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 = 16573935616 (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
	ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20150818/tbfadt-649)


Guest:
	10.1-RELEASE i386




-- 
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.


More information about the freebsd-virtualization mailing list