Bug 1351057

Description of problem:
lxc: when undefine a vm first, cannot destroy it successfully. 

Version-Release number of selected component (if applicable):
libvirt-1.3.5-1.el7.x86_64
qemu-kvm-rhev-2.6.0-5.el7.x86_64
virt-install-1.4.0-1.el7.noarch
kenel-3.10.0-382.el7.x86_64

How reproducible:
100%

Please note, this is a regression issue and not reproducible in libvirt 1.3.4-1
Steps to Reproduce:
1. # virt-install --connect lxc:/// --name avocado-vt-vm1 --ram 500 --noautoconsole
WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results.

Starting install...
Creating domain... | 0 B 00:00:00
Domain creation completed.


2. # virsh -c lxc:/// undefine avocado-vt-vm1
Domain avocado-vt-vm1 has been undefined

3. # virsh -c lxc:/// destroy avocado-vt-vm1
error: Disconnected from lxc:/// due to I/O error
error: Failed to destroy domain avocado-vt-vm1
error: End of file while reading data: Input/output error

Actual results:
after undefine vm, destroy failed. 

Expected results:
Destroy vm should be successful in last step. 

Additional info:
During the test, we met another issue but not always reproducible. It's also a IO error issue when try to virt-install a lxc vm. We met this issue with a autoscript, and machines are not reserved, so when this bug have assignee, we'll provide a machine to debug. Steps as follow: 

# virt-install --connect lxc:/// --name avocado-vt-vm1 --ram 500 --noautoconsole; virsh -c lxc:/// list --all
WARNING  No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results.

Starting install...
ERROR    End of file while reading data: Input/output error
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
  virsh --connect lxc:/// start avocado-vt-vm1
otherwise, please restart your installation.
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused

system log:
Jun 28 06:27:37 hp-dl320eg8-08 journal: internal error: guest failed to start: Failure in libvirt_lxc startup: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 28 06:27:37 hp-dl320eg8-08 kernel: libvirtd[17119]: segfault at a0 ip 00007f366ab2bcd5 sp 00007f3677eb39b0 error 4 in libvirt_driver_lxc.so[7f366ab13000+43000]
Jun 28 06:27:37 hp-dl320eg8-08 systemd: libvirtd.service: main process exited, code=killed, status=11/SEGV
Jun 28 06:27:37 hp-dl320eg8-08 systemd: Unit libvirtd.service entered failed state.
Jun 28 06:27:37 hp-dl320eg8-08 systemd: libvirtd.service failed.
Jun 28 06:27:37 hp-dl320eg8-08 systemd: libvirtd.service holdoff time over, scheduling restart.
Jun 28 06:27:37 hp-dl320eg8-08 systemd: Starting Virtualization daemon...
Jun 28 06:27:37 hp-dl320eg8-08 systemd: Started Virtualization daemon.