[libvirt] libvirt accidentally destroys guests after being restarted
Sorry in advance for possible top-post, I`m not able to add proper messageid here.
Does it ever occur if you don't run with DHCP snooping enabled?
Stefan
No, please disregard those errors. We don`t run DHCP snooping/IP learning on interfaces but only modified clean-traffic rules, current issue almost for sure does not have relation to it.
On 03/02/2013 09:39 AM, Andrey Korolyov wrote:
Sorry in advance for possible top-post, I`m not able to add proper messageid here.
Does it ever occur if you don't run with DHCP snooping enabled?
Stefan No, please disregard those errors. We don`t run DHCP snooping/IP learning on interfaces but only modified clean-traffic rules, current issue almost for sure does not have relation to it.
Ok. Nevertheless I may convert the noise from NWFilter DHCP Snooping to only become active in case debugging is enabled. Other information that may be of interest is the checkout revision of libvirt 'beyond' version 1.0.2. What version of QEMU are you using? And possibly what is the XML your VMs are using? At least that's the info I would use to start debugging this, though 'others' may have something in the back of their minds... Stefan
Stefan, qemu-1.1.2 with dfsg-5 patchset http://ftp.de.debian.org/debian/pool/main/q/qemu/qemu_1.1.2+dfsg-5.debian.ta... for example VM` xml is quite simple, qemu64 cpu model, pc-1.1 machine model, one virtio disk, two bridged virtio NICs, serial and virtio-serial ptys. On Sat, Mar 2, 2013 at 7:26 PM, Stefan Berger <stefanb@linux.vnet.ibm.com> wrote:
On 03/02/2013 09:39 AM, Andrey Korolyov wrote:
Sorry in advance for possible top-post, I`m not able to add proper messageid here.
Does it ever occur if you don't run with DHCP snooping enabled?
Stefan
No, please disregard those errors. We don`t run DHCP snooping/IP learning on interfaces but only modified clean-traffic rules, current issue almost for sure does not have relation to it.
Ok. Nevertheless I may convert the noise from NWFilter DHCP Snooping to only become active in case debugging is enabled.
Other information that may be of interest is the checkout revision of libvirt 'beyond' version 1.0.2. What version of QEMU are you using? And possibly what is the XML your VMs are using? At least that's the info I would use to start debugging this, though 'others' may have something in the back of their minds...
Stefan
Hello. We finally found the cause of this problem. When we use "virsh reboot domain", it is actually two calls qemuMonitorSystemPowerdown() and qemuProcessFakeReboot(). Inside the first call domain stateReason is set to VIR_DOMAIN_SHUTDOWN_UNKNOWN and then virDomainSaveStatus() is called. Inside the second call domain stateReason is set to VIR_DOMAIN_RESUMED_UNPAUSED but domain configuration is not saved into XML. After restart of libvirtd domain stateReason SHUTDOWN_UNKNOWN is restored and domain is automatically shutdown. In the attached files there are shell log, qemu log, libvirtd log and proposed patch. wbr, Sergey.
participants (3)
-
Andrey Korolyov -
Sergey Fionov -
Stefan Berger