Thanks for the info. Those xml files will be invaluable. Looking at the pool-logical*.xml, pool-logical.xml will not harm an existing data on disk, correct? Whereas pool-logical-create.xml will attempt to create a new VG (and could cause data loss)? Since I already have LVM setup, and an active VG should I just omit the following from my logical vol xml? <source> <device path='/dev/sda2'> <extent start='31440502784' end='33520877568'/> </device> </source> <capacity>2080374784</capacity> <allocation>2080374784</allocation> You can understand I'm somewhat hesitant to do this, as I don't want to destroy or overwrite any existing data. Best, Casey

Hi Osier, So, I have managed to setup an LVM backed pool (koth-main), and created volumes from this pool: vol-create-as --pool koth-main --name koth-foo-snap --capacity 2G vol-create-as --pool koth-main --name koth-foo --capacity 2G --backing-vol koth-foo-snap I then performed a virt-install, and after configuring the system attempted s snapshot, but as you can see it still doesn't work. I get the same error as before: snapshot-create koth-foo error: Requested operation is not valid: Disk '/dev/main/koth-foo' does not support snapshotting Did I miss a step? Best, Casey Below is the XML for the main volume: <volume> <name>koth-foo</name> <key>5er4qK-stqa-zzJn-Npbe-HOeH-aYfs-TULujB</key> <source> <device path='/dev/sda2'> <extent start='417685569536' end='419833053184'/> </device> </source> <capacity>2147483648</capacity> <allocation>2147483648</allocation> <target> <path>/dev/main/koth-foo</path> <permissions> <mode>0600</mode> <owner>0</owner> <group>6</group> </permissions> </target> <backingStore> <path>/dev/main/koth-foo-snap</path> <permissions> <mode>0660</mode> <owner>0</owner> <group>6</group> </permissions> </backingStore> </volume>

Ah, thanks. I assume this means I can't snapshot LVM backed domains at this time? That is, it isn't possible to use qcow2 and lvm at the same time? Best, Casey