similar to: Clone VM with saved state

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 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?

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

Hi everyone! I use the libvirt(version: 1.2.2) and QEMU(version: 2.2.1) to test qemu snapshot features: I tried virsh blockcommit when VM offline, the virsh blockcommit failed: the error messase as below: error: Requested operation is not valid: domain is not running when I start the VM, the virsh blockcommit work fine! my question is：we need

Hi Kashyap Chamarthy: thank you very much for answer my question: 一： lead to VM filesystem becoming read-only 1： test case it lead to VM filesystem becoming read-only test case as follows: we want to snapshot for VM , to obtain VM incremental data，and use virsh blockcommit，qemu-img commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the

Hi , Working on the simple POC : Advanced snapshot using libvirt and qemu . Following are the exact steps which are followed . 1. Created as base VM - Ubuntu 15.10 with following libvirt and qemu versions Using library: libvirt 1.2.16 Using API: QEMU 1.2.16 Running hypervisor: QEMU 2.3.0 QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9.1), Copyright (c) 2003-2008 Fabrice

Morning, I have a KVM guest running Win 2012 with MS SQL 2012. In order to provide a quick method of restoring the service should the live server die, we've decided to clone it to a preserved state. Ideally, this clone should also be kept up to date and cloning should be done on a regular basis. Is there any reason not to do unattended cloning? As in, when I leave on a Friday afternoon,

Versions -------- (Libvirt locally built from a recent git commit -ec7b922): $ rpm -q libvirt-daemon-kvm qemu-system-x86 libvirt-daemon-kvm-1.2.6-1.fc20.x86_64 qemu-system-x86-2.0.0-1.fc21.x86_64 Test ---- [All images are qcow2 files.] We have this simple chain: base <- snap1 Let's quickly examine the contents of 'base' and 'snap1' images:

Hi,guys I wanna to get the disk snapshot size, but found nothing libvirt commands related,except qemu-img. I create two disk snapshots, but nothing return its' size [root@cskvm01 qcow2]# qemu-img info /mnt/e6758700-af68-3c06-ade3-53f5f9b93507/e2cf6551-0d2c-4382-a86c-8ba633954ff2 image: /mnt/e6758700-af68-3c06-ade3-53f5f9b93507/e2cf6551-0d2c-4382-a86c-8ba633954ff2 file format: qcow2 virtual

Thanks for your answer, 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. I have already try to create snapshot of disk, which is not problem. I use qcow2 format, and create new disk image using original disk image as backing file. But still I am not able to assign state of vm with new disk. I have found

Hello, I am working on my PhD thesis and it would be really helpfull if someone could advise me, whether can Virsh create snapshots of VMs using copy-on-write. Thanks for reply. Juraj

Dear all, Please let me start by indicating that I am not from a technical background, so please be gentle and patient with me. I am trying to get a snapshot from my virtual machines (vm) and the following command works for all of them bar one: # virsh snapshot-create-as --quiesce --no-metadata --domain myvm myvm-state --diskspec vda,file=overlay.qcow2 --disk-only --atomic The only exception is

Hi (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file

Hello, 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 multiple disks, I'd like to back them up individually with separate calls to snapshot-create-as, so I can more easily manage the disk images. The code I have now is essentially as follows: virsh snapshot-create-as --domain "vmname" --name

I have used virsh snapshot-create-as <VM name> <snapshot name> "<snapshot description>" --diskspec "vda,snapshot=external,file=/path/to/external-snapshot" --disk-only --atomic to create an external snapshot of a running VM. I followed it with virsh blockpull <VM name> --path /path/to/external-snapshot and monitored it until done.

Hello Thanks heaps for your suggestions. responses inline. On 10 Apr 2014, at 10:34 pm, Eric Blake <eblake@rehost1hat.com> wrote: > > [ … ] > [Can you convince your mailer to wrap long lines? It makes it easier > for other readers] I’ll try and keep the lines short. I don’t see any obvious setting to change the wrap. >> >> Using RHEL 6.4 and libvirt version

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

Hello, I have a running transient domain with a storage volume that utilizes a backing file (both QCOW2 format). I'd like to capture the disk and memory state of the domain preferably to external file(s) (which I understand is an 'external checkpoint'), so that other independent domains can be instantiated and effectively "resumed" from this point-in-time profile. My

Versions: $ rpm -q libvirt-daemon-kvm qemu-system-x86 libvirt-daemon-kvm-1.2.9-3.fc21.x86_64 qemu-system-x86-2.1.2-4.fc21.x86_64 When I attempt to revert to an internal snapshot: $ virsh snapshot-list node1 Name Creation Time State ------------------------------------------------------------ snap1 2014-06-03 14:07:28 -0400 running $

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