At 2010-11-29 03:10, Federico Alves Write: > My KVM fails to start when I type "virsh start Domain" > I get: > Nov 28 14:07:47 rhel60 kernel: virbr0: topology change detected, > propagating > Nov 28 14:07:47 rhel60 kernel: virbr0: port 1(vnet0) entering forwarding > state > Nov 28 14:07:47 rhel60 kernel: libvirtd[14404]: segfault at 7f8aa0adf000 > ip 0000000000438020 sp 00007f8aa0adc0c0 error 4 in libvirtd[400000+dc000] > Nov 28 14:07:47 rhel60 abrt[14408]: saved core dump of pid 14404 > (/usr/sbin/libvirtd) to /var/spool/abrt/ccpp-1290971267-14404.new/coredump > (71540736 bytes) > Nov 28 14:07:47 rhel60 abrtd: Directory 'ccpp-1290971267-14404' creation > detected > Nov 28 14:07:47 rhel60 libvirtd: 14:07:47.477: error : > virExecDaemonize:778 : internal error Intermediate daemon process exited > with status 0. > Nov 28 14:07:47 rhel60 kernel: virbr0: port 1(vnet0) entering disabled > state > Nov 28 14:07:47 rhel60 kernel: device vnet0 left promiscuous mode > Nov 28 14:07:47 rhel60 kernel: virbr0: port 1(vnet0) entering disabled > state > Nov 28 14:07:47 rhel60 libvirtd: 14:07:47.512: error : > qemudReadLogOutput:2315 : internal error Process exited while reading > console log output: > Nov 28 14:07:47 rhel60 abrtd: Crash is in database already (dup of > /var/spool/abrt/ccpp-1290963179-7955) > Nov 28 14:07:47 rhel60 abrtd: Deleting crash ccpp-1290971267-14404 (dup of > ccpp-1290963179-7955), sending dbus signal > > Any idea what is happening?
According to your log, the libvirtd core dumped. It is a bug of libvirt, not virt-tools. What is the version of libvirt that you use? The bug may be fixed in newest libvirt(A similar bug that is caused by e6b68d74 has been fixed). > > Federico > > _______________________________________________ virt-tools-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-tools-list
