Date: Tue, 24 Oct 2023 09:51:20 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 274689] 15-CURRENT does not load with bhyveload on 12-STABLE: ERROR: cannot open /boot/lua/loader.lua: no such file or directory. Message-ID: <bug-274689-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274689 Bug ID: 274689 Summary: 15-CURRENT does not load with bhyveload on 12-STABLE: ERROR: cannot open /boot/lua/loader.lua: no such file or directory. Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: michaelo@FreeBSD.org Hypervisor runs on: > FreeBSD deblndw013x.ad001.siemens.net 12.4-STABLE FreeBSD 12.4-STABLE 5f4= 46a12d GENERIC amd64 Created a VM with vm-bhyve: > loader=3D"bhyveload" > cpu=3D"4" > memory=3D"4G" > network0_type=3D"virtio-net" > network0_switch=3D"VL-G-DE-SP02-1681" > disk0_type=3D"virtio-blk" > disk0_name=3D"disk0.img" > uuid=3D"d6d905f9-71a9-11ee-b87d-b499bac04fbe" > network0_mac=3D"58:9c:fc:08:58:c4" The installation is ZFS on root with GPT (UEFI). After the installation and= the reboot the system says: > Consoles: userboot >=20 > FreeBSD/amd64 User boot lua, Revision 1.2 > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > ERROR: cannot open /boot/lua/loader.lua: no such file or directory. >=20 >=20 > Type '?' for a list of commands, 'help' for more detailed help. > OK > OK ls > open '/' failed: no such file or directory > OK lsdev > host devices: > host0: Host filesystem > disk devices: > disk0: Guest drive image > disk0p1: EFI > disk0p2: FreeBSD swap > disk0p3: FreeBSD ZFS I have used FreeBSD-15.0-CURRENT-amd64-20231019-fb7140b1f928-266042-disc1.i= so As soon as I switch to loader=3D"uefi" the system boots. Log file: > Okt. 24 11:43:27: initialising > Okt. 24 11:43:27: [loader: bhyveload] > Okt. 24 11:43:27: [cpu: 4] > Okt. 24 11:43:27: [memory: 4G] > Okt. 24 11:43:27: [hostbridge: standard] > Okt. 24 11:43:27: [com ports: com1] > Okt. 24 11:43:27: [uuid: d6d905f9-71a9-11ee-b87d-b499bac04fbe] > Okt. 24 11:43:27: [debug mode: no] > Okt. 24 11:43:27: [primary disk: disk0.img] > Okt. 24 11:43:27: [primary disk dev: file] > Okt. 24 11:43:27: initialising network device tap1 > Okt. 24 11:43:27: adding tap1 -> bce1bridge (VL-G-DE-SP02-1681 addm) > Okt. 24 11:43:27: bring up tap1 -> bce1bridge (VL-G-DE-SP02-1681 addm) > Okt. 24 11:43:27: booting > Okt. 24 11:43:27: bhyveload -c /dev/nmdm-deblndw013x3v.1A -m 4G -e autobo= ot_delay=3D3 -d /usr/local/bhyve/deblndw013x3v/disk0.img deblndw013x3v > Okt. 24 11:44:19: fatal; loader returned error 2 > Okt. 24 11:44:19: destroying network device tap1 > Okt. 24 11:44:19: stopped > Okt. 24 11:44:34: initialising > Okt. 24 11:44:34: [loader: bhyveload] > Okt. 24 11:44:34: [cpu: 4] > Okt. 24 11:44:34: [memory: 4G] > Okt. 24 11:44:34: [hostbridge: standard] > Okt. 24 11:44:34: [com ports: com1] > Okt. 24 11:44:34: [uuid: d6d905f9-71a9-11ee-b87d-b499bac04fbe] > Okt. 24 11:44:34: [debug mode: no] > Okt. 24 11:44:34: [primary disk: disk0.img] > Okt. 24 11:44:34: [primary disk dev: file] > Okt. 24 11:44:34: initialising network device tap1 > Okt. 24 11:44:34: adding tap1 -> bce1bridge (VL-G-DE-SP02-1681 addm) > Okt. 24 11:44:34: bring up tap1 -> bce1bridge (VL-G-DE-SP02-1681 addm) > Okt. 24 11:44:34: booting > Okt. 24 11:44:34: bhyveload -c /dev/nmdm-deblndw013x3v.1A -m 4G -e autobo= ot_delay=3D3 -d /usr/local/bhyve/deblndw013x3v/disk0.img deblndw013x3v > Okt. 24 11:50:43: fatal; loader returned error 1 > Okt. 24 11:50:43: destroying network device tap1 > Okt. 24 11:50:43: stopped Seems like something is broken here... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274689-27103>