[Bug 251250] bhyveload cannot find filesystem: ERROR: cannot open /boot/lua/loader.lua: no such file or directory.
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Nov 19 07:55:49 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251250
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 at FreeBSD.org
Reporter: d8zNeCFG at 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 tap909
-d /dev/diskid/DISK-HAL_V0909 v909", the following appears on the console:
Launching virtual machine "v909" ...
Consoles: userboot
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
- Entering "show" yields:
OK show
LINES=24
autoboot_delay=NO
boot_serial=1
console=userboot
currdev=disk0:
interpret=OK
loaddev=disk0:
prompt=${interpret}
script.lang=lua
smbios.bios.vendor=BHYVE
twiddle_divisor=1
OK
- 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
- The problem seems to be that currdev and loaddev are wrong, they should point
to disk0a: instead
- The filesystem is not found:
OK ls
open '/' failed: no such file or directory
OK
- It is possible to set currdev: manually to disk0a: (loaddev cannot be
changed), then load all necessary modules manually, and then issue the command
"boot" in order to start the system. However, when doing it this way no console
output is shown. Otherwise, the client seems to work o.k.
OK set currdev=disk0a:
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
-- Martin
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-virtualization
mailing list