NAbox installation on QEmu | NetApp | Page 1

dim hazel Mar 25, 2025, 8:46 AM

#

The NAbox documentation only covers installation with VMware.
How should NAbox be deployed with QEmu/Virt-Manager? We tried but it gets stuck booting while looking for sdb and also there was no way to input the template customization the same way as with OVF-deployment.

tough lance Mar 25, 2025, 8:47 AM

#

There is a experimental one available for qemu https://nabox.org/downloads/

#

@jade gulch

jade gulch Mar 25, 2025, 8:48 AM

#

I think that’s what @dim hazel is referring to, but configuration is… sparse…

#

Normally you should just have to add a secondary drive and it should boot normally, using dhcp

dim hazel Mar 25, 2025, 8:52 AM

#

Yes that experimental image is the one we were trying to use but it doesn't even seem to boot. Also dhcp is not available but that didn't even get so far to try that.

jade gulch Mar 25, 2025, 9:59 AM

#

So you added a secondary drive disk and it doesn’t boot ?

dim hazel Mar 25, 2025, 10:24 AM

#

yes we tried that. I'll try again and get a screenshot...

dim hazel Mar 25, 2025, 10:51 AM

#

#

that's how it failed

#

would you have any ready commands for the installation from command line instead of virt-manager?

dim hazel Mar 25, 2025, 11:12 AM

#

ok now we got it to boot after adding multiple SATA-disks. static IP-configuration still needed...

jade gulch Mar 25, 2025, 4:38 PM

#

Ok here you can follow this : https://nabox.org/faq/#reset-network-configuration

jade gulch Mar 25, 2025, 4:39 PM

#

dim hazel ok now we got it to boot after adding multiple SATA-disks. static IP-configurati...

I think it’s still unclear what different qemu flavors load in term of disk orders. NAbox requires, on first boot, data disk to be presented as sdb.
It’s possible multiple restart got you to a point where your randomly had your data disk on sdb

burnt kestrel Apr 23, 2025, 6:33 AM

#

Hello Yann you may don't use /dev/sdb but disk uuid it will be constant mount then during reboot, otherwise you have a bad luck to get all sdX randomly affected

jade gulch Apr 23, 2025, 7:03 PM

#

That's really tricky actually. I cannot guess uuid on first boot as far as I know, and device path (I thought) was tthe most reliable way to get the second attached disk. Once that is passed, everything is based on UUID indeed

burnt kestrel May 5, 2025, 9:15 AM

#

double boot with a script to setup uuid on second boot during install may work

jade gulch May 5, 2025, 7:45 PM

#

I'll try the flatcar guys, I've already mentioned that in the past but as it's random, I thought it was solved and it also depends on the hypervisor

sullen kraken May 11, 2026, 6:43 AM

#

Hey @jade gulch
the deployment version for Proxmox has no "qemu-guest-agent" installed ... is it possible to integrate with next release? 🙂
or is there a way to install manually?

jade gulch May 11, 2026, 6:46 AM

#

Mmm, yes that doesn’t sound right but I noticed as well during a recent test, maybe there is a packaging issue with flatcar

jade gulch May 11, 2026, 8:02 AM

#

#

Make sure you enable this. I updated the doc as well.

#NAbox installation on QEmu