[libvirt-users] Fwd: Socket getting closed automatically after destroying vm.

[Michal Privoznik]

On 29.11.2013 14:13, cool dharma06 wrote:
> hi all,
> 
> i am experimenting libvirt-1.1.4 with my xen-4.2.1. virsh working fine
> when creating the vm. but it getting crashed or closed after destroying vm.
> 
> the output is as follows:
> 
> virsh # create /opt/i-47FD0798/libvirt_sec.xml 
> Domain Customer1_Db_domU created from /opt/i-47FD0798/libvirt_sec.xml
> 
> virsh # list
>  Id    Name                           State
> ----------------------------------------------------
>  5     Sample              running
> 
> virsh # destroy 5
> error: Failed to destroy domain 5
> error: End of file while reading data: Input/output error
> error: One or more references were leaked after disconnect from the
> hypervisor
> error: Failed to reconnect to the hypervisor
> 
> virsh # version
> error: failed to connect to the hypervisor
> error: no valid connection
> error: Failed to connect socket to '/var/run/libvirt/libvirt-sock':
> Connection refused
> 
> ___

Well, it seems like the daemon has crashed. Are you able to get any
sensible backtrace? You can:

1) service libvirtd start
2) gdb -p $(pgrep libvirtd)  -> you may need to use debug infos - gdb
will let you know in that case
3) use the virsh commands to reproduce the issue


Michal