On 13-05-15 04:45 AM, Stefan Hajnoczi wrote:
>
> $ qemu-img create -f qcow2 -b template.img vm001.qcow2
> $ qemu-img create -f qcow2 -b template.img vm002.qcow2
> $ qemu-img create -f qcow2 -b template.img vm003.qcow2
> $ ...launch vm001-vm002...
>
> This is safe.
Yes. This is exactly what I di
On Sun, May 12, 2013 at 11:43:31PM -, Brian J. Murrell wrote:
> On 13-05-12 05:14 PM, Michael Tokarev wrote:
> > First, having a single qcow2 file open for read-write access by more
> > than one process in unsupported.
>
> But I don't, if I understand how qcow2 snapshots work. Let me apologiz
First, having a single qcow2 file open for read-write access by more
than one process in unsupported.
Second, this version of qemu/kvm is too old to be supported upstream,
it's a few years old already and there has been *lots* of changes since
that version.
** Changed in: qemu
Status: New
On 13-05-12 05:14 PM, Michael Tokarev wrote:
> First, having a single qcow2 file open for read-write access by more
> than one process in unsupported.
But I don't, if I understand how qcow2 snapshots work. Let me apologize
if I was not clear. Each of the VMs have their own snapshot of the
common
