> No I've never used raw, I've used lvm (local block device) and qcow2. > I think you should use the libvirt tools to run VM's and not directly > use qemu-kvm. Sorry, I should have provided some more clarification: that was the error I got from virt-manager. I'm doing all of my work from virt-manager (creating VMs, adding storage, starting/stopping VMs, defining storage pools, etc). > Are you creating the qcow2 file with qemu-img first? example: > qemu-img create -f qcow2 /var/lib/libvirt/images/xfs/kvm2.img 200G No, I'm creating the storage from virt-manager. Host Details -> add a VirtIO disk etc. I'll try to pre-create with qemu-img shortly. > [root@ ~]# virsh pool-dumpxml d34c701f-275c-49d1-92f7-a952d7d5e967 > <pool type='dir'> > <name>d34c701f-275c-49d1-92f7-a952d7d5e967</name> > <uuid>d34c701f-275c-49d1-92f7-a952d7d5e967</uuid> > <capacity unit='bytes'>6593848541184</capacity> > <allocation unit='bytes'>505990348800</allocation> > <available unit='bytes'>6087858192384</available> > <source> > </source> > <target> > <path>/gluster/qcow2</path> > <permissions> > <mode>0700</mode> > <owner>-1</owner> > <group>-1</group> > </permissions> > </target> > </pool> > Thanks for sending this. The one thing I noticed is that you have your gluster filesystem pre-mounted and the pool defined as a "directory". I've been defining my storage pool as a gluster (netfs) filesystem. Similar to using qemu-img, I'll try this as well. -Jacob
