search for: savevm

...ou can shed some light on the following error. I created a VM on my Centos 6 KVM machine, used a qcow2 image and wanted to create a snapshot via 'virsh snapshot-create' command: // [root at kvmhost ~]# virsh snapshot-create server01 error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found \\ I googled before the post, found some [0] threads [1], but could not find an answer how to solve the problem. If the kvm-qemu lacks the support of a savevm monitor, how can I add one? Do I need to recompile kvm-qemu with special flags or is simply a R...

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm' id='6'> <name>CentOS6-x86-001</name> <uuid>050fb9d8-0b9a-48b9-a432-16eec57a9e8f</uuid> <memor...

hello. I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do: "savevm $domain" the domain ist gone. Console says "unable to connect to monitor". Libvirt.log says: qemu-system-x86_64: /var/tmp/portage/app- emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348: virtio_net_save: Assertion `!n->vhost_started' fail ed. Googling for this...

Am 22.09.14 10:42, schrieb Daniel P. Berrange: > On Sat, Sep 20, 2014 at 02:13:16PM +0200, Thomas Stein wrote: >> hello. >> >> I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do: >> >> "savevm $domain" >> >> the domain ist gone. Console says "unable to connect to monitor". Libvirt.log >> says: >> >> qemu-system-x86_64: /var/tmp/portage/app- >> emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348: >> virtio_net_save: A...

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm' id='6'> <name>CentOS6-x86-001</name> <uuid>050fb9d8-0b9a-48b9-a432-16eec57a9e8f</uuid> <memor...

On Sat, Sep 20, 2014 at 02:13:16PM +0200, Thomas Stein wrote: > hello. > > I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do: > > "savevm $domain" > > the domain ist gone. Console says "unable to connect to monitor". Libvirt.log > says: > > qemu-system-x86_64: /var/tmp/portage/app- > emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348: > virtio_net_save: Assertion `!n->vhost_start...

...rd part is > Windows 7 is restored properly from the managedsave however XP does not, > doing a start from virsh shows this: > > virsh # start xp-check > error: Failed to start domain xp-check > error: internal error: early end of file from monitor: possible problem: > Unknown savevm section type 5 > 2015-02-04T23:55:37.117515Z qemu-kvm: load of migration failed: Invalid > argument > > (qemu-kvm is a link to qemu-system-x86_64). > > Any ideas how to fix this ? Smells like qemu bug to me. The only way that this could be a libvirt bug is that libvirt will ge...

...set to suspend at shutdown. The weird part is Windows 7 is restored properly from the managedsave however XP does not, doing a start from virsh shows this: virsh # start xp-check error: Failed to start domain xp-check error: internal error: early end of file from monitor: possible problem: Unknown savevm section type 5 2015-02-04T23:55:37.117515Z qemu-kvm: load of migration failed: Invalid argument (qemu-kvm is a link to qemu-system-x86_64). Any ideas how to fix this ? Thanks

..."), this is not expected to >> work. > > Hi David, thanks for getting back to us on this. Hi Florian, (sombeody please correct me if I'm wrong) > > I see your point, except the issue Kashyap and I are describing does > not occur with live migration, it occurs with savevm/loadvm (virsh > managedsave/virsh start in libvirt terms, nova suspend/resume in > OpenStack lingo). And it's not immediately self-evident that the > limitations for the former also apply to the latter. Even for the live > migration limitation, I've been unsuccessful at finding...

...ir noses on that. :) Indeed. nesting is nice to enable as it works in 99% of all cases. It just doesn't work when trying to migrate a nested hypervisor. (on x86) That's what most people don't realize, as it works "just fine" for 99% of all use cases. [...] >> >> savevm/loadvm is not expected to work correctly on an L1 if it is >> running L2 guests. It should work on L2 however. > > Again, I'm somewhat struggling to understand this vs. live migration — > but it's entirely possible that I'm sorely lacking in my knowledge of > kernel a...

...ight be screwed up after migration, resulting in L1 crashes. > > In addition, certain VMX features might be missing on the target, which > also still has to be handled via the CPU model in the future. Thanks a bunch for the added detail. Now I got a primer today from Kashyap on IRC on how savevm/loadvm is very similar to migration, but I'm still struggling to wrap my head around it. What you say makes perfect sense to me in that _migration_ might blow up in subtle ways, but can you try to explain to me why the same considerations would apply with savevm/loadvm? > L0, should hopeful...

Hi, Is anyone clear about the format of qemu file for savevm or loadvm? bruce

On Thu, Feb 8, 2018 at 2:47 PM, David Hildenbrand <david@redhat.com> wrote: >> Again, I'm somewhat struggling to understand this vs. live migration — >> but it's entirely possible that I'm sorely lacking in my knowledge of >> kernel and CPU internals. > > (savevm/loadvm is also called "migration to file") > > When we migrate to a file, it really is the same migration stream. You > "dump" the VM state into a file, instead of sending it over to another > (running) target. > > Once you load your VM state from that file, it...

...files, which are such raw physical memory images, when a guest is paused or snapshotted.) In order to analyze the memory of Libvirt/KVM guests with my Linux memory forensics software, Second Look, I've created a tool for converting Libvirt-QEMU-save files (output of virsh save command) or QEMU-savevm files (output of virsh dump command) to raw physical memory images. I've got a basic working capability, though I'm still tracking down some problems with a guest allocated 8GB RAM--not all the memory seems to be present in the save or dump file. And I haven't tested very extensively...

On 07.02.2018 16:31, Kashyap Chamarthy wrote: > [Cc: KVM upstream list.] > > On Tue, Feb 06, 2018 at 04:11:46PM +0100, Florian Haas wrote: >> Hi everyone, >> >> I hope this is the correct list to discuss this issue; please feel >> free to redirect me otherwise. >> >> I have a nested virtualization setup that looks as follows: >> >> - Host:

...the same state. > This way I can reset the VMs without having to reboot them (booting is > rather slow). > > I practice I'll probably have ~16 instances at the same time. > Constantly being reset to the same state. > I tried with QEMU, and it's seems totally doable with savevm, copy > file, then doing loadvm twice in parallel. > (I'll be using a separate network for each VM, so I can be sure which > one I'm talking to). Well, as long as they're completely isolated from each other, you may have a better chance of success. However there will still...

...support for nested VMX yet. So as > soon as your guest is using VMX itself ("nVMX"), this is not expected to > work. Hi David, thanks for getting back to us on this. I see your point, except the issue Kashyap and I are describing does not occur with live migration, it occurs with savevm/loadvm (virsh managedsave/virsh start in libvirt terms, nova suspend/resume in OpenStack lingo). And it's not immediately self-evident that the limitations for the former also apply to the latter. Even for the live migration limitation, I've been unsuccessful at finding documentation that w...

...eset the VMs without having to reboot them (booting is >>> rather slow). >>> >>> I practice I'll probably have ~16 instances at the same time. Constantly >>> being reset to the same state. >>> I tried with QEMU, and it's seems totally doable with savevm, copy file, >>> then doing loadvm twice in parallel. >>> (I'll be using a separate network for each VM, so I can be sure which one >>> I'm talking to). >>> >> >> Well, as long as they're completely isolated from each other, you may have &g...

On Mon, Apr 18, 2016 at 10:05:02PM +0300, Michael Ravits wrote: >Hi Jonas, > >I asked a similar question here last week. You could find it by searching >for this topic in the mailing list archives: "Clone VM with saved state". >That being said I'd be very glad if you could update here when you find a >complete solution. > >- Michael > What I *think* Jones

...ces-state" Set runstate to INMIGRATE earlier xen: record physmap changes to xenstore docs/xen-save-devices-state.txt | 34 +++++++++++++ hw/cirrus_vga.c | 4 -- qapi-schema.json | 19 +++++++ qmp-commands.hx | 27 ++++++++++ savevm.c | 71 ++++++++++++++++++++++++++ vl.c | 2 +- xen-all.c | 104 ++++++++++++++++++++++++++++++++++++++- xen-mapcache.c | 22 +++++++- xen-mapcache.h | 9 +++- 9 files changed, 280 i...