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 ?
I also received this input from the ISP, they are running this kernel:
4.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=0
and verified via sysctl:
$ sysctl hw.vmm.vmx.cap.virtual_interrupt_delivery
hw.vmm.vmx.cap.virtual_interrupt_delivery: 0
$
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.
later,
Peter.
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
