On 07/09/2018 09:54, Peter Krempa wrote:
No, that is a supported configuration and even the security should not
create a problem here as we assume the backing image is raw in this
case. That is only a problem if you have a qcow2 image as the base
image.
Thanks for confirmation. I'll continue
On Thu, Sep 06, 2018 at 18:23:46 +0200, Gionatan Danti wrote:
> Il 06-09-2018 12:54 Peter Krempa ha scritto:
> > You forgot to specify the format of the backing file into the overlay
> > file (qemu-img option -F). Libvirt treats any unspecified format as raw
> > since it's not secure to do probing
Il 06-09-2018 12:54 Peter Krempa ha scritto:
You forgot to specify the format of the backing file into the overlay
file (qemu-img option -F). Libvirt treats any unspecified format as raw
since it's not secure to do probing of the format.
Hi, the immutable base file *was* a raw image. Then a qco
On Tue, Sep 04, 2018 at 17:32:49 +0200, Gionatan Danti wrote:
> Il 03-09-2018 13:14 Gionatan Danti ha scritto:
> > Hi list,
> > suppose I have an immutable (ie: due to a read-only snapshot) backing
> > file.
> >
> > After creating an overlay file with "qemu-img create -f qcow2 -o
> > backing_file=
Il 03-09-2018 13:14 Gionatan Danti ha scritto:
Hi list,
suppose I have an immutable (ie: due to a read-only snapshot) backing
file.
After creating an overlay file with "qemu-img create -f qcow2 -o
backing_file=/path/to/immutable/file.img current.qcow2", libvirt
refuse to start the virtual mach