Thank you Stefan that does clarify on how to correctly use "qemu-img commit "
Regards
sl
--- On Fri, 11/3/11, Stefan Hajnoczi wrote:
From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] Issue with snapshot outside qcow2 disk - qemu 0.14.0
To: "SAURAV LAHIRI"
Cc: "J
Sorensen
Subject: Re: [Qemu-devel] Issue with snapshot outside qcow2 disk - qemu 0.14.0
To: "SAURAV LAHIRI"
Cc: "Stefan Hajnoczi" , qemu-devel@nongnu.org
Date: Friday, 11 March, 2011, 5:50
On 03/11/11 10:39, SAURAV LAHIRI wrote:
> Thank you Stefan, Jes. So it appears that sna
On Fri, Mar 11, 2011 at 9:50 AM, Jes Sorensen wrote:
> On 03/11/11 10:39, SAURAV LAHIRI wrote:
>> Thank you Stefan, Jes. So it appears that snapshot_blkdev is the way
>> to go for vm disk backup with running vms.
>>
>> In regard to merging changes, assuming that we go snapshot_blkdev
>> rightaway.
On 03/11/11 10:39, SAURAV LAHIRI wrote:
> Thank you Stefan, Jes. So it appears that snapshot_blkdev is the way
> to go for vm disk backup with running vms.
>
> In regard to merging changes, assuming that we go snapshot_blkdev
> rightaway. Stefan's suggestion: "qemu-img commit" Jes's suggestion:
>
the "live merge" will be
available.
Thanks and Regards
Saurav Lahiri
--- On Fri, 11/3/11, Jes Sorensen wrote:
From: Jes Sorensen
Subject: Re: [Qemu-devel] Issue with snapshot outside qcow2 disk - qemu 0.14.0
To: "Stefan Hajnoczi"
Cc: "SAURAV LAHIRI" , qemu-dev
On 03/10/11 22:04, Stefan Hajnoczi wrote:
> On Thu, Mar 10, 2011 at 7:57 PM, SAURAV LAHIRI
> wrote:
>> The high level use case is that of being able to backup user specified disks
>> of a VM without having to bring down the VM.
>
> Excellent, that sounds exactly like Jes is addressing so future
On Thu, Mar 10, 2011 at 7:57 PM, SAURAV LAHIRI wrote:
> The high level use case is that of being able to backup user specified disks
> of a VM without having to bring down the VM.
Excellent, that sounds exactly like Jes is addressing so future
QEMU/KVM releases will hopefully have the live snaps
is able to connect. But since my
current environment does use libvirt, shutting down libvirt is not an option.
Is there any way around this ?
Appreciate your help.
Regards
sl
--- On Thu, 10/3/11, Jes Sorensen wrote:
From: Jes Sorensen
Subject: Re: [Qemu-devel] Issue with snapshot out
On 03/10/11 10:58, Stefan Hajnoczi wrote:
> On Thu, Mar 10, 2011 at 9:32 AM, Jes Sorensen wrote:
>> On 03/10/11 10:27, Stefan Hajnoczi wrote:
>>> I have CCed Jes who has been working on a live snapshot mechanism. He
>>> recently added the snapshot_blkdev monitor command that takes a
>>> snapshot
On Thu, Mar 10, 2011 at 9:32 AM, Jes Sorensen wrote:
> On 03/10/11 10:27, Stefan Hajnoczi wrote:
>> I have CCed Jes who has been working on a live snapshot mechanism. He
>> recently added the snapshot_blkdev monitor command that takes a
>> snapshot of a block device while the VM is running. A ne
On 03/10/11 10:27, Stefan Hajnoczi wrote:
>> Is Scenario 2 safe where in the copying the snapshot outside the original
>> qcow2 is being executed with the VM running. This is because if this is safe
>> then this could be an approach as it would not require a long downtime for
>> the VM.
>
> The
On Thu, Mar 10, 2011 at 1:51 AM, SAURAV LAHIRI wrote:
> Scenario 1:
> 1) I executed following with the vm in shutdown state.
> "#qemu-img snapshot -c snap1 /home/user1/lucid-vm2"
Here you are snapshotting the current disk image and storing the
snapshot away as "snap1".
> 2) Brought the VM Up.
>
be an approach as it would not require a long downtime for the VM.
Regards
sl
--- On Wed, 9/3/11, Stefan Hajnoczi wrote:
From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] Issue with snapshot outside qcow2 disk - qemu 0.14.0
To: "SAURAV LAHIRI"
Cc: qemu-devel@nongnu.org
Date: Wednesday, 9 M
On Wed, Mar 9, 2011 at 6:06 PM, SAURAV LAHIRI wrote:
> Following steps were executed to copy a snapshot outside the original qcow2
> but looks like there is an issue.
>
> 1. VM(vm1) brought up with a qcow2 image(/home/user1/lucid-vm2). This is a
> lucid 10.04 VM.
>
> 2. Next snapshot created for
Hello,
I attempted to create snapshots outside the original qcow2 disk, a feature that
is available with 0.14.0, but facing an unexpected behaviour as described
below. Any help is greatly appreciated.
I am using qemu version 0.14
# qemu --version
QEMU emulator version 0.14.0, Copyright (c) 2003
15 matches
Mail list logo
