Ok, let's see if I have this right.

You are creating luns on the host machine, _not_ using lvm, then using
those luns as VM disks, inside the VM's you are using LVM internally
to the VM?

My first question, and i think your going to get a lot of this so hang
in there, is why? should be the other way around imho.

Not that I don't think it should work, just trying to understand the
rational behind this.  What you could try is called "tagging".

it's a PITA though so your mileage may very greatly.

Bascially, you edit, your VM's /etc/lvm.conf with a line like this...

volume_list = [ "@vmname"]

in the "activation" section.

Where "vmname" is anything you care to use that's unique, like your vmname...

Then, you tag the volume group (or volume) using either vgchange or
lvchange --addtag=vmname

Once you do that, the only nodes that will allow the volume (or volume
group) to be actvated are the ones with the volume_list entry in there
lvm.conf.

This is the older method for doing HA-LVM on non GFS1/2 RHEL clusters.
A way of protecting the file system against accidental, multinode
mounts.

I've never tried this but it might work. If it doesn't, or someone
else has a better idea (or a better understanding of the problem) we
never had this talk...


-C


On Fri, Mar 11, 2011 at 9:18 PM, Michael Torrie <[email protected]> wrote:
> On 03/11/2011 01:37 PM, Michael Torrie wrote:
>> 1. create new LUN(s) that will be used as a virtual machine disk
>> 2. create the virtual machine, and set up the logical volumes, punching
>> the SAN devices through into the VM.
>> 3. reboot the physical machine (suspending or shutting down the vms too)
>> 4. volumes intended for the VM are now instead active on the host.
>>
>> Hope that helps.  No amount of zoning is going to fix that.
>
> I should add that given this problem there is no way to use LVM inside
> of a VM guest using a physical disk of any kind without the host RH EL
> activating the volumes.  SAN is just one case where this is going to
> occur, even with zoning.  I'm currently exploring the options in lvm.conf.
>
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list
>

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to