Date: Thu, 10 Sep 2020 07:46:31 -0700 From: Pete Wright <pete@nomadlogic.org> To: Peter Grehan <grehan@freebsd.org> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Nested Virtualization Under KVM Hypervisor Message-ID: <b1e2350c-8036-68ff-c0eb-2909face750e@nomadlogic.org> In-Reply-To: <adbfa9f8-7e8b-edb2-e547-587e9187cb95@freebsd.org> References: <e819886a-82d1-7fad-c341-b3e2bba50aed@nomadlogic.org> <5eacd0a5-89bd-cc98-6c5a-d5490e33b100@freebsd.org> <5e62480f-14cb-5963-f753-8562aab381e3@nomadlogic.org> <adbfa9f8-7e8b-edb2-e547-587e9187cb95@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
u On 9/10/20 12:30 AM, Peter Grehan wrote: > Hi Pete, > >> Sep 10 03:25:01 bells kernel: vmx_init: processor does not support >> desired basic capabilities > > ^^^ This is what's causing the issues, and is covered in the first > bug report I mentioned > (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203994) > > Would you be able to dump the MSRs for the FreeBSD guest as mentioned > in the bug report ? > Ah I see - once I realized we had a newer kernel I didn't focus too much on the first bug - here's the MSR's MSR 0x480: 0x00981000 0x11e57ed0 MSR 0x482: 0xfff9fffe 0x0401e172 MSR 0x48b: 0x000003fb 0x00000000 MSR 0x48c: 0x00000f01 0x04114040 >> since you mention this is a possible bug with KVM is there some >> useful information i can relay to my ISP (they are a BSD friendly >> vendor) that they can try on their end as a workaround, or perhaps >> something they ping the linux/kvm community about? > > As above, this isn't the issue for this particular case: it manifests > as a hypervisor guest immediately exiting when started. > ok perfect this aligns with what i'm seeing as well when i run bhyvload or bhyvectl and it just bails with a "vm_create: Device not configured" error. Cheers, -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1e2350c-8036-68ff-c0eb-2909face750e>