[Bug 246168] Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246168

--- Comment #11 from John Hartley <drum at graphica.com.au> ---
(In reply to Peter Grehan from comment #10)

Hi Peter,

you have eagle eyes.

Your suggestion worked and I now have Layer 3 - FreeBSD UEFI guest doing an
install.


I also tried to see if disabling X2APIC via QEMU fixed the problem via:

<cpu mode='host-model' check='partial'>
  <feature policy='disable' name='x2apic'/>
</cpu>

This did not work, but it did turn off the feature correct in Layer 1 - Guest /
Host.

Here is output from sysctl on Layer 1 - FreeBSD Guest Host

<<LAYER 1 - SYSCTL>>
# sysctl hw.vmm
hw.vmm.amdvi.domain_id: 0
hw.vmm.amdvi.disable_io_fault: 0
hw.vmm.amdvi.ptp_level: 4
hw.vmm.amdvi.host_ptp: 1
hw.vmm.amdvi.enable: 0
hw.vmm.amdvi.count: 0
hw.vmm.npt.pmap_flags: 0
hw.vmm.svm.num_asids: 0
hw.vmm.svm.disable_npf_assist: 0
hw.vmm.svm.features: 4294967295
hw.vmm.svm.vmcb_clean: 1023
hw.vmm.vmx.l1d_flush_sw: 0
hw.vmm.vmx.l1d_flush: 0
hw.vmm.vmx.vpid_alloc_failed: 0
hw.vmm.vmx.posted_interrupt_vector: -1
hw.vmm.vmx.cap.posted_interrupts: 0
hw.vmm.vmx.cap.virtual_interrupt_delivery: 0
hw.vmm.vmx.cap.invpcid: 1
hw.vmm.vmx.cap.monitor_trap: 1
hw.vmm.vmx.cap.unrestricted_guest: 1
hw.vmm.vmx.cap.pause_exit: 1
hw.vmm.vmx.cap.halt_exit: 1
hw.vmm.vmx.initialized: 1
hw.vmm.vmx.cr4_zeros_mask: 18446744073705934848
hw.vmm.vmx.cr4_ones_mask: 8192
hw.vmm.vmx.cr0_zeros_mask: 18446744071025197056
hw.vmm.vmx.cr0_ones_mask: 32
hw.vmm.vmx.no_flush_rsb: 0
hw.vmm.ept.pmap_flags: 1531
hw.vmm.vrtc.flag_broken_time: 1
hw.vmm.ppt.devices: 0
hw.vmm.iommu.enable: 1
hw.vmm.iommu.initialized: 0
hw.vmm.bhyve_xcpuids: 0
hw.vmm.topology.cpuid_leaf_b: 1
hw.vmm.create: beavis
hw.vmm.destroy: beavis
hw.vmm.trace_guest_exceptions: 0
hw.vmm.ipinum: 251
hw.vmm.halt_detection: 1
<<END LAYER 1 - SYSCTL>>


So have work around.

Do think believe this needs fix within FreeBSD bhyve or is issue with QEMU /
KVM ?

NOTE: I also tested with FreeBSD 13 CURRENT and this had same problem.

Thanks again for help on this.

Cheers,


John Hartley

-- 
You are receiving this mail because:
You are the assignee for the bug.