Open Thecoder3281F opened 4 years ago
@Thecoder3281F where was it stuck?
Update UMTP about system runlevel changes By the way, I used Virtualbox's feature to boot from usb
It worked in QEMU
@Thecoder3281F another thing you can try if you're running a virtual machine is the Intel NUC image (if you're not already).
I used the generic x86-64 image
What's the difference?
Should I use the generic or QEMU image for my Linux install? I dual boot Ubuntu and Windows 10
QEMU works
I tried the NUC image Doesn't work
I think it doesn't support Virtualbox
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
The balena supervisor and balena application container engine failed to start
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:
here is the relevant guide
Thanks
doesn't work on second boot(after flashing)
The balena supervisor and balena application container engine failed to start
Yes, it happened again
hey @jtonello can you give this a try on your machine please? Use the intel-nuc image to test. Thanks :)
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.
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.