From: Eric Blake <eblake@redhat.com>
To: 吴志勇 <zhiyong.wzy@alibaba-inc.com>, libguestfs <libguestfs@redhat.com>
Cc: "zwu.kernel" <zwu.kernel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Why is virt-resize designed to involve two disks?
Date: Tue, 23 Sep 2014 11:01:20 -0600 [thread overview]
Message-ID: <5421A760.5050906@redhat.com> (raw)
In-Reply-To: <d20fe438-1596-4075-85d7-d2b901976d59@alibaba-inc.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On 09/23/2014 04:15 AM, 吴志勇 wrote:
> HI,
[please configure your mailer to wrap long lines]
> As you've known, vhd-util and qemu-img both provide the capacity for
resizing the original disk, but why is virt-resize designed to involve
two disks, not only original disk? Is there any concern? Is it possible
that only one original disk is involved in virt-resize?
virt-resize is part of libguestfs, and as such is not maintained on this
list. You'll get better answers about why virt-resize does not support
in-place resizing by asking on that list. But the answer probably
involves the fact that virt-resize is doing MUCH more than resizing the
block device - it is also copying entire filesystems from the old
location to the new resized location for optimal initial placement.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
prev parent reply other threads:[~2014-09-23 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 10:15 [Qemu-devel] Why is virt-resize designed to involve two disks? 吴志勇
2014-09-23 17:01 ` Eric Blake [this message]
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=5421A760.5050906@redhat.com \
--to=eblake@redhat.com \
--cc=libguestfs@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhiyong.wzy@alibaba-inc.com \
--cc=zwu.kernel@gmail.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.