[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

[bugzilla-noreply at freebsd.org]

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

--- Comment #20 from mr.xanto at gmail.com ---
(In reply to Konstantin Belousov from comment #19)
I mean, that when bhyve process is aborted, bhyvectl return "VM:<name> is not
created.

I've wrote stupid script for get bhyvectl message before start and after close
vm:

#!/bin/sh

echo
"============================================================================="
>> /mnt/Data/vm/win10/get.log
date +"%Y.%m.%d - %X" >> /mnt/Data/vm/win10/get.log
bhyvectl --vm=win10 --get-all >> /mnt/Data/vm/win10/get.log
echo
"============================================================================="
>> /mnt/Data/vm/win10/get.log
vm start win10
sleep 1

while pgrep bhyve >/dev/null;
do
    date +"%Y.%m.%d - %X" >> /mnt/Data/vm/win10/get.log
    bhyvectl --vm=win10 --get-all >> /mnt/Data/vm/win10/get.log
    echo
"============================================================================="
>> /mnt/Data/vm/win10/get.log
    sleep 0.1
done
    sleep 1
    date +"%Y.%m.%d - %X" >> /mnt/Data/vm/win10/get.log
    bhyvectl --vm=win10 --get-all >> /mnt/Data/vm/win10/get.log
    echo
"============================================================================="
>> /mnt/Data/vm/win10/get.log

Result of work this script I've placed at https://yadi.sk/d/Xn3AFSoW_wDdRA

bhyve log:
Unhandled ps2 keyboard command 0x02
Unhandled ps2 keyboard command 0x02
Assertion failed: (pi->pi_bar[baridx].type == PCIBAR_IO), function
passthru_write, file /usr/src/usr.sbin/bhyve/pci_passthru.c, line 916.

bhyve options:
Nov 07 14:32:42: booting
Nov 07 14:32:42:  [bhyve options: -c 1 -m 3G -Hwl
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U
00dad61d-0d2e-11eb-936d-70f3951447ea -S]
Nov 07 14:32:42:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,ahci,hd:/mnt/Data/vm/win10/disk0.img -s
5:0,virtio-net,tap0,mac=58:9c:fc:01:00:a8 -s 6:0,passthru,1/0
/0 -s 6:1,passthru,1/0/1]
Nov 07 14:32:42:  [bhyve console: -l com1,stdio]
Nov 07 14:32:42:  [bhyve iso device: -s
3:0,ahci-cd,/mnt/Data/vm/.config/null.iso]
Nov 07 14:32:42: starting bhyve (run 1)
Nov 07 14:33:40: bhyve exited with status 0
Nov 07 14:33:40: restarting
Nov 07 14:33:40:  [bhyve options: -c 1 -m 3G -Hwl
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U
00dad61d-0d2e-11eb-936d-70f3951447ea -S]
Nov 07 14:33:40:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,ahci,hd:/mnt/Data/vm/win10/disk0.img -s
5:0,virtio-net,tap0,mac=58:9c:fc:01:00:a8 -s 6:0,passthru,1/0
/0 -s 6:1,passthru,1/0/1]
Nov 07 14:33:40:  [bhyve console: -l com1,stdio]
Nov 07 14:33:40:  [bhyve iso device: -s
3:0,ahci-cd,/mnt/Data/vm/.config/null.iso]
Nov 07 14:33:40: starting bhyve (run 2)
Nov 07 14:34:15: bhyve exited with status 134

Some explanations: first start of Windows guest after crash will be in
diagnostic mode, and because I don't have
console access to VM (as I understand, GPU pass through not compatible with
"fbuf" options), then I've reset VM
and when VM load, bhyve exited.

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