Yes, it does appear, you just need to make vvfat rw:
$ qemu-system-x86_64 -drive file.driver=vvfat,file.dir=foo,file.rw=on
vvfat foo chs 1024,16,63
WARNING: Image format was not specified for 'json:{"dir": "foo", "driver":
"vvfat", "rw": "on"}' and probing guessed raw.
Automatically
Looking through old bug tickets... can you still reproduce this bug
with the latest version of QEMU? At least for vvfat, the warning message
does not seem to occur anymore.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of
> I could actually see the use of non-raw over NBD. We support nested
> protocols (where you can use qcow2->qcow2->file), that is, where a file
> contains a qcow2 file whose contents are themselves a qcow2 image.
> (Perhaps useful in nested guests, where the outer qcow2 layer serves a
> disk to
On Wed, Jul 15, 2015 at 10:54:47AM -0600, Eric Blake wrote:
On 07/15/2015 09:42 AM, Max Reitz wrote:
Hi,
Indeed using non-raw images should not be used over NBD. The warning
however is not superfluous, since qemu does indeed probe the image
format, so a malicious guest might write a
On 07/15/2015 09:42 AM, Max Reitz wrote:
Hi,
Indeed using non-raw images should not be used over NBD. The warning
however is not superfluous, since qemu does indeed probe the image
format, so a malicious guest might write a qcow2 header into the raw
image, thus making qemu probe a qcow2
Hi,
Indeed using non-raw images should not be used over NBD. The warning
however is not superfluous, since qemu does indeed probe the image
format, so a malicious guest might write a qcow2 header into the raw
image, thus making qemu probe a qcow2 image the next time the same
configuration is
