BalenaOS startup hang on Virtualbox

[Thecoder3281F]

When I plugged in the installation thumb drive, the balena logo came out and the computer shut down. After turning it on again, I pressed the up arrow to open the command prompt and saw that it was stuck on a particular stage.

[chrisys]

@Thecoder3281F where was it stuck?

[Thecoder3281F]

Update UMTP about system runlevel changes
By the way, I used Virtualbox's feature to boot from usb

[Thecoder3281F]

It worked in QEMU

[chrisys]

@Thecoder3281F another thing you can try if you're running a virtual machine is the Intel NUC image (if you're not already).

[Thecoder3281F]

I used the generic x86-64 image

[Thecoder3281F]

What's the difference?

[Thecoder3281F]

Should I use the generic or QEMU image for my Linux install?
I dual boot Ubuntu and Windows 10

[Thecoder3281F]

QEMU works

[Thecoder3281F]

I tried the NUC image
Doesn't work

[Thecoder3281F]

I think it doesn't support Virtualbox

[Thecoder3281F]

There was a warning that only appeared in the NUC image, not the generic one.
WARN[0000] Couldn't run auplink before unmount /tmp/docker-aufs-union852908369 error="exec: \"auplink"\: executable file not found in $PATH" storage-driver=aufs

[Thecoder3281F]

The balena supervisor and balena application container engine failed to start

[rahul-thakoor]

Hey @Thecoder3281F
Thanks for the feedback. We do have people who successfully run intel-nuc imagein VirtualBox. Can you please describe the workflow you are using to get it to work?

For virtualbox the recommended steps are:

1. creating a new virtual machine, setting the type to "Other Linux 64-bit"
2. In the VM settings
   • Disable I/O APIC (default setting can result in a boot crash)
   • Enable EFI (the NUC image is set up for UEFI boot)
3. add a new SATA storage controller and a virtual hard disk. The virtual hard disk can be any image format; Make the disk at least 8 GB in size.
4. unzip the download image and convert it to a virtual hardware image using the VBoxManage tool and create a Virtual Machine Disk (VMDK) file
5. add the .vmdk image file you created in the previous step as a second SATA hard disk.
6. Boot, you should see an initial Flash boot screen

[rahul-thakoor]

here is the relevant guide

[Thecoder3281F]

Thanks

[Thecoder3281F]

[Thecoder3281F]

doesn't work on second boot(after flashing)

[Thecoder3281F]

The balena supervisor and balena application container engine failed to start

Yes, it happened again

[rahul-thakoor]

hey @jtonello can you give this a try on your machine please?
Use the intel-nuc image to test. Thanks :)

[jtonello]

This worked fine for me. I got a brief flash of an error, but the VM booted to flash, stopped, and booted to the balena screen properly. The key is to not add a device when creating the VM. That defaults to IDE, which doesn't work. A user must create a SATA controller and add two virtual disks to that from VirtualBox settings before booting.