On 10/15/2013 05:15 PM, Chris Murphy wrote: > > On Oct 15, 2013, at 4:30 PM, Josh Stone <jistone@xxxxxxxxxx> wrote: > >> On 10/15/2013 02:46 PM, Richard W.M. Jones wrote: >>> On Tue, Oct 15, 2013 at 03:29:38PM -0600, Chris Murphy wrote: >>>> The better snapshots sound ideal for VM testing. Snapshot a >>>> successful install and then try to break the snapshot. Etc. >>>> >>>> Presently virt-manager ignores thinp pools and only creates >>>> conventional LV's. I haven't tried using virsh to force it to use an >>>> already created virtualsize LV as backing, but I'm wondering if it >>>> should work. If not, is there a rough time frame on such support? >> >> FWIW, I have tried, and my VMs with thin LV storage are working fine, >> even though the libvirt storage pool barfs on the VG. (bz924672) > > So you're using virsh to compel it to use the LV I take it? I only just started using this, and I converted my existing VMs to this underneath by manually creating a thin volume, copying the "thick" volume to it, then lvrename so the thin is in place. Libvirt didn't bat an eye at the change. I've since tried cloning by taking a manual LVM snapshot, then "virt-clone ... --file=/dev/vg_foo/lv_bar --preserve-data". This also booted on the thin device just fine. It would be nice if virt-clone could do the snapshot itself though. So I'm not sure about virsh commands, but it seems possible. I did try in virt-manager, you can still get to the thin volumes by using "Browse Local" and go into /dev (assuming you are actually local). -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
