For guest OS ISO install on standalone HVM, use xvda1 or xvda2?

Quick question about installing a guest OS via ISO install on a standalone HVM qube. As part of the install processes, the guest OS detected that it could be installed on either xvda1 or xvda2. xvda1 appears to be associated with “system storage” when configuring the qubes using the qubes manager. If I increase that number, the guest OS detects a bigger number during the install. xvda2 appears to be associated with the “private storage” allocation. I selected xvda1 and it seems to work. I’m just curious if one of the two is suggested as better.

I guess you mean xvda instead of xvda1 and xvdb instead of xvdb2.
I’d install the system on the system storage xvda device for consistence with Qubes OS templates:

You are correct, I had meant xvda and xvdb. Good catch. Also, I agree, putting the install on xvda keeps things the most consistent with other qubes. But it seems that other than being best for humans, putting it on xvdb would have been ok from a purely technical perspective.


1 Like

xvda is the correct answer.
If you want to do it at template level in Dom0 terminal:
qvm-create GUIX --class TemplateVM --label blue
When you install with the latest ISO (net installs), give the hardware (sys-net) to the GUIX template. If you want to transfer files, you can do it with BTRFS partitions… This topic is vast and I just gave you a few pointers.