similar to: unattended cloning

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. The Changelog of qemu-2.0.0 mentioned "Live snapshot merging". Someone has an idea what could be ment by this? I'm asking because i'm still struggling with finding a reliable backup solution for running kvm machines. Blockcopy is my current solution. best regards Thomas

Hello, I recently compiled libvirt 1.0.1 and qemu 1.3.0 on Ubuntu 12.04. I have performed live snapshots on VMs using "virsh snapshot-create-as" and then later re-merge the images together using "virsh blockpull". I am wondering how I can do a couple of other operations on the images while the VM is running. For example, VM1 is running from the snap3 image, with the following

Am 10.06.13 10:40, schrieb Kashyap Chamarthy: > On 06/10/2013 01:20 PM, Thomas Stein wrote: >> Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >>> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>>> Hello. >>>> >>>> I just tried the following: >>>> >>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml

All, I have a service that takes new live KVM snapshots Si regularly, keeps a fixed number N (Si ,..,Si-N+1), and therefore needs to delete Si-N in this cycle. Until libvirt includes support for this capability that is said to be available in qemu, what is a safe workflow to delete old live KVM snapshots w/o losing data. Do I need to pause/shut down the VM? The development environment is

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

Please can someone take a look at the attached file which shows the output on my machine of zfs list -r -t filesystem,snapshot -o space rpool/export/home/matt The USEDDS figure of ~2GB is what I would expect, and is the same figure reported by the Disk Usage Analyzer. Where is the remaining 13.8GB USEDSNAP figure coming from? If I total up the list of zfs-auto snapshots it adds up to about 4.8GB,

Hi all, I have a kvm virtual machine running (qemu version 2.0), and I had took several external snapshots of the disk( using "virsh snapshot-create-as"). Now, the existed disk files relationship look like: base <- snap1 <-snap2 <- current using disk file. Now I want to remove snap1 and snap2, and let current disk using the base image file as back file directly. Unfortunately,

> virsh dumpxml --security-info dom > dom.xml > virsh undefine dom Hello. Someone was talking about this (undefining the VM) would not be neccessary anymore when qemu-1.5 has been released. Is that true? > virsh blockcopy dom vda /path/to/backup-vda > polling loop - check periodically until 'virsh blockjob dom vda' > shows 100% completion > virsh suspend

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:

What ''verbose information'' is reported by the "zfs send -v <snapshot>" contain? Also on Solaris 10u6 I don''t get any output at all - is this a bug? Regards, Nick -- This message posted from opensolaris.org

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

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

Il 13/01/2015 10:51, Kashyap Chamarthy ha scritto: > On Tue, Jan 13, 2015 at 10:10:53AM +0100, Fiorenza Meini wrote: >> Hi there, >> I receive this error when I run nova image-create <VM name> <Vm Sanpshot >> name>: > > Okay, you're talking in the context of OpenStack. > > You can also check the Nova compute.log for more contextual details of >

Am 02.07.13 15:42, schrieb Eric Blake: > On 07/02/2013 06:55 AM, Thomas Stein wrote: >> >>> virsh dumpxml --security-info dom > dom.xml >>> virsh undefine dom >> >> Hello. >> >> Someone was talking about this (undefining the VM) would not be >> neccessary anymore when qemu-1.5 has been released. Is that true? > > Undefining

Hi there, I receive this error when I run nova image-create <VM name> <Vm Sanpshot name>: Exception during message handling: block copy still active: domain has active block job In libvirt log file I can see: error : qemuDomainDefineXML:6312 : block copy still active: domain has active block job Libvirt is 1.2.7 version, linux system is Debian Wheezy Please, what does it mean ?

On 09/16/2014 01:19 AM, Adam King wrote: > 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

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