Bug 1073466 - live snapshot turns the VM off
Summary: live snapshot turns the VM off
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 13:40 UTC by Tomas Jelinek
Modified: 2016-04-10 18:05 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-04-10 18:05:52 UTC
Embargoed:


Attachments (Terms of Use)
engine log (36.14 KB, text/x-log)
2014-03-06 13:40 UTC, Tomas Jelinek
no flags Details
vdsm logs (351.67 KB, text/x-log)
2014-03-06 13:41 UTC, Tomas Jelinek
no flags Details
libvirt's log (3.02 MB, text/plain)
2014-03-11 13:53 UTC, Arik
no flags Details
qemu's log (2.51 KB, text/plain)
2014-03-11 13:54 UTC, Arik
no flags Details

Description Tomas Jelinek 2014-03-06 13:40:54 UTC
Created attachment 871452 [details]
engine log

1: have a VM with no OS installed, attached 1 disk
2: start the VM
3: in webadmin go to VM -> snapshots -> create (also include memory)
4: it creates the snapshot properly, but turns the VM off

vdsm: vdsm-4.13.3-4.fc20.x86_64
engine: ovirt-engine-3.4.0-0.12.master.20140228075627.fc19.noarch

Comment 1 Tomas Jelinek 2014-03-06 13:41:31 UTC
Created attachment 871454 [details]
vdsm logs

Comment 2 Arik 2014-03-09 13:28:19 UTC
can you please also attach libvirt logs?

Comment 3 Arik 2014-03-11 13:53:47 UTC
Created attachment 873148 [details]
libvirt's log

Comment 4 Arik 2014-03-11 13:54:19 UTC
Created attachment 873149 [details]
qemu's log

Comment 5 Arik 2014-03-11 14:02:10 UTC
I managed to reproduce it and it seems that the guest crashes when taking snapshot with memory for a guest with no OS installed.
The log files of libvirt & qemu were attached.

libvirt: 1.1.3.2
qemu-kvm: 1.6.1
(fedora 19)

Comment 6 Cole Robinson 2016-04-10 18:05:52 UTC
guest crashes are likely qemu issues, which I suspect in this case is long since fixed. if anyone is still hitting issues, please file a bug against your distro's qemu version


Note You need to log in before you can comment on or make changes to this bug.