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

Nils Beyer <n...@renzel.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |n...@renzel.net

--- Comment #8 from Nils Beyer <n...@renzel.net> ---
Same behaviour here on a Ryzen 1700 and "FreeBSD 12.0-CURRENT #0
334829e6c(drm-next)-dirty".

Setting vCPU count greater than 1 leads to random lock-ups of the Windows 10
VM. Two, sometimes three of the vCPUs are creating 100% load on the host
system. Keyboard input via VNC doesn't work at all.

"bhyve" itself writes:
-------------------------------------------------------------------------------
fbuf frame buffer base: 0xa43200000 [sz 16777216]
rdmsr to register 0xc0010114 on vcpu 0
rdmsr to register 0xc0010114 on vcpu 1
wrmsr to register 0x10(0) on vcpu 1
rdmsr to register 0xc0010114 on vcpu 2
wrmsr to register 0x10(0) on vcpu 2
rdmsr to register 0xc0010114 on vcpu 3
wrmsr to register 0x10(0) on vcpu 3
wrmsr to register 0x10(0xcc75fcd2078) on vcpu 3
wrmsr to register 0x10(0xcc75fcd2078) on vcpu 0
wrmsr to register 0x10(0xcc75fcd2078) on vcpu 1
wrmsr to register 0x10(0xcc75fcd2078) on vcpu 2
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
atkbd data buffer full
-------------------------------------------------------------------------------

sysctls:
-------------------------------------------------------------------------------
#sysctl hw.vmm
hw.vmm.npt.pmap_flags: 507
hw.vmm.svm.num_asids: 32768
hw.vmm.svm.disable_npf_assist: 0
hw.vmm.svm.features: 113919
hw.vmm.svm.vmcb_clean: 959
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: 0
hw.vmm.vmx.cap.monitor_trap: 0
hw.vmm.vmx.cap.unrestricted_guest: 0
hw.vmm.vmx.cap.pause_exit: 0
hw.vmm.vmx.cap.halt_exit: 0
hw.vmm.vmx.initialized: 0
hw.vmm.vmx.cr4_zeros_mask: 0
hw.vmm.vmx.cr4_ones_mask: 0
hw.vmm.vmx.cr0_zeros_mask: 0
hw.vmm.vmx.cr0_ones_mask: 0
hw.vmm.ept.pmap_flags: 0
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: 136
hw.vmm.topology.cpuid_leaf_b: 1
hw.vmm.topology.cores_per_package: 4
hw.vmm.topology.threads_per_core: 1
hw.vmm.create: beavis
hw.vmm.destroy: beavis
hw.vmm.trace_guest_exceptions: 0
hw.vmm.ipinum: 251
hw.vmm.halt_detection: 1
-------------------------------------------------------------------------------

started "bhyve" with:
-------------------------------------------------------------------------------
bhyve -c 4 -m 8G \                                                              
        -w -H -A -P \                                                           
        -s 0,amd_hostbridge \                                                   
        -s 1,lpc \                                                              
        -s 2,ahci-cd,/mnt/ryzen/iso/Windows10-PRO.de.iso \                      
        -s 3,ahci-hd,/mnt/ryzen/vms/${NAME}/lun0.img \                          
        -s 9,e1000,tap${ID} \                                                   
        -s 29,fbuf,tcp=0.0.0.0:5901,w=1024,h=768,wait \                         
        -s 30,xhci,tablet \                                                     
        -l com1,/dev/nmdm0A \                                                   
        -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \               
        ${NAME}                                                      
-------------------------------------------------------------------------------

looking at the "ktrace -p" file, I see lots of:
-------------------------------------------------------------------------------
[...]
  3826 vcpu 0   CALL  ioctl(0x3,0xc0907601,0x7fffddbebe30)
  3826 vcpu 3   RET   ioctl 0
  3826 vcpu 0   RET   ioctl 0
  3826 vcpu 0   CALL  ioctl(0x3,0xc0907601,0x7fffddbebe30)
  3826 vcpu 3   CALL  ioctl(0x3,0xc0907601,0x7fffdd3e7e30)
  3826 vcpu 2   CALL  ioctl(0x3,0xc0907601,0x7fffdd5e8e30)
  3826 vcpu 3   RET   ioctl 0
  3826 vcpu 3   CALL  ioctl(0x3,0xc0907601,0x7fffdd3e7e30)
  3826 vcpu 2   RET   ioctl 0
  3826 vcpu 3   RET   ioctl 0
  3826 vcpu 3   CALL  ioctl(0x3,0xc0907601,0x7fffdd3e7e30)
  3826 vcpu 0   RET   ioctl 0
  3826 vcpu 3   RET   ioctl 0
  3826 vcpu 3   CALL  ioctl(0x3,0xc0907601,0x7fffdd3e7e30)
  3826 vcpu 0   CALL  ioctl(0x3,0xc0907601,0x7fffddbebe30)
  3826 vcpu 3   RET   ioctl 0
  3826 vcpu 0   RET   ioctl 0
  3826 vcpu 2   CALL  ioctl(0x3,0xc0907601,0x7fffdd5e8e30)
  3826 vcpu 2   RET   ioctl 0
  3826 vcpu 3   CALL  ioctl(0x3,0xc0907601,0x7fffdd3e7e30)
  3826 vcpu 3   RET   ioctl 0
  3826 vcpu 0   CALL  ioctl(0x3,0xc0907601,0x7fffddbebe30)
  3826 vcpu 2   CALL  ioctl(0x3,0xc0907601,0x7fffdd5e8e30)
  3826 vcpu 2   RET   ioctl 0
[...]
-------------------------------------------------------------------------------

Anything I can do to help debugging?

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
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"

Reply via email to