Date: Mon, 6 Oct 2025 20:10:59 +0200 From: Xavier Humbert <xavier@xavierhumbert.net> To: infoomatic <infoomatic@gmx.at>, virtualization@freebsd.org Subject: [SOLVED]Re: VM bhyve suddenly stopped working Message-ID: <ad15477a-bf4c-440d-b0ca-1dd044ffbc99@xavierhumbert.net> In-Reply-To: <642e2ddf-8909-42be-bf3c-42eddbb98e95@xavierhumbert.net> References: <fceb6a37-1999-43ce-9f55-555f7d1ed50f@xavierhumbert.net> <0af77cf0-1dbe-4efa-8f65-4e6cbeaba9ff@gmx.at> <642e2ddf-8909-42be-bf3c-42eddbb98e95@xavierhumbert.net>
index | next in thread | previous in thread | raw e-mail
Le 04/10/2025 20:20, Xavier Humbert a écrit : > Le 04/10/2025 19:00, infoomatic a écrit : >> 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 >>> >> > Hi Infoomatic, > > It worked fine until yesterday with this config. I fixed the typo, > with no success > > Regards, > > Xavier > Hi, Th issue was that sysutils/grub2-bhyve was broken for some unknown reason. Reinstalling it fixed the problem. Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.frhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ad15477a-bf4c-440d-b0ca-1dd044ffbc99>