[Qemu-devel] Why is virt-resize designed to involve two disks?

[Qemu-devel] Why is virt-resize designed to involve two disks?

[吴志勇]

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

HI,
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?

-- 
Regards,
 
Zhi Yong Wu

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

Re: [Qemu-devel] Why is virt-resize designed to involve two disks?

[Eric Blake]

[-- 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 --]