Date: Thu, 10 Sep 2020 17:30:36 +1000 From: Peter Grehan <grehan@freebsd.org> To: Pete Wright <pete@nomadlogic.org> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Nested Virtualization Under KVM Hypervisor Message-ID: <adbfa9f8-7e8b-edb2-e547-587e9187cb95@freebsd.org> In-Reply-To: <5e62480f-14cb-5963-f753-8562aab381e3@nomadlogic.org> References: <e819886a-82d1-7fad-c341-b3e2bba50aed@nomadlogic.org> <5eacd0a5-89bd-cc98-6c5a-d5490e33b100@freebsd.org> <5e62480f-14cb-5963-f753-8562aab381e3@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Pete, > Sep 10 03:25:01 bells kernel: vmx_init: processor does not support=20 > desired basic capabilities ^^^ This is what's causing the issues, and is covered in the first=20 bug report I mentioned=20 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203994) Would you be able to dump the MSRs for the FreeBSD guest as mentioned=20 in the bug report ? > I also received this input from the ISP, they are running this kernel: > =C2=A04.15.0-47-generic #50~16.04.1-Ubuntu SMP I'm now wondering if this is too old a kernel :( > reading through that ticket i set this in loader.conf: > hw.vmm.vmx.use_apic_vid=3D0 >=20 > and verified via sysctl: > $ sysctl hw.vmm.vmx.cap.virtual_interrupt_delivery > hw.vmm.vmx.cap.virtual_interrupt_delivery: 0 > $ >=20 > since you mention this is a possible bug with KVM is there some useful=20 > information i can relay to my ISP (they are a BSD friendly vendor) that= =20 > they can try on their end as a workaround, or perhaps something they=20 > ping the linux/kvm community about? As above, this isn't the issue for this particular case: it manifests=20 as a hypervisor guest immediately exiting when started. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?adbfa9f8-7e8b-edb2-e547-587e9187cb95>