Ref articles
vmware	article link

Notes;

This procedure can be used in general for most virtual plaforms that support direct LUN mapping and and clustering (they must support giving multiple virtual machines direct access to storage LUNs). LUN's in a msft cluster have signatures that must be preserved.

1. import the node's OS drive into the Virtual host
   1. vmware convertor
   2. symantec
   3. acronis
   4. platespin
2. import the disk;
   1. if the disk are on a SAN, see step 3.3 changing SAN acl.
   2. if the cluster data is being moved to new disk, export the cluster LUN images using the cloning software in step 1 or the table below, or contact Vigilant to get a V-drive
3. shut down the hardware cluster nodes
   1. before shutting down, make note of the ip addresses of the nodes (most virtualizations system do not preserve these because a different NIC driver is used, but his can be found in the registry)
   2. shut down the nodes
   3. add the Virtual host to the ACL (access list) to the LUN's and optionally disable the hardware node access
4. map the LUNs to the imported virtual machine
5. start up one node of the cluster
6. Connect thru the virtual console and add the node IP addresses for the node
7. restart cluster services and resolve any problems

Cloning software;

Robocopy	http://technet.microsoft.com/en-us/magazine/cc160891.aspx
Platespin
ViceVersa	http://www.tgrmn.com/
Ghost	http://www.symantec.com/business/products/overview.jsp?pcid=2247&pvid=865_1
Acronis	http://www.acronis.com/
symantec	symantec system recovery
DoubleTake	http://www.doubletake.com/
NetBackup	http://www.symantec.com/business/products/overview.jsp?pcid=2244&pvid=2_1