search for: vhbas

I'm missing something. The purpose of NPIV (as I understand it) is to give a guest OS an HBA that it can scan, play with new luns, etc all without making changes to the physical server(s) the guest is living in currently. However, I can't find a way to either have the guest's XML config create the HBA or for the physical server to successfully GIVE the HBA to the guest. I can give

...I can build the nested environment (using OVM, and I have to step back to OVM3.2.2 to allow me to do PCI passthrough), but as soon as I start up a VM with a phys device passed through, the first layer loses all connectivity to the SAN. Setup: * 2 UCS B200M2 blades - configured with 9 vHBAs. * Linux machines running LIO-ORG''s and SCST''s FCAL target mode (trying both to decide on which to use going forwards) The first vHBA is passed through to the "bare metal" OVM3.2.2, and the rest are managed through xen-pciback. I then install another OVM3.2...

...;2101001b32a9da5e</wwpn> </capability> </capability> </device> This vHBA will only be defined as long the host is not rebooted. In order to create a persistent vHBA, one must use a libvirt storage pool (see next section). 3) Creation of vHBA by the storage pool By design, vHBAs managed by the node device driver are transient across host reboots. It is recommended to define a libvirt storage pool based on the vHBA in order to preserve the vHBA configuration. Using a storage pool has two primary advantage, first the libvirt code will find the LUN's path via simple virsh...