I'm in the process of moving from virtualized NetWare 6.5 to virtualized
OES11 and had a design dilemma with regard to setting up the storage.

It comes down to a question of whether or not the flexibility gained is
worth the logically-expected hit on performance.

Pertinent notes:
I intend on sticking with NSS for my data storage.
All storage resides on a fiber channel SAN array (no iSCSI).
Although I don't think the brand of hypervisor is a factor, I use VMWare's
ESXi.

There are basically two ways to set up the virtualized server:

1) Assign a LUN to a hypervisor and let it dole out the storage to the VM.
The hypervisor formats the datastore in its format of choice and then the
VM's storage is dealt with however a hypervisor deals with NSS formatting.

2) Configure the HBA as a pass-through device, and assign the LUN directly
to the VM. The VM then formats the LUN as an NSS partition.

Method (1) would logically impact I/O performance, but I don't know to what
degree.

As to the flexibility factor, if I want relocate the VM on different host
hardware the two methods would be:

Create hypervisor on new hardware with different HBA.
Add WWN of new HBA to SAN fabric.
Edit Zone to assign LUN to new WWN.
Populate hypervisor with vm's from datastore.
Boot VM.


Relocate with a pass-through HBA requires:
Create hypervisor on new hardware with different HBA.
Add WWN of new HBA to SAN fabric.
Put HBA in pass-through mode.
Copy VM to new hypervisor with VEEAM.
Edit VM to add HBA.
Edit Zone to assign LUN to new WWN.
Boot VM.


At this point in time, the servers do not have a huge amount of data (less
than 2TB on each server) and I currently have less than 400 users in the
system.
That will change, however, and I wish to minimize the impact that growth
will have.

Any thoughts are welcome, especially if I'm missing a factor or overlooking
a 3rd alternative.