7:03 a.m.
I am slightly lost trying to attach some storage to a functioning virtual
machine. If this where a real machine, I would simply be trying to mount a
LVM volume.
I have found a lot of documentation about adding storage pools, but I'm
unsure if that is actually what I should be doing. Is that just for storage
of the virtual machines themselves? Once I'd added my LVM volume group to
virsh I could see no way of then assigning one volume of that to be offered
as a logical volume to one particular virtual machine.
I've also seen this:
http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/s...
Looks like I could use that to assign one of the LVM volumes in my LVM
volume group to the VM.
If anyone could explain the different function of these two techniques and
which sounds applicable I would be most grateful.
Thanks,
Douglas
2:43 p.m.
On 10/30/2012 06:03 AM, Douglas Russell wrote:
I am slightly lost trying to attach some storage to a functioning
virtual
machine. If this where a real machine, I would simply be trying to mount a
LVM volume.
I have found a lot of documentation about adding storage pools, but I'm
unsure if that is actually what I should be doing. Is that just for storage
of the virtual machines themselves? Once I'd added my LVM volume group to
virsh I could see no way of then assigning one volume of that to be offered
as a logical volume to one particular virtual machine.
I've also seen this:
http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/s...
Looks like I could use that to assign one of the LVM volumes in my LVM
volume group to the VM.
What is typically done is creating LVM volumes in the host, and then
assigning that as a block device for the guest to use as though it were
a raw disk. The guest then does _another_ layer of PVM/LVM
partitioning, if the guest is something that uses LVM in the first
place. If you want the guest to see an LVM partition created by the
host as an LVM within the guest, without an additional layer, then you
have to expose the PVM as the block device to the guest; this is not a
typical setup, in part because it is then up to you to ensure that the
host and guest are not modifying the same storage at the same time (or
put another way, that the guest is not reading from any other LVM
partitions than the one you wanted it to use).
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
4:51 a.m.
On 30 October 2012 19:43, Eric Blake <eblake(a)redhat.com> wrote:
On 10/30/2012 06:03 AM, Douglas Russell wrote:
> I am slightly lost trying to attach some storage to a functioning virtual
> machine. If this where a real machine, I would simply be trying to mount
a
> LVM volume.
>
> I have found a lot of documentation about adding storage pools, but I'm
> unsure if that is actually what I should be doing. Is that just for
storage
> of the virtual machines themselves? Once I'd added my LVM volume group to
> virsh I could see no way of then assigning one volume of that to be
offered
> as a logical volume to one particular virtual machine.
>
> I've also seen this:
>
http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/s...
>
> Looks like I could use that to assign one of the LVM volumes in my LVM
> volume group to the VM.
What is typically done is creating LVM volumes in the host, and then
assigning that as a block device for the guest to use as though it were
a raw disk. The guest then does _another_ layer of PVM/LVM
partitioning, if the guest is something that uses LVM in the first
place. If you want the guest to see an LVM partition created by the
host as an LVM within the guest, without an additional layer, then you
have to expose the PVM as the block device to the guest; this is not a
typical setup, in part because it is then up to you to ensure that the
host and guest are not modifying the same storage at the same time (or
put another way, that the guest is not reading from any other LVM
partitions than the one you wanted it to use).
Ok, I understand your answer and I feel I'm close to the solution, but I'm
still unclear on the storage pools part. In what you've described below,
these aren't used? I assume you've used attach-disk to add the LVM volume
to the guest as a block device? I definitely never intended to add the
logical volume to the guest and have it appear as a logical volume. I was,
as you say, trying to attach it as a block device.
Thanks for your response!
Douglas
10:03 a.m.
On 10/31/2012 03:51 AM, Douglas Russell wrote:
> What is typically done is creating LVM volumes in the host, and
then
> assigning that as a block device for the guest to use as though it were
> a raw disk. The guest then does _another_ layer of PVM/LVM
> partitioning, if the guest is something that uses LVM in the first
> place. If you want the guest to see an LVM partition created by the
> host as an LVM within the guest, without an additional layer, then you
> have to expose the PVM as the block device to the guest; this is not a
> typical setup, in part because it is then up to you to ensure that the
> host and guest are not modifying the same storage at the same time (or
> put another way, that the guest is not reading from any other LVM
> partitions than the one you wanted it to use).
>
Ok, I understand your answer and I feel I'm close to the solution, but I'm
still unclear on the storage pools part. In what you've described below,
these aren't used? I assume you've used attach-disk to add the LVM volume
to the guest as a block device? I definitely never intended to add the
logical volume to the guest and have it appear as a logical volume. I was,
as you say, trying to attach it as a block device.
Right now, we have a disconnect in the libvirt design, that I'd like to
fix someday. virDomainPtr <domain> XML could care less that storage
pools exist - it only cares about <disk> elements having an absolute
path to storage, and the storage does not have to belong to a pool.
Likewise, virStoragePoolPtr and virStorageVolPtr could care less that
domains exist - they only care that storage volumes belong to a storage
pool (that is, virStorageVolPtr can't exist without a pool).
What I _want_ to have, someday in the future, is the ability to have an
alternate XML representation for <domain> that lets you list
pool=poolname volume=volname instead of path=/path/to/name. I'd also
like to have API that given a domain, you can get back virStorageVolPtr
for every disk referenced by that domain, even if it means creating
transient virStoragePoolPtr for the directory containing the path; that
means that EVERY disk image would belong to a pool, whether or not you
explicitly created a pool. Conversely, I'd also like an API that given
a virStorageVolPtr, you can then get at all other volumes and domains
that are currently referring to the storage volume (either as domain
<disk> or as backing files of things like qcow2 files).
But since that does not exist, all you need to know now is that if you
want libvirt to help you create LVM volumes, then create a storage pool;
but if the LVM volumes are already created, merely set the <disk> in
your domain to point to its absolute path, without having to worry about
pools.
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
4387
days inactive
4388
days old
3 comments
2 participants
participants (2)
-
Douglas Russell -
Eric Blake