Bug 273099 - 14.0-ALPHA1 unbootable after install
Summary: 14.0-ALPHA1 unbootable after install
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-13 12:25 UTC by Slawomir Wojciech Wojtczak
Modified: 2023-11-03 17:04 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Slawomir Wojciech Wojtczak 2023-08-13 12:25:03 UTC 
Hi,

regarding the message about 14.0-ALPHA1 from here:

- https://lists.freebsd.org/archives/freebsd-snapshots/2023-August/000283.html

I just installed it under Bhyve but after reboot got unbootable system:

| 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.
| 
| Type '?' for a list of commands, 'help' for more detailed help.
| OK 

Regards,
vermaden
Comment 1 Robert Wing freebsd_committer freebsd_triage 2023-08-15 18:12:55 UTC 
(In reply to Slawomir Wojciech Wojtczak from comment #0)

Are you running an updated loader? Can you verify?

This issue should have been fixed in https://cgit.freebsd.org/src/commit/?id=5fd34912b4a51f6ebe55d0d832fab4f3c60228e7
Comment 2 Slawomir Wojciech Wojtczak 2023-08-15 21:58:57 UTC 
(In reply to Robert Wing from comment #1)

It was new/fresh install of 14.0-ALPHA1.

I downloaded thus ISO image:

- FreeBSD-14.0-ALPHA1-amd64-20230811-136fc495615f-264678-disc1.iso

... and installed fresh 14.0-ALPHA1 from it.

Nothing more.

Regards.
Comment 3 Robert Wing freebsd_committer freebsd_triage 2023-08-15 23:13:58 UTC 
(In reply to Slawomir Wojciech Wojtczak from comment #2)

I'm able to reproduce this problem.

I'll start looking into it.
Comment 4 Robert Wing freebsd_committer freebsd_triage 2023-08-15 23:58:00 UTC 
Are you using bhyveload?

I'm guessing that userboot.so from the host is being used.

Can you try using bhyveload with a newer loader?

If you have a current src tree:

    # cd /usr/src/stand && make
    # find /usr/obj -type f -name userboot_lua.so
    /usr/obj/usr/src/amd64.amd64/stand/userboot/userboot_lua/userboot_lua.so

Then pass that loader to bhyveload:

    # bhyveload -d $DISK \
                -m 1024M \
                -l /usr/obj/usr/src/amd64.amd64/stand/userboot/userboot_lua/userboot_lua.so \
                vmname
Comment 5 Slawomir Wojciech Wojtczak 2023-08-16 18:55:21 UTC 
(In reply to Robert Wing from comment #4)

For the record. In UEFI mode it boots/works without any problems.

I will try to rebuild and check that later.
Comment 6 Slawomir Wojciech Wojtczak 2023-08-17 10:07:54 UTC 
(In reply to Robert Wing from comment #4)

Hi.

As you specified - that helped.

I paste below the vm-bhyve config I used to overcome this.

% ls -l /vm/userboot_lua.so          
-rwxr-xr-x 1 root root 588072 2023-08-17 11:55 /vm/userboot_lua.so

% cat /vm/freebsd14/freebsd14.conf 
loader="bhyveload"
bhyveload_loader="/vm/userboot_lua.so"
cpu=1
memory=256M
network0_type="virtio-net"
network0_switch="public"
disk0_type="nvme"
disk0_name="disk0.img"
uuid="asdfasdf-1234-1234-1234-asdfasdfasdf"
network0_mac="01:23:45:67:89:0a"

Hope that helps.

Closing as resolved.

Regards.
Comment 7 Robert Wing freebsd_committer freebsd_triage 2023-11-03 16:10:22 UTC 
*** Bug 274689 has been marked as a duplicate of this bug. ***