- Create RDM disks:
#vmkfstools -z /vmfs/devices/disks/t10.ATA_____Samsung_SSD_840_Series__________________S14GNEBCB62239V____
_ rdm/Samsung_SSD_840_Series-S14GNEBCB62239V.vmdk -a lsisas
# vmkfstools -z /vmfs/devices/disks/t10.ATA_____ST3640323AS_________________________________________5VK045H
3 rdm/ST3640323AS-5VK045H3.vmdk -a lsisas
Note: RDMs cannot be stores on a NFS datastore, see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001856 .
- Create VM referencing the new RDM disks.
- Start VM and look at the BSOD :(
- Start physical machine and make the changes referenced here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/b4d45d9d-4c90-4ab0-ae38-f1257ce9c608/windows-7-server-2008-r2-bare-metal-restore-0x0000007b-stop-error?forum=windowsbackup :
"If in doubt, turn on all possible required services e.g. set both intelide = 0/pciide = 0 and msahci = 0, or set all of these to 0 and it will still boot with the correct driver/s:
aliide, amdide, atapi, cmdide, iastorv, intelide, msahci, pciide, viaide and LSI_SAS."
- Start VM... no BSOD :)
- Let Windows install and update drivers for virtual environment and reboot
- Install VMware tools and reboot
- VM is ready
