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

Re: [libvirt] libvirtd crashes



2009/12/3 Shi Jin <jinzishuai yahoo com>:
> Hi there,
>
> My libvirtd built from the latest git code keeps on crashing on all machines.
> I turned on debugging and this is the information I have in the log file before crashing:
> 14:31:50.828: debug : virEventUpdateHandleImpl:146 : Update handle w=110 e=12
> 14:31:50.828: debug : virEventInterruptLocked:662 : Interrupting
> 14:31:50.828: debug : qemuMonitorCommandWithHandler:271 : Receive command reply ret=-1 errno=104 0 bytes '(null)'
> 14:31:50.828: error : qemuMonitorCommandWithHandler:290 : cannot send monitor command 'info cpus': Connection reset by peer
> 14:31:50.828: error : qemuMonitorTextGetCPUInfo:436 : internal error cannot run monitor command to fetch CPU thread info
>
> I am not sure if there is any other information needed to help identify the problem.  My building options are:
> ./autogen.sh  --prefix=/usr --sysconfdir=/etc --localstatedir=/var  --without-xen --with-qemu --with-qemu-user=oneadmin --with-qemu-group=oneadmin --without-uml --without-vbox --without-openvz --without-lxc
>
> Please help me here. I can accept the service failing queries from time to time since I have error handling written so that they can be re-tried. But a crashing libvirtd takes the whole thing down.
>
> Thanks a lot.
>
> Shi
> --
> Shi Jin, PhD
>

A GDB backtrace would be helpful. Judging by the debug log alone it
could be a known issue, see:

https://www.redhat.com/archives/libvir-list/2009-December/msg00063.html

Matthias


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