All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: jcody@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH] vpc: Ignore geometry for large images
Date: Tue, 10 Feb 2015 12:41:46 +0100	[thread overview]
Message-ID: <54D9EE7A.9050802@kamp.de> (raw)
In-Reply-To: <1423498163-2001-1-git-send-email-kwolf@redhat.com>

Am 09.02.2015 um 17:09 schrieb Kevin Wolf:
> The CHS calculation as done per the VHD spec imposes a maximum image
> size of ~127 GB. Real VHD images exist that are larger than that.
>
> Apparently there are two separate non-standard ways to achieve this:
> You could use more heads than the spec does - this is the option that
> qemu-img create chooses.
>
> However, other images exist where the geometry is set to the maximum
> (65536/16/255), but the actual image size is larger. Until now, such
> images are truncated at 127 GB when opening them with qemu.
>
> This patch changes the vpc driver to ignore geometry in this case and
> only trust the size field in the header.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>
> Peter, I'm replacing some of your code in the hope that the new approach
> is more generally valid. Of course, I haven't tested if your case with
> disk2vhd is still covered. Could you check this, please?

I checked this and found that disk2vhd always sets CHS to 65535ULL * 16 * 255
independed of the real size.

But, as the conversion to CHS may have an error its maybe the best solution
to ignore CHS completely and always derive total_sectors from footer->size unconditionally.

I had a look at what virtualbox does and they only rely on footer->size. If they
alter the size or create an image the write the new size into the footer and recalculate
CHS by the formula found in the appendix of the original spec.

Check vhdCreateImage, vhdOpen in http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Storage/VHD.cpp

The original spec also says that CHS values purpose is the use in an ATA controller only.

Peter


>
>   block/vpc.c | 10 ++++------
>   1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/block/vpc.c b/block/vpc.c
> index 46803b1..00409a6 100644
> --- a/block/vpc.c
> +++ b/block/vpc.c
> @@ -215,12 +215,10 @@ static int vpc_open(BlockDriverState *bs, QDict *options, int flags,
>       bs->total_sectors = (int64_t)
>           be16_to_cpu(footer->cyls) * footer->heads * footer->secs_per_cyl;
>   
> -    /* images created with disk2vhd report a far higher virtual size
> -     * than expected with the cyls * heads * sectors_per_cyl formula.
> -     * use the footer->size instead if the image was created with
> -     * disk2vhd.
> -     */
> -    if (!strncmp(footer->creator_app, "d2v", 4)) {
> +    /* Images that have exactly the maximum geometry are probably bigger and
> +     * would be truncated if we adhered to the geometry for them. Rely on
> +     * footer->size for them. */
> +    if (bs->total_sectors == 65535ULL * 16 * 255) {
>           bs->total_sectors = be64_to_cpu(footer->size) / BDRV_SECTOR_SIZE;
>       }
>   


-- 

Mit freundlichen Grüßen

Peter Lieven

...........................................................

   KAMP Netzwerkdienste GmbH
   Vestische Str. 89-91 | 46117 Oberhausen
   Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
   pl@kamp.de | http://www.kamp.de

   Geschäftsführer: Heiner Lante | Michael Lante
   Amtsgericht Duisburg | HRB Nr. 12154
   USt-Id-Nr.: DE 120607556

...........................................................

  reply	other threads:[~2015-02-10 11:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 16:09 [Qemu-devel] [RFC PATCH] vpc: Ignore geometry for large images Kevin Wolf
2015-02-10 11:41 ` Peter Lieven [this message]
2015-02-10 13:34   ` Kevin Wolf
2015-02-10 13:42     ` Jeff Cody
2015-02-10 13:54       ` Kevin Wolf
2015-02-10 14:00         ` Peter Lieven
2015-02-10 14:53           ` Kevin Wolf
2015-02-12  9:23             ` Peter Lieven
2015-02-12  9:58               ` Kevin Wolf
2015-02-12 10:02                 ` Peter Lieven
2015-02-12 10:06                   ` Kevin Wolf
2015-02-12 10:09                     ` Peter Lieven
2015-02-12 10:23                       ` Kevin Wolf
2015-02-12 10:30                         ` Peter Lieven
2015-02-12 17:18                         ` Charles Arnold
2015-02-12 19:05                           ` Peter Lieven
2015-02-12 21:01                             ` Charles Arnold
2015-02-18 13:38                               ` Peter Lieven
2015-02-18 14:11                                 ` Eric Blake
2015-02-10 14:11         ` Jeff Cody

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=54D9EE7A.9050802@kamp.de \
    --to=pl@kamp.de \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.