Setting about to get a Win 10 Pro qube running, I’ve been doing some digging, but I wanted to ask a question about what I want to attempt, as it seems most of the documentation is about first-time installs.
So, here’s my situation. Before Qubes, I was attempting to get Xen going from scratch on CentOS 7. I had so many issues with it that I just had to give up. However, I was able to get a clean Windows 10 Pro VM working on it, just never could get the PCI passthrough to work (due to OVMF issues). So, I have a LVM volume group with three LVs (boot, data, swap) in it on a dedicated SSD which has that working Windows install on it. It used the qemu-supplied VNC video driver, and I have all the Xen PV drivers (v9.0) already installed in it. I want to try and see if I can use that install, but I am not sure how to get a qube standalone setup adapted to use an existing LVM VG and LVs, rather than stuffing it in the vm-pool allocation. I expect I will have to install the QWT tools as well (is there a way to do that to the dedicated LVs in the Win10 VG?). I guess the first order of business is to determine if and how I can substitute the existing VG/LVs in the qube config. Looking at the qvm-prefs doc, I don’t see anything that can set or change the volume arrangements. Is there any doc on the underlying configs? Like, does Qubes generate and use xl vm .cfg files under-the-hood? If so, where might they be stored and can I modify them, or do I have to modify a higher-level meta-config file? (for reasons like “don’t edit this file directly, it is regenerated by xxx automatically, so any changes won’t be persistent”)
Also, looking at the Community QWT doc, it looks like the Qubes Video Driver isn’t working/available yet for Win10. Is there any VNC/SPICE support available? Ultimately, if GPU Passthrough will work, I will probably disable the emulated adapters, but until I can get it to work, I think emulated VNC/SPICE or similar will be required.
Again, thank you in advance for any advice.