Re: VM bhyve suddenly stopped working

Hi,

I just noticed, you have "disk1_dev" set twice, but not "disk2_dev", 
maybe this is the issue?

Regards,
Robert


On 04.10.25 08:49, Xavier Humbert wrote:
> Hi,
> 
> My Byhve VM suddenly won't boot. I use vm-bhyve
> 
> The config :
> 
> loader="grub"
> grub_run_partition="2"
> cpu=2
> memory=4096M
> network0_type="virtio-net"
> network0_switch="public"
> disk0_type="virtio-blk"
> disk0_name="disk0.img"
> uuid="f878c150-de67-11ec-8816-d05099c11279"
> network0_mac="58:9c:fc:0d:84:62"
> disk1_name="disk1.img"
> disk1_type="virtio-blk"
> disk1_dev="file"
> disk2_name="disk2.img"
> disk2_type="virtio-blk"
> disk1_dev="file"
> bhyve_options="-wA"
> 
> The log :
> 
> Oct 04 08:43:27: initialising
> Oct 04 08:43:27:  [loader: grub]
> Oct 04 08:43:27:  [cpu: 2]
> Oct 04 08:43:27:  [memory: 4096M]
> Oct 04 08:43:27:  [hostbridge: standard]
> Oct 04 08:43:27:  [com ports: com1]
> Oct 04 08:43:27:  [uuid: f878c150-de67-11ec-8816-d05099c11279]
> Oct 04 08:43:27:  [debug mode: no]
> Oct 04 08:43:27:  [primary disk: disk0.img]
> Oct 04 08:43:27:  [primary disk dev: file]
> Oct 04 08:43:27: initialising network device tap0
> Oct 04 08:43:27: adding tap0 -> vm-public (public addm)
> Oct 04 08:43:27: bring up tap0 -> vm-public (public addm)
> Oct 04 08:43:28: booting
> Oct 04 08:43:28: create file /vms/valinor/device.map
> Oct 04 08:43:28:  -> (hd0) /vms/valinor/disk0.img
> Oct 04 08:43:28:  -> (hd1) /vms/valinor/disk1.img
> Oct 04 08:43:28:  -> (hd2) /vms/valinor/disk2.img
> Oct 04 08:43:28: /usr/local/sbin/grub-bhyve -c /dev/nmdm-valinor.1A -m / 
> vms/valinor/device.map -M 4096M -r hd0,2 valinor
> Oct 04 08:43:28: fatal; loader returned error 1
> Oct 04 08:43:28: destroying network device tap0
> Oct 04 08:43:28: stopped
> 
> Any idea how to debug this ?
> 
> TIA,
> 
> Regards,
> 
> Xavier
>