[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [fedora-virt] info on save function in virt-manager



On Fri, 2009-09-25 at 08:52 +0200, Chris Lalancette wrote: 
> gianluca.cecchi wrote:
> > BTW: the restore on the same host (with the VM still stopped as at the
> > end of the save), doesn't work either. I get:
> > Error restoring domain '/mnt/rhel54_240909_1750.save': Unable to read
> > QEMU help output: Interrupted system call
> > 
> > And inside the details window:
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/manager.py", line 458, in
> > restore_saved_callback
> >     newconn.restore(file_to_load)
> >   File "/usr/share/virt-manager/virtManager/connection.py", line 642, in
> > restore
> >     self.vmm.restore(frm)
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1420, in
> > restore
> >     if ret == -1: raise libvirtError ('virDomainRestore() failed',
> > conn=self)
> > libvirtError: Unable to read QEMU help output: Interrupted system call
> > 
> > [root virtfedbis qemu]# ll /mnt/rhel54_240909_1750.save
> > -rw------- 1 root root 334221504 2009-09-24 17:51
> > /mnt/rhel54_240909_1750.save
> > 
> > The VM has an hd of 8Gb of size and 4Gb of ram.
> > 
> > If I want to debug setting LIBVIRTD_DEBUG=1 and then run the restore
> > command via command line, what would it be, so that I can bugzilla this
> > (if not already there)?
> > 
> > Inside /var/log/messages I have this:
> > Sep 24 17:51:51 virtfedbis kernel: libvirtd[25820]: segfault at 0 ip
> > 00000039762a4822 sp 00007f20a7546880 error 4 in libc-2.10.1.so
> > <http://libc-2.10.1.so>[3976200000+164000]
> > Sep 24 17:51:51 virtfedbis libvirtd: 17:51:51.379: error :
> > qemudExtractVersionInfo:1032 : Unable to read QEMU help output:
> > Interrupted system call
> 
> OK, yeah, it looks like libvirtd segfaulted, which is obviously not good.
> You'll want to stop libvirtd, then run (as root):
> 
> # ulimit -c unlimited
> # LIBVIRT_DEBUG=1 /usr/sbin/libvirtd --verbose
> 
> Assuming you get a core out of it, the best information to get is the output of
> "thread apply all bt" with gdb.

This looks similar to Charles Duffy's recent post to libvir-list here:

https://www.redhat.com/archives/libvir-list/2009-September/msg00663.html

Paul

-- 
Paul Jenner <psj familyjenner co uk>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]