Ross Boylan wrote:
Or do you mean I should back each virtual disk with an LVM volume?
Yes, this option is what was meant.
That does seem cleaner; I've just been following the docs and they use regular files. They say I can't just use a raw partition, but maybe kvm-img -f qcow2 /dev/MyVolumeGroup/Volume10 ?
While new versions of qcow2 have some extensions that let the last-written sector be tracked for use on device-backed partitions, the expectation is that you'll (really) just use the raw partition; qcow2 more than takes back the performance gain from getting your host filesystem out of the loop.
I'm not sure how growing the logical volume would interact with qcow...
Right -- folks doing this route go raw rather than qcow, so it's just a matter of resizing the partitions / filesystems within the guest.
-- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
