similar to: Copy VM in running-snapshoted state to another host

On 05/23/2014 08:41 AM, Andrew Martin wrote: >> >> Any reason you aren't upgrading to newer versions? Although these seem >> sufficient for what you are trying. > The VM hosts I'm using all run Ubuntu 12.04 and I haven't had time to backport > and test newer versions yet. I've published the latest versions I built in this > PPA:

> >> --live only makes sense when mixed with memory snapshots (with --memspec); > >> but > >> as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if > >> it > >> will error out as mutually exclusive or just be silently ignored, > >> without reading the code). > > I'm using this code in a script for creating

Hi Kashyap, Thanks for your answer! Unfortunately my use case requires cloning the exact memory state, so I won't be able to use virt-sysprep. But the snapshot command looks like something I could use. Could you suggest how to proceed and create/start a new vm from that snapshot? Thanks, Michael On Tue, Apr 12, 2016 at 2:37 PM, Kashyap Chamarthy <kchamart@redhat.com> wrote: > On

On Mon, Apr 11, 2016 at 12:01:08PM +0300, Michael Ravits wrote: > Hi, > > My use case involves creating duplicates of saved virtual machines. While I realize you want to trivially clone VMs with some state at random point in time, you might want to look into `virt-builder` about cloning VMs. It has some sensible advice: http://libguestfs.org/virt-builder.1.html#clones Using

On Tue, Apr 12, 2016 at 03:15:16PM +0300, Michael Ravits wrote: > Hi Kashyap, > > Thanks for your answer! > > Unfortunately my use case requires cloning the exact memory state, so I > won't be able to use virt-sysprep. > But the snapshot command looks like something I could use. > Could you suggest how to proceed and create/start a new vm from that > snapshot?

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

On 3/23/2015 12:49 PM, Michal Privoznik wrote: > On 23.03.2015 16:02, Fiorenza Meini wrote: >> Hi there, >> I'm running KVM under Openstack . >> >> When I give virsh list command, I see some VM in NON persistent state. >> What does it mean? How can I move it to a persisten state ? > You can do that by running: > > virsh dumpxml $dom > dom.xml

On 08/20/2013 09:13 AM, Tobias Brunner wrote: > Hi, > > Thanks a lot for the answer. > >> An internal snapshot of a VM requires that the VM has at least one disk >> using a QCOW2 volume or similar. The memory state is saved in that >> image. Your VM has only a RAW disk image and thus it can't be used for >> internal snapshot. > > Ok, that makes

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still

All, Using Centos 6.4 with provided libvirt: [root@node1 ~]# rpm -q libvirt libvirt-1.0.1-2.el6.x86_64 Assume a VM with one or more live snapshots. In virsh the VM snapshots can be listed. With virsh: - Stop and undefine this VM. - Then define (and start) this VM. The new VM does not have the list of snapshots. Is there a way with virsh to rebuild the metadata such that

[dropping multiple lists; let's just use libvirt-users] On 02/11/2015 02:45 PM, Edward Young wrote: > I perform a simple test, but failed. > > In the source, I create: base <- mid <- active (2 snapshots, the active > one is the current one) > In order to migrate this vm to the destination, I manually copy both base > and mid to the destination, and put them in the

>>> External snapshots (via the blockdev-snapshot-sync QMP command) can be >>> taken in a matter of milliseconds if you only care about disk state. >>> Furthermore, if you want to take a snapshot of both memory and disk >>> state, such that the clone can be resumed from the same time, you can do >>> that with a guest downtime that only lasts as long as

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

Hi, My use case involves creating duplicates of saved virtual machines. Tried with virt-manager and with virsh but so far it seems like this case is not supported by these tools. Does anyone know how I could achieve the above? Thanks, Michael

Hi, I have a win10 guest on a fedora32 system and have some questions as I explore using external snapshots as a form of backup in case of a Windows failure (as in, it won't boot or is completely irrecoverable) as well as revision control (to be able to rollback changes after a failed app install, etc). The first hit on Google for external snapshots involves a RHEL7 document that talks

So I notice that some operations by libvirt such as creating a snapshot actually change the source of the active disk image for a domain without requiring a restart of the vm. How can this be achieved manually? There are instances where I am manipulating files with qemu-img or virsh commands and afterward need to change what file the vm is using as its disk. One example is when deleting a

On 12/04/2013 08:29 AM, Juraj Melo wrote: > Thanks for your answer, [please don't top-post on technical lists, and use proper in-reply-to headers to keep things properly threaded] > > I am trying to make a snapshot of whole virtual machine (disk, CPU > state, memory). But I need to make this snapshot in matter of seconds. This is possible using external snapshots with memory,

On 05/22/2014 04:31 PM, Andrew Martin wrote: > Hello, > [Can you convince your mailer to wrap long lines?] > I am working on a script to automatically create live snapshots of > running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has Any reason you aren't upgrading to newer versions? Although these seem sufficient for what you are trying. > multiple disks, I'd

On 05/23/2014 12:16 PM, Andrew Martin wrote: >> --quiesce requires the guest to be running to work, while --memspec >> forceably stops the guest (the migration algorithm must pause, even if >> --live minimizes the pause to a fraction of a second). > Would calling snapshot-create-as with --disk-only and --quiese still succeed > on a VM that is stopped (since the disk would