qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] Make default invocation of block drivers safer
Date: Thu, 15 Jul 2010 19:10:25 +0200	[thread overview]
Message-ID: <4C3F4101.8070005@redhat.com> (raw)
In-Reply-To: <4C3F355E.3020800@codemonkey.ws>

Am 15.07.2010 18:20, schrieb Anthony Liguori:
> I have another idea that I hope will solve the problem in a more 
> complete way.  The fundamental issue is that it's impossible to probe 
> raw images reliably.  We can probe qcow2, vmdk, etc but not raw.
> 
> So, let's do the following: have raw_probe() always fail.  Probing 
> shouldn't be a heuristic, it should be an absolute.  We can't prove it's 
> a raw image, so we should always fail.
> 
> To accomodate current use-cases with raw, let's introduce a new format 
> called "probed_raw".  probed_raw's semantics will be the following:
> 
> The signature of a probed_raw will be ~{'QFI\xfb', 'VMDK', 'COWD', 
> 'OOOM', ...}.  If the signature is 'QRAW', then instead of reading the 
> first sector at offset 0, we read the first sector at offset LENGTH.  If 
> the signature is 'QRAW', LENGTH is computed by calculating FILE_SIZE - 512.
> 
> For probed_raw, write requests to sector 0 are checked.  If the first 
> four bytes is an invalid probed_raw signature or QRAW, we write a QRAW 
> signature to file offset 0 and copy the first sector to the end of the 
> file redirecting reads and writes to the end of file.
> 
> An approach like this has the following properties:
> 
> 1) We can make the bdrv_probe check 100% reliable and return a boolean.
> 2) In the cases where we known format=raw, none of this code is ever 
> invoked.
> 3) probed_raw images usually look exactly like raw images in most cases
> 4) In the degenerate cases, probe_raw images are still mountable in the 
> normal way.
> 5) Even after the QRAW signature is applied, if the guest writes a valid 
> signature, we can truncate the file and make it appear as a normal raw 
> image.
> 
> Christoph/Markus/Stefan, does this seem like a more reasonable approach?

I hope I may answer even though you didn't ask me. ;-)

This qraw format you introduce is a weird thing, mainly because
depending on a signature the first sectors moves to somewhere completely
else.

If we want to introduce something, that's _almost_ raw and that we can
use by default, what about doing something similar to what statically
sized VHD images look like: take a raw image and attach a footer? With
this approach you should still be able to mount it in the host etc. We
could automatically append this footer when opening a probed qraw image r/w.

Kevin

  reply	other threads:[~2010-07-15 17:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 16:12 [Qemu-devel] [PATCH] Make default invocation of block drivers safer Anthony Liguori
2010-07-14 16:42 ` [Qemu-devel] " Kevin Wolf
2010-07-14 17:40   ` Anthony Liguori
2010-07-15  8:00     ` Kevin Wolf
2010-07-14 18:43 ` [Qemu-devel] " Christoph Hellwig
2010-07-14 18:50   ` Anthony Liguori
2010-07-15  9:20     ` Daniel P. Berrange
2010-07-15 12:35       ` Anthony Liguori
2010-07-15 15:19     ` Markus Armbruster
2010-07-15 16:20       ` Anthony Liguori
2010-07-15 17:10         ` Kevin Wolf [this message]
2010-07-15 17:51           ` Anthony Liguori
2010-07-16  7:30             ` Kevin Wolf
2010-07-16 12:55         ` Stefan Hajnoczi
2010-07-16 13:00           ` Stefan Hajnoczi
2010-07-16 16:06         ` Markus Armbruster
2010-07-16 16:16           ` Anthony Liguori
2010-07-16 16:24             ` Kevin Wolf
2010-07-14 18:53   ` Anthony Liguori
2010-07-14 18:54   ` Aurelien Jarno
2010-07-14 19:04     ` Anthony Liguori
2010-07-15  8:09   ` Kevin Wolf
2010-07-15  9:10     ` Stefan Hajnoczi
2010-07-15 12:57       ` Anthony Liguori
2010-07-15 13:16         ` Kevin Wolf
2010-07-15 13:20         ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C3F4101.8070005@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=hch@lst.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).