qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vpc: Fix size in fixed image creation
Date: Wed, 11 Feb 2015 17:32:57 -0500	[thread overview]
Message-ID: <54DBD899.3030603@redhat.com> (raw)
In-Reply-To: <1423671745-31547-1-git-send-email-kwolf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On 2015-02-11 at 11:22, Kevin Wolf wrote:
> If total_sectors is rounded to match the geometry, total_size needs to
> be changed as well. Otherwise we end up with an image whose geometry
> describes a disk larger than the image file, which doesn't end well.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>   block/vpc.c | 10 +++-------
>   1 file changed, 3 insertions(+), 7 deletions(-)

Looks fine to me, but the spec says: "When the user creates a hard disk 
of a certain size, the size of the hard disk image in the virtual 
machine is smaller than that created by the user. This is because CHS 
value calculated from the hard disk size is rounded down."

So, well, qemu has been violating the specification all along, I guess.

So, with that in mind (that nobody has been screaming so far):

Reviewed-by: Max Reitz <mreitz@redhat.com>

Alternatively we may want to "fix" it, and actually let the CHS size be 
smaller than total_sectors/total_size, if that's possible. But maybe 
that'll be even worse, so I'm fine either way.

[-- Attachment #2: Type: text/html, Size: 2269 bytes --]

  reply	other threads:[~2015-02-11 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 16:22 [Qemu-devel] [PATCH] vpc: Fix size in fixed image creation Kevin Wolf
2015-02-11 22:32 ` Max Reitz [this message]
2015-02-12  9:50   ` Kevin Wolf
2015-02-16 10:20 ` Kevin Wolf

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=54DBD899.3030603@redhat.com \
    --to=mreitz@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 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).