kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* docs on storage pools?
@ 2009-10-02 20:04 Richard Wurman
  2009-10-04 22:10 ` Cole Robinson
  0 siblings, 1 reply; 2+ messages in thread
From: Richard Wurman @ 2009-10-02 20:04 UTC (permalink / raw)
  To: kvm

So far I've been using files and/or LVM partitions for my VMs --
basically by using virt-manager and modifying existing XML configs and
just copying my VM files to be reused.

I'm wondering how KVM storage pools work -- at first I thought it was
something like KVM's version of LVM where you can just dump all your
VMs in one space .. .but it looks like it's really means "different
places you want to store your VMs":

- dir: Filesystem Directory
- disk: Physical Disk Device
- fs: Pre-Formatted Block Device
- iscsi: iSCSI Target
-logical: LVM Volume Group
- netfs: Network exported directory

I understand things like LVM and storing VMs in a filesystem
directory.. but what real difference is there by going through the
GUI? I suppose nothing. Maybe I'm overthinking this -- it's just a
frontend to where you store your VMs?

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: docs on storage pools?
  2009-10-02 20:04 docs on storage pools? Richard Wurman
@ 2009-10-04 22:10 ` Cole Robinson
  0 siblings, 0 replies; 2+ messages in thread
From: Cole Robinson @ 2009-10-04 22:10 UTC (permalink / raw)
  To: Richard Wurman; +Cc: kvm

Richard Wurman wrote:
> So far I've been using files and/or LVM partitions for my VMs --
> basically by using virt-manager and modifying existing XML configs and
> just copying my VM files to be reused.
> 
> I'm wondering how KVM storage pools work -- at first I thought it was
> something like KVM's version of LVM where you can just dump all your
> VMs in one space .. .but it looks like it's really means "different
> places you want to store your VMs":
> 

The 'storage pool' concept you're talking about is libvirt functionality, not
KVM/QEMU:

http://libvirt.org/storage.html

> - dir: Filesystem Directory
> - disk: Physical Disk Device
> - fs: Pre-Formatted Block Device
> - iscsi: iSCSI Target
> -logical: LVM Volume Group
> - netfs: Network exported directory
> 
> I understand things like LVM and storing VMs in a filesystem
> directory.. but what real difference is there by going through the
> GUI? I suppose nothing. Maybe I'm overthinking this -- it's just a
> frontend to where you store your VMs?

Exposing storage management through libvirt allows remote storage
provisioning, and saves libvirt users (like virt-install and virt-manager) the
trouble of knowing all the differing details between creating lvm LVs, disk
partitions, raw/qcow2/vmdk images, etc. For desktop virt using raw files for
storage, there isn't much need to concern yourself with the concept.

Any further questions should be directed to libvirt-list@redhat.com (for
libvirt) or virt-tools-list@redhat.com (for virt-manager).

- Cole

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-10-04 22:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-02 20:04 docs on storage pools? Richard Wurman
2009-10-04 22:10 ` Cole Robinson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).