Re: (vm-)bhyve stopped working recently on 13.2

On Fri, Jan 12, 2024 at 10:54 PM Michael Gmelin wrote:
> What are you running inside bhyve (OS and version)? Could you maybe share vm-bhyve‘s config file?

I was running Debian 11 and since it stopped working I tried Debian 12.

debug="yes"
#loader="bhyveload"
loader="uefi"
uefi_vars="yes"
graphics="yes"
graphics_res="1920x1080"
graphics_listen="127.0.0.1"
graphics_wait="no"
graphics_vga="no"
cpu="4"
memory="20G"
network0_type="virtio-net"
network0_switch="public"
#disk0_type="virtio-blk"
disk0_type="nvme"
disk0_name="disk0.img"
sound="yes"
sound_play="/dev/dsp"
passthru0="6/0/0"
xhci_mouse="yes"
uuid="XXX"
network0_mac="XXX"

Debian 12 log:

Jan 12 22:33:49: initialising
Jan 12 22:33:49:  [loader: uefi]
Jan 12 22:33:49:  [cpu: 4]
Jan 12 22:33:49:  [memory: 20G]
Jan 12 22:33:49:  [hostbridge: standard]
Jan 12 22:33:49:  [com ports: com1]
Jan 12 22:33:49:  [uuid: XXX]
Jan 12 22:33:49:  [debug mode: yes]
Jan 12 22:33:49:  [primary disk: disk0.img]
Jan 12 22:33:49:  [primary disk dev: file]
Jan 12 22:33:49: initialising network device tap0
Jan 12 22:33:49: adding tap0 -> vm-public (public addm)
Jan 12 22:33:49: bring up tap0 -> vm-public (public addm)
Jan 12 22:33:49: dynamically allocated port 5900 for vnc connections
Jan 12 22:33:49: booting
Jan 12 22:33:49:  [bhyve options: -c 4 -m 20G -Hwl
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/ztuff/vm/bhyve/debian12/uefi-vars.fd
-U 273d0407-b18d-11ee-ba62-60a44c60c172 -u -S]
Jan 12 22:33:49:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,nvme,/ztuff/vm/bhyve/debian12/disk0.img -s
5:0,virtio-net,tap0,mac=58:9c:fc:06:d3:8f -s 6:0,passthru,6/0/0 -s
7:0,fbuf,tcp=127.0.0.1:5900,w=1920,h=1080,vga=no -s 8:0,xhci,tablet -s
9:0,hda,play=/dev/dsp]
Jan 12 22:33:49:  [bhyve console: -l com1,/dev/nmdm-debian12.1A]
Jan 12 22:33:49:  [bhyve iso device: -s
3:0,ahci-cd,/ztuff/vm/bhyve/.iso/debian-12.4.0-amd64-netinst.iso,ro]
Jan 12 22:33:49: starting bhyve (run 1)
Jan 12 22:33:56: bhyve exited with status 4
Jan 12 22:33:56: destroying network device tap0
Jan 12 22:33:56: stopped


Debian11 log:

Jan 12 21:46:01: booting
Jan 12 21:46:01:  [bhyve options: -c 4 -m 20G -Hwl
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd,/ztuff/vm/bhyve/debian11/uefi-vars.fd
-U XXX -u -S]
Jan 12 21:46:01:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,nvme,/ztuff/vm/bhyve/debian11/disk0.img -s
5:0,virtio-net,tap0,mac=XXX -s 6:0,passthru,6/0/0 -s
7:0,fbuf,tcp=127.0.0.1:5900,w=1920,h=1080]
Jan 12 21:46:01:  [bhyve console: -l com1,/dev/nmdm-debian11.1A]
Jan 12 21:46:01: starting bhyve (run 1)
Jan 12 21:46:10: bhyve exited with status 134
Jan 12 21:46:10: destroying network device tap0
Jan 12 21:46:10: stopped


What I found regarding exit status 134 was forum post that hardware is
too old lol.. but it was working week ago and I am older :-) `man
bhyve` states that error code 4 means "exited due to an error" and
that tells a lot :-) Enabling debug does not help here the log is the
same.

My last reply went to the questions list only, so as this one goes
also to the virtualisation I would like to humbly express an idea of
moving vh-bhyve under FreeeBSD wings and make it a default frontend
for bhyve as it is amazingly simple and does the job :-)

Thanks Michael :-)
Tomek

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info