Re: [libvirt] When vm's status file being left over, some persistent but inactive vms will be lost by libvirtd after libvirtd rebooting.

2013-11-06 Thread Wangyufei (A)
t@redhat.com; Xuchao (H); Wangrui (K) > Subject: Re: [libvirt] When vm's status file being left over, some persistent > but inactive vms will be lost by libvirtd after libvirtd rebooting. > > On Fri, Oct 18, 2013 at 03:00:22AM +, Wangyufei (A) wrote: > > Hello, > >

Re: [libvirt] When vm's status file being left over, some persistent but inactive vms will be lost by libvirtd after libvirtd rebooting.

2013-10-28 Thread Daniel P. Berrange
On Fri, Oct 18, 2013 at 03:00:22AM +, Wangyufei (A) wrote: > Hello, > I found a problem that: > vm's status file may be left over in the path /var/run/libvirt/qemu under > some situation, such as host reboot. When vm's status file is left over, some > persistent but inactive vms will be l

[libvirt] When vm's status file being left over, some persistent but inactive vms will be lost by libvirtd after libvirtd rebooting.

2013-10-17 Thread Wangyufei (A)
Hello, I found a problem that: vm's status file may be left over in the path /var/run/libvirt/qemu under some situation, such as host reboot. When vm's status file is left over, some persistent but inactive vms will be lost by libvirtd after it is rebooted. And you can do as follows to repro