I have a physical Windows 2008 R2 server that connects via iSCSI, over ethernet, to a SAN. I need to convert the server to virtual, but I don't want to convert the iSCSI volume to VMDK, because I don't have the storage space required.

Rather, I'd like to leave the iSCSI connection intact and have the new VM continue to use the SAN. The VMs on my vSphere host are not being stored on the SAN (they're on local storage), and everything is on the same LAN.

Can I do this? When using vSphere P2V Converter, would I simply uncheck the box to convert the iSCSI volume? Will the iSCSI connection carry over to the VM and continue to work?


You can select to not convert that disk in the converter, as simple as that. The iSCSI connection will be usable in the VM and the settings will follow the P2V.

but, IMO, I would recommand to not use an iSCSI disk inside a VM. To be sure before please validate, as when in a VM if the storage is in a iSCSI the quiesce method for snapshot does not work usually.

Virtual machines with independent disks must be powered off before you take a snapshot. Snapshots of powered-on or suspended virtual machines with independent disks are not supported.


You don't convert iSCSI disk -> VMDK (in reality it won't even work), rather you allow converted OS to maintain TCP (...and iSCSI) connectivity.


Plus, it's a good idea to allow OS to manage your iSCSI connection, in-guest iSCSI is always slow.


Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.