System hangs or reboots during live cd boot about iso HOT 19 CLOSED

Using VirtualBox I can boot the ISO both in BIOS and EFI mode:

You might be fine with the ISO, and with restarting from a .vdi-based installation, however starting from a .vdi with the guest in EFI mode can be troublesome. https://old.reddit.com/r/freebsd/comments/k3p47f/-/ggj900o/?context=1:

VirtualBox's UEFI does not have a NVRAM and cannot save boot options. VB's EFI is like one from 2011.

#25 (comment)

… VMware works only when set to BIOS booting for whatever reason.

FreeBSD bug 251866 – Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

from iso.

Thanks for the clarification. Maybe we should write a concise summary for https://hellosystem.github.io/docs/user/getting-started.html#system-requirements? Pull requests welcome!

from iso.

Hi @FabioSedia, thanks for testing.
Can you give some information about your system?
Also, can you try on a different computer please?

from iso.

Hi @FabioSedia, thanks for testing.
Can you give some information about your system?
Also, can you try on a different computer please?

I can't try on another computer. Anyway my pc is a ryzen zen+ cpu with uefi and 16gb of ram. Radeon gpu. The weird thing is it has the same behavior on virtual box bios mode, when in uefi it just opens the uefi shell. Maybe the image is corrupted?

from iso.

Might be. The next one will be up soon.

from iso.

I am downloading the next build...

from iso.

Fine I'll test it tomorrow

from iso.

Happens to me as well while making a rw swap-memdisk copy at boot, all the times! Was curious but couldn't test it...
Mine is an HP EliteBook 8460p Intel Sandybridge i7-2720QM, 12GB RAM.

from iso.

@probonopd The new image still reboots itself during the copy on my pc, but the vm with bios works. The vm with uefi doesn't, i still get an uefi shell only

from iso.

Typing this from a machine booted with UEFI. It's an Acer machine with an InsydeH2O UEFI firmware and an Intel CPU.

What we know so far is that VMware works only when set to BIOS booting for whatever reason.

from iso.

Typing this from a machine booted with UEFI. It's an Acer machine with an InsydeH2O UEFI firmware and an Intel CPU.

What we know so far is that VMware works only when set to BIOS booting for whatever reason.

Yeah, same behavior on virtualbox. What happens when you use uefi on vmware? I get an uefi shell only

from iso.

When it comes to virtualization, the only combinations I have tested myself are

• BIOS mode on VirtualBox on FreeBSD
• BIOS mode on Qemu on FreeBSD (slow)

Do you get the same errors e.g., with GhostBSD?

from iso.

Happens to me as well, my machine is thinkpad t440p

from iso.

Do you get the same errors e.g., with GhostBSD?

In my case no, it boots just fine.

from iso.

Very interesting. Needs more investigation.

Using VIrtualBox I can boot the ISO both in BIOS and EFI mode:

from iso.

For reference only, involving VirtualBox on FreeBSD-CURRENT: #74 (closed)

from iso.

@FabioSedia @gcvl @heirbol please, is the issue reproducible with 0.4.0 (0D13)?

hello-0.4.0_0D13-FreeBSD-12.1-amd64.iso (specifically) under https://github.com/helloSystem/ISO/releases/tag/experimental-12.1

Considerations

https://hellosystem.github.io/docs/user/troubleshooting.html#known-issues

Boot stalls during Replicate system image to swap-based memdisk: This build of the ISO is damaged. Please wait for another continuous build to appear and try again.

• overlapping with parts of #102 where for a single build, some boots will fail whilst some (not all) others succeed; and for a single build, some boots will stall whilst some others are interrupted by sudden restarts …

from iso.

#25 (comment)

hangs or reboots at the section: can we get the union fa or openzfs to make...

In context (a screenshot of my own):

With the reasonable assumption that hangs and reboots are at the zfs recv … stage:

• this issue #25 can be closed with reference to #102 (comment)

from iso.

Closing in favor of #102 (comment).

If anyone can reproduce the issue with a released version (0.4.0,...) rather than an experimental one then please comment here and we will reopen.

from iso.