[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Why is virt-resize designed to involve two disks?
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] Why is virt-resize designed to involve two disks? |
Date: |
Tue, 23 Sep 2014 11:01:20 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 |
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
signature.asc
Description: OpenPGP digital signature