Bug in Snapshot Removing
--_000_D1915E46D966soerenmalchowmconnet_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all I am not sure if the mail just did not get any attention between all the ma= ils and this time it is also going to the libvirt mailing list. I am experiencing a problem with VM becoming unresponsive when removing Sna= pshots (Live Merge) and i think there is a serious problem. Here are the previous mails, http://lists.ovirt.org/pipermail/users/2015-May/033083.html The problem is on a system with everything on the latest version, CentOS 7.= 1 and ovirt 3.5.2.1 all upgrades applied. This Problem did NOT exist before upgrading to CentOS 7.1 with an environme= nt running ovirt 3.5.0 and 3.5.1 and Fedora 20 with the libvirt-preview rep= o activated. I think this is a bug in libvirt, not ovirt itself, but i am not sure. The = actual file throwing the exception is in VDSM (/usr/share/vdsm/virt/vm.py, = line 697). We are very willing to help, test and supply log files in anyway we can. Regards Soeren --_000_D1915E46D966soerenmalchowmconnet_ Content-Type: text/html; charset="us-ascii" Content-ID: <44E2907177D7344D9986671B228BCE48@liquidcampaign.com> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
</head> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin= e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami= ly: Calibri, sans-serif;"> <div>Dear all</div> <div><br> </div> <div>I am not sure if the mail just did not get any attention between all t= he mails and this time it is also going to the libvirt mailing list.</div> <div><br> </div> <div>I am experiencing a problem with VM becoming unresponsive when removin= g Snapshots (Live Merge) and i think there is a serious problem.</div> <div><br> </div> <div>Here are the previous mails,</div> <div><br> </div> <div><a href=3D"http://lists.ovirt.org/pipermail/users/2015-May/033083.html= ">http://lists.ovirt.org/pipermail/users/2015-May/033083.html</a></div> <div><br> </div> <div>The problem is on a system with everything on the latest version, Cent= OS 7.1 and ovirt 3.5.2.1 all upgrades applied.</div> <div><br> </div> <div>This Problem did NOT exist before upgrading to CentOS 7.1 with an envi= ronment running ovirt 3.5.0 and 3.5.1 and Fedora 20 with the libvirt-previe= w repo activated.</div> <div><br> </div> <div>I think this is a bug in libvirt, not ovirt itself, but i am not sure.= The actual file throwing the exception is in VDSM (/usr/share/vdsm/virt/vm= .py, line 697).</div> <div><br> </div> <div>We are very willing to help, test and supply log files in anyway we ca= n. </div> <div><br> </div> <div>Regards</div> <div>Soeren </div> <div><br> </div> </body> </html> --_000_D1915E46D966soerenmalchowmconnet_--
On Sun, May 31, 2015 at 10:56:40PM +0000, Soeren Malchow wrote:
Dear all
I am not sure if the mail just did not get any attention between all the mails and this time it is also going to the libvirt mailing list.
Saw your mails, but it was hard to parse them.
I am experiencing a problem with VM becoming unresponsive when removing Snapshots (Live Merge) and i think there is a serious problem.
Can you do an independent live merge test just with plain libvirt and explain how exactly you can trigger it? For example, I wrote some notes here which I normally use to test live disk image chain merge: http://wiki.libvirt.org/page/Live-merge-an-entire-disk-image-chain-including... Can you reproduce your bug when testing with a variant of the above?
Here are the previous mails,
http://lists.ovirt.org/pipermail/users/2015-May/033083.html
The problem is on a system with everything on the latest version, CentOS 7.1 and ovirt 3.5.2.1 all upgrades applied.
This Problem did NOT exist before upgrading to CentOS 7.1 with an environment running ovirt 3.5.0 and 3.5.1 and Fedora 20 with the libvirt-preview repo activated.
I think this is a bug in libvirt, not ovirt itself, but i am not sure. The actual file throwing the exception is in VDSM (/usr/share/vdsm/virt/vm.py, line 697).
We are very willing to help, test and supply log files in anyway we can.
Regards Soeren
-- /kashyap
participants (2)
-
Kashyap Chamarthy -
Soeren Malchow