[Bug 685338] New: XendCheckpoint.py calls acquire_running_lock() which is no longer defined in XendDomainInfo.py
https://bugzilla.novell.com/show_bug.cgi?id=685338 https://bugzilla.novell.com/show_bug.cgi?id=685338#c0 Summary: XendCheckpoint.py calls acquire_running_lock() which is no longer defined in XendDomainInfo.py Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: brianlgilbert@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Using xen-4.1.0_01-111.1.src.rpm on OpenSuse 11.3 This contains the patch file xend-domain-lock.patch. Diff that file against the version in xen-4.0.1_01-96.1.src.rpm, observe that the changes the old version made to XendDomainInfo.py are no longer included. These changes included defining functions acquire_running_lock() and release_running_lock(). Problem I am seeing is that this command fails (where xpsp3 is an hvm): #xm snapshot-apply xpsp3 snap1 xend.log contents are: 2011-04-04 10:11:05 5123] ERROR (XendCheckpoint:419) acquire_running_lock Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 415, in restore dominfo.acquire_running_lock() File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 3488, in __getattr__ raise AttributeError(name) AttributeError: acquire_running_lock [2011-04-04 10:11:05 5123] ERROR (XendDomain:1206) Restore failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1184, in domain_restore_fd dominfo = XendCheckpoint.restore(self, fd, paused=paused, relocating=relocating) File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 420, in restore raise exn AttributeError: acquire_running_lock Commenting out the call to acquire_running_lock gets past the error, but don't think that's the right direction to go. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=685338
https://bugzilla.novell.com/show_bug.cgi?id=685338#c
Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=685338
https://bugzilla.novell.com/show_bug.cgi?id=685338#c1
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=685338
https://bugzilla.novell.com/show_bug.cgi?id=685338#c2
--- Comment #2 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com