Hi! I am using ovirt 3.1 in iSCSI environment . I fixed some bug of vdsm.. In this version , snapshot only for disk, not memory . When I try to take snapshot for a running vm , error log shown in vdsm.log *libvirtError: unsupported configuration: source for disk 'vda' is not a regular file; refusing to generate external snapshot name* After reading libvirt's mail archive, I found a patch in this mail : *http://www.redhat.com/archives/libvir-list/2011-November/msg00843.html <http://www.redhat.com/archives/libvir-list/2011-November/msg00843.html>* but in vdsm environment, every image from iSCSI server is a link file or a dev file , not a regular file . Do you have any solution ? Or I should patch more code , something like memory snapshot ?
----- Original Message -----
From: "yao xu" <xuyao18@gmail.com> To: devel@ovirt.org Sent: Wednesday, August 12, 2015 5:45:24 AM Subject: [ovirt-devel] snapshot for LVM2 Volume
Hi!
I am using ovirt 3.1 in iSCSI environment . I fixed some bug of vdsm..
In this version , snapshot only for disk, not memory .
When I try to take snapshot for a running vm , error log shown in vdsm.log
libvirtError: unsupported configuration: source for disk 'vda' is not a regular file; refusing to generate external snapshot name
After reading libvirt's mail archive, I found a patch in this mail :
http://www.redhat.com/archives/libvir-list/2011-November/msg00843.html
but in vdsm environment, every image from iSCSI server is a link file or a dev file , not a regular file .
Do you have any solution ? Or I should patch more code , something like memory snapshot ?
Who will support your patched ovirt-3.1? The best fix is to upgrade to the latest stable version, ovirt 3.5. Nir
participants (2)
-
Nir Soffer -
yao xu