Date: Tue, 19 Jun 2018 09:45:12 -0700 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-virtualization@freebsd.org Subject: Re: bhyve panic on netcup root server (vmx enabled) Message-ID: <17d9d5b9-8928-866e-ba0f-fb2ba9c681e6@FreeBSD.org> In-Reply-To: <f9a824d4-7b20-ef0d-80b7-384f0187d3da@FreeBSD.org> References: <46c8809d-89d3-dbe5-bfd7-7add64ac7e84@bader-muenchen.de> <f9a824d4-7b20-ef0d-80b7-384f0187d3da@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/15/18 11:22 AM, John Baldwin wrote: > On 6/15/18 4:44 AM, richard bader wrote: >> Hi, >> >> i try to install a virtual host on a virtual root-server (netcup.de) >> >> I've enabled the VMX-Options on the root-server. >> >> I've followed the instruction from >> https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html >> >> on the root-server i've installed FreeBSD-11.1. >> >> but wenn starting the guest it panics: >> >> sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 5Gb -w -t tap0 -d >> guest.img -i -I FreeBSD-11.1-RELEASE-anly.iso test1 >> >> >> /boot/kernel/kernel text=0x14972f8 data=0x1384c0+0x4c15e8 >> syms=[0x8+0x15e8b0+0x8+0x178422] >> Booting... >> Copyright (c) 1992-2017 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017 >> root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on >> LLVM 4.0.0) >> VT(vga): text 80x25 >> CPU: Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz (2294.60-MHz K8-class CPU) >> Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4 >> Features=0x1f83fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,SS,HTT> >> Features2=0xfeda3203<SSE3,PCLMULQDQ,SSSE3,FMA,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> >> AMD Features=0x24100800<SYSCALL,NX,Page1GB,LM> >> AMD Features2=0x121<LAHF,ABM,Prefetch> >> Structured Extended >> Features=0x10010b38<BMI1,HLE,AVX2,BMI2,ERMS,RTM,AVX512F,AVX512CD> >> XSAVE Features=0x1<XSAVEOPT> >> Hypervisor: Origin = "bhyve bhyve " >> real memory = 6442450944 (6144 MB) >> avail memory = 5131386880 (4893 MB) >> Event timer "LAPIC" quality 600 >> ACPI APIC Table: <BHYVE BVMADT > >> panic: APIC: CPU with APIC ID 224 is not enabled >> cpuid = 0 >> KDB: stack backtrace: >> #0 0xffffffff80aada97 at kdb_backtrace+0x67 >> #1 0xffffffff80a6bb76 at vpanic+0x186 >> #2 0xffffffff80a6b9e3 at panic+0x43 >> #3 0xffffffff8101dc11 at madt_set_ids+0x91 >> #4 0xffffffff80a07c9c at mi_startup+0x9c >> #5 0xffffffff8030202c at btext+0x2c >> Uptime: 1s >> >> Any ideas to get it working or is it just not possible. > > This indicates a bug in the ACPI tables generated by bhyve to give to the > guest. Try setting the environment variable 'BHYVE_ACPI_KEEPTMPS=yes' > when running vmrun.sh and then look in /tmp for files named 'bhyve.*'. > If you can provide them via a URL or some such, I'm mostly interested in > the MADT table. I looked at the raw AML richard provided and it looked fine. :-/ In particular, the MADT only lists a single CPU with APIC ID of 0, so I'm not sure why it thinks there is a CPU with an APIC ID of 224. Can you do a 'boot -v' so I can see more messages from the MADT code while it is running? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17d9d5b9-8928-866e-ba0f-fb2ba9c681e6>