From: Christoph Hellwig <hch@lst.de>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, hch@lst.de
Subject: Re: [Qemu-devel] QEMU online guest disk resize wrt host block devices
Date: Thu, 1 Sep 2011 17:56:20 +0200 [thread overview]
Message-ID: <20110901155620.GB11219@lst.de> (raw)
In-Reply-To: <20110901142735.GI14462@redhat.com>
On Thu, Sep 01, 2011 at 03:27:35PM +0100, Daniel P. Berrange wrote:
> One other question too, when creating a qcow2 image via 'qemu-img create'
> you can specify a 'prealloc' option to require metadata to be allocated
> at time of creation.
>
> Should we have the same control at time of resize too. If the app had
> originally created the qcow2 image with preallocated metadata, then
> I'd expect they want to pre-allocate metadata when extending it too,
> or is there no additional metadata allocation required when extending
> an image ?
Sounds reasonable. Keving, is there a sane way to implement this?
>
>
> Daniel
> --
> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org -o- http://virt-manager.org :|
> |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
---end quoted text---
next prev parent reply other threads:[~2011-09-01 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 13:27 [Qemu-devel] QEMU online guest disk resize wrt host block devices Daniel P. Berrange
2011-09-01 14:05 ` Christoph Hellwig
2011-09-01 14:30 ` Daniel P. Berrange
2011-09-01 15:55 ` Christoph Hellwig
2011-09-02 15:00 ` Daniel P. Berrange
2011-09-07 11:02 ` [Qemu-devel] [PATCH] block: allow resizing of images residing on host devices Christoph Hellwig
2011-09-09 9:37 ` Kevin Wolf
2011-09-01 14:27 ` [Qemu-devel] QEMU online guest disk resize wrt host block devices Daniel P. Berrange
2011-09-01 15:56 ` Christoph Hellwig [this message]
2011-09-05 13:03 ` 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=20110901155620.GB11219@lst.de \
--to=hch@lst.de \
--cc=berrange@redhat.com \
--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).