On Mon, 2013-05-27 at 14:28 +0200, Viktor Mihajlovski wrote: > On 05/27/2013 10:41 AM, Chen Fan wrote: > > From: chenfan <chen.fan.fnst@xxxxxxxxxxxxxx> > > @@ -3185,6 +3194,9 @@ int qemuMonitorVMStatusToPausedReason(const char *status) > > case QEMU_MONITOR_VM_STATUS_WATCHDOG: > > return VIR_DOMAIN_PAUSED_WATCHDOG; > > > > + case QEMU_MONITOR_VM_STATUS_GUEST_PANICKED: > > + return VIR_DOMAIN_PAUSED_GUEST_PANICKED; > > + > > /* unreachable from this point on */ > > case QEMU_MONITOR_VM_STATUS_LAST: > > ; > I just have crashed the guest while libvirtd wasn't running, > after a restart, virsh domstate --reason always reports > paused (guest panicked) while I would expect crashed (guest panicked). > Either QEMU is reporting a bogus state or the state computation > is flawed somewhere... > Then I will fix this bug. and remain on_crash default behavior in the XML. Thanks for your comments. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list