On Sunday, July 13th, 2025 at 11:10, Marek Marczykowski-Górecki <marma...@invisiblethingslab.com> wrote: > > The above documentation is outdated a bit - ...
Ah-ha: thanks for pointing that out. > ... with LVM thin provisioning > the CoW layer on root volume is done in dom0, so VM gets read-write > snapshot as xvda and doesn't need to do CoW on its own. Yeah: so I did dump, and take a look in, the virsh files and saw the read-write config there, but clearly didn't appreciate the implications of it, especially as I was looking for something read-only. I just assumed I had missed something. > So, volatile > volume is used only for swap. To just clarify that last bit though: the 9G partition in the volatile VBD doesn't even play a part in the in-Dom0 CoW layering: it's just 9G of unused space in a 10G volume that will get created for every VM instance? Asking, as I have an old laptop on which I haven't been able to get Qubes to install, but was hoping to still replicate most of the Qubes compartmentalisation for the VMs, but running a vanilla Xen. > Generally VM's initramfs takes care of assembling /dev/mapper/dmroot. > But if you look closely, /dev/mapper/dmroot is simply a symlink to > /dev/xvda3. That may well have been a case of not seeing the wood for the trees, because I thought I was in the middle of a dmsetup forest! Feedback much appreciated: I think I can get to where I want to now. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/qubes-devel/175248876812.8.2935117852836103997.807349373%404forl1st5.slmail.me.
