Date: Thu, 19 Nov 2020 07:55:49 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 251250] bhyveload cannot find filesystem: ERROR: cannot open /boot/lua/loader.lua: no such file or directory. Message-ID: <bug-251250-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251250 Bug ID: 251250 Summary: bhyveload cannot find filesystem: ERROR: cannot open /boot/lua/loader.lua: no such file or directory. Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: d8zNeCFG@aon.at Scenario: - Host system was running FreeBSD 12.1 - Using /usr/share/examples/bhyve/vmrun.sh to start a VM running FreeBSD 12= .2, using a disk device attached via iSCSI and a network device via bridge/tap - This was running without issues. - Now, the host system has been upgraded to FreeBSD 12.2 Result: - After entering "sh /usr/share/examples/bhyve/vmrun.sh -u -c 4 -m 3G -t ta= p909 -d /dev/diskid/DISK-HAL_V0909 v909", the following appears on the console: Launching virtual machine "v909" ... Consoles: userboot=20=20 FreeBSD/amd64 User boot lua, Revision 1.2 ERROR: cannot open /boot/lua/loader.lua: no such file or directory. Type '?' for a list of commands, 'help' for more detailed help. OK=20 - Entering "show" yields: OK show LINES=3D24 autoboot_delay=3DNO boot_serial=3D1 console=3Duserboot currdev=3Ddisk0: interpret=3DOK loaddev=3Ddisk0: prompt=3D${interpret} script.lang=3Dlua smbios.bios.vendor=3DBHYVE twiddle_divisor=3D1 OK=20 - Entering "lsdev" yields: OK lsdev host devices: host0: Host filesystem disk devices: disk0: Guest drive image disk0a: FreeBSD UFS disk0b: FreeBSD swap disk0d: FreeBSD UFS OK=20 - The problem seems to be that currdev and loaddev are wrong, they should p= oint to disk0a: instead - The filesystem is not found: OK ls open '/' failed: no such file or directory OK=20 - It is possible to set currdev: manually to disk0a: (loaddev cannot be changed), then load all necessary modules manually, and then issue the comm= and "boot" in order to start the system. However, when doing it this way no con= sole output is shown. Otherwise, the client seems to work o.k. OK set currdev=3Ddisk0a: OK ls / d .snap d lost+found d usr d CVS d boot d root d etc d bin d dev d lib d libexec d media d mnt d proc d rescue d sbin d tmp d var l sys d vol .cshrc .profile COPYRIGHT entropy d d d a d net patch.2020-11-01.19:15:22 releng_12.1.r354774.tar.gz OK=20 -- Martin --=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-251250-27103>