> > What is your thought process behind this process? Are you wanting your > > guests to be the ones running multipath? The only configurations I've seen > > The goal is pretty simple: give FC LUNs to guests. My first thought > was treating guests as "normal" physical machines and terminating FC > connections on them, using N_Port ID Virtualization (I'm not sure if > it is supported).
I don't know about N_Port ID Virtualization, but I would say that trying to manage that might be a bit more work than its worth. > > or played with had the host machine handling all the heavy lifting and just > > passing the final disks (be it multipath raw disks, or lvm, etc) to the > > guest. > > This sounds like a good idea. You have a few paths for this depending on what you are playing with. I know that up and coming virsch and libvirt have support for some pool management, and it looks like the options exist but I don't see any real documentation on it (hint: anyone with some please provide, or Red Hat please document?!). Since you are playing with virtuals and FC, I'm going to assume two things: 1) you have more than 1 path over the FC to you disk That being said you have all kinds of options, but I think the common one would be to use multipathd to "combine" your paths, so that you can easily pass that FC LUN to the guest as one device. This helps handle some of the limitations of number of disks you can pass to a guest in some/most virtualization technologies. 2) you have more than 1 box In this circumstance you can explore things like clvm and clustering so that you can easily live migrate guests between your boxes. -greg _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
