Ok, “Qubes dom0 as a domU” v4.1 installed and running ! I could even start the sys-net domU, but only in PV mode (HVM = 100% CPU usage and PVH = crash on boot).
I also realized the vmexit log lines filling my dom0 xl dmesg were caused by using a qubes domU in HVM mode. In PV mode, all good !
Also, for point number 2 about hap=1, the answer was on the “nested virt” page of the Xen wiki …
For now the requirements I found mandatory to have a nested dom0 working:
# builder="hvm" # deprecated
type="hvm"
nesthvm=1
hap=1
# using PV drivers notation for disks is ok (maybe because it falls back to hda ? didn't check yet) ...
disk = [ 'qubes4.1/disk0.img,,xvda' ,
',,xvdb,cdrom' ,
]
# ... but not for the network, the "vif" is not detected by qubes dom0, but the "e1000" is
vif = [ 'bridge=xbr-pftests, mac=00:16:3e:48:40:40, vifname=qubes41,model=e1000' ,
'bridge=xbr-pftests, mac=00:16:3e:48:40:41, vifname=qubes41-pv,type=vif' ,
]
So I’m left with:
- (old 1.) trying to see if I have a IOMMU and if yes get it to work (BIOS and/or microcode update ?)
- (old 3.) Invalid EFER update, I have as many lines as I have vCPU given to qubes
- this bug (qubes not bootable cause 100% CPU), but not sure if it’s related to a nested virt prob or another, no log avail
- when from Qubes dom0 I do
xl console DOMAIN(as I can’t terminal in yet …), the console is really awful (lots of control characters printed), why is that ?