qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] block/vpc: give option to force the current_size field in .bdrv_create
Date: Wed, 24 Feb 2016 14:07:18 +0100	[thread overview]
Message-ID: <20160224130718.GE4485@noname.redhat.com> (raw)
In-Reply-To: <E153A087-FB93-45F8-A0D2-5E4C236B5F55@kamp.de>

Am 24.02.2016 um 13:44 hat Peter Lieven geschrieben:
> if the size is forced I would set the chs values to max. this way no
> new creator String is needed and it is even backwards compatible. this
> is what disk2vhd does.

Does disk2vhd do it this way even if the size is smaller than the
maximum that can be represented with CHS?

> > Am 24.02.2016 um 13:24 schrieb Jeff Cody <jcody@redhat.com>:
> > 
> >> On Wed, Feb 24, 2016 at 11:19:37AM +0100, Kevin Wolf wrote:
> >> Am 24.02.2016 um 01:47 hat Jeff Cody geschrieben:
> >>> When QEMU creates a VHD image, it goes by the original spec,
> >>> calculating the current_size based on the nearest CHS geometry (with an
> >>> exception for disks > 127GB).
> >>> 
> >>> Apparently, Azure will only allow images that are sized to the nearest
> >>> MB, and the current_size as calculated from CHS cannot guarantee that.
> >>> 
> >>> Allow QEMU to create images similar to how Hyper-V creates images, by
> >>> setting current_size to the specified virtual disk size.  This
> >>> introduces an option, force_size, to be passed to the vpc format during
> >>> image creation, e.g.:
> >>> 
> >>>    qemu-img convert -f raw -o force_size -O vpc test.img test.vhd
> >>> 
> >>> Bug reference: https://bugs.launchpad.net/qemu/+bug/1490611
> >>> 
> >>> Signed-off-by: Jeff Cody <jcody@redhat.com>
> >> 
> >> We need to set a different creator string here that makes vpc_open()
> >> recognise the image as current_size based.
> >> 
> >> Kevin
> > 
> > How about "qem2"?  I initially thought about just changing the case on
> > "qemu", but I was afraid some other software may treat the app creator
> > string as case-insensitive.
> > 
> > I'll also update patch 1, to recognize that string as well.

I had the same thoughts about our options, and I wasn't fully convinced
of either, so I didn't propose any. I was leaning towards the case
change, though, as I don't think it should make a difference and it
reads nicer. But "qem2" is okay with me, too.

Kevin

  reply	other threads:[~2016-02-24 13:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  0:47 [Qemu-devel] [PATCH 0/4] VHD/VPC format compatibility Jeff Cody
2016-02-24  0:47 ` [Qemu-devel] [PATCH 1/4] block/vpc: choose size calculation method based on creator_app field Jeff Cody
2016-02-24  0:47 ` [Qemu-devel] [PATCH 2/4] block/vpc: tests for auto-detecting VPC and Hyper-V VHD images Jeff Cody
2016-02-24 10:23   ` Kevin Wolf
2016-02-24 12:19     ` Jeff Cody
2016-02-24 15:40     ` Jeff Cody
2016-02-24 15:44       ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-02-24 15:47         ` Jeff Cody
2016-02-24 15:49       ` Max Reitz
2016-02-24  0:47 ` [Qemu-devel] [PATCH 3/4] block/vpc: give option to force the current_size field in .bdrv_create Jeff Cody
2016-02-24 10:19   ` Kevin Wolf
2016-02-24 12:24     ` Jeff Cody
2016-02-24 12:44       ` Peter Lieven
2016-02-24 13:07         ` Kevin Wolf [this message]
2016-02-24 13:40           ` Jeff Cody
2016-02-24 19:28             ` Peter Lieven
2016-02-24 21:17               ` Jeff Cody
2016-02-24 19:29           ` Peter Lieven
2016-02-24  0:47 ` [Qemu-devel] [PATCH 4/4] block/vpc: add tests for image creation force_size parameter 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=20160224130718.GE4485@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=jcody@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).