CC to libvirt-users mail list
Thank you Eric
----- Original Message -----
| From: "Eric Blake" <eblake@redhat.com>
| To: "shyu" <shyu@redhat.com>
| Sent: Thursday, June 12, 2014 6:07:13 AM
| Subject: Re: a small problem about *Disk* type pool
|
| On 06/10/2014 09:23 PM, shyu wrote:
| > Hi Eric,
| >
| > There is a small problem about *Disk* type pool.
|
| This sort of question might be better on the libvirt-users mailing list,
| as it will reach a wider audience.
|
| >
| > On libvirt.org, the valid pool format type include "lvm2",
which was
| > introduce by commit c47884a. While "POOL_DISK_LVM2 can not be
created by
| > "parted mklabel" but is only returned from auto-detection on
disk
| > pools", should this word be added to the org in case of misleading
| > building a "lvm2" type pool?
|
| Yes, it might make sense to document that libvirt can't currently create
| lvm partitions automatically (but such support might be added in the
| future, if parted is enhanced, or if libvirt is taught to use lvm tools
| to do it).
|
| >
| > And, since lvm2 can't be create by parted mklabel, while when build
disk
| > type pool, libvirt call "parted", so how POOL_DISK_LVM2 was
created ?
|
| This particular enum value is used when reading a disk that was
| partitioned externally by some other tool, and already had an lvm
| partition on it (just because libvirt can't create it does not make it
| any less useful for libvirt to report that it exists).
|
| --
| Eric Blake eblake redhat com +1-919-301-3266
| Libvirt virtualization library http://libvirt.org
|
|
--
Regards
shyu
