VMware P2V Process
VMware P2V Process
VMware P2V Process
Title: Process: Date of Revision: Version Number: Effective Date: VMWare P2V Conversion Process Document
1.0 Purpose
This document serves as a procedural guide to standardize how we can convert a Physical Machine in to a Virtual Machine using VMware P2V Conversion process.
126726441.doc a11/p11
Page 1 of 1
2.0 Procedure
Log onto Physical Server, shutdown any application services such as WWW, BES, SQL ETC. Log into VCenter Server (Server_Name) From the Plugins menu, select Manage Plugins, click on the Installed Tab, Verify VMware Converter is enabled.
Right click on either of the ESX server and choose Import Machine
126726441.doc a11/p11
Page 2 of 1
Click Next
126726441.doc a11/p11
Page 3 of 1
Enter Name or IP address of Physical Server, and enter DOMAIN_NAME\XXXXXX domain credentials.
126726441.doc a11/p11
Page 4 of 1
Choose the Automatic option for the install and removal of convert, click Yes
126726441.doc a11/p11
Page 5 of 1
This screen will allow you to resize volumes if desired, from the drop down list choose <size in GB> and type the new size of the volume. Click Next
126726441.doc a11/p11
Page 6 of 1
Enter the Server name as it will be listed in Virtual Center, should be the same as the Windows Host Name (Please use all capitals). Choose the folder where the VM should reside, these folders are just for management purposes, if you choose the wrong folder dont be concerned, once the P2V is complete the VM can be moved in VCenter without issue.
126726441.doc a11/p11
Page 7 of 1
Choose the SAN Datastore this VM should reside on. VMFS1 and VMFS2 are used in the Most Environment for general VMs. Once again this can be changed using VCenter and Storage-V-Motion at a later date, but its easiest to choose the correct volume now.
126726441.doc a11/p11
Page 8 of 1
From the Networks menu, choose to add only 1 NIC to the VM, and uncheck the Connect at Power on box.
******Do NOT choose to install the VMware Tools here. Click Next at the Customization Screen Click next at the Schedule Task Screen, the default option is to run now.
126726441.doc a11/p11
Page 9 of 1
Verify the Power on.. is unchecked, click Finish to start the P2V Process.
Page 10 of 1
Monitor the P2V process from the Recent Tasks window in VCenter. Do not proceed until the task is complete, the time needed to complete may vary due to network usage and amount of data on the physical machine.
Page 11 of 1
Page 12 of 1
Right click and edit settings again-you will have to do edit settings after every operation prior to power on
Page 13 of 1
We will then need to change the SCSI Controller fromBUS Logic to LSI Logic
Page 14 of 1
Page 15 of 1
Page 16 of 1
Choose SCSI 1:0 from the Device Node drop down list, click next and finish
Page 17 of 1
Click OKAY
To Change SCSI controller type Click on the NEW BUS Logic adapter
Page 18 of 1
Page 19 of 1
Click Add and add a CD/DVD Drive to the VM, just click next to all the defaults Click OK
Page 20 of 1
Page 21 of 1
Page 22 of 1
Power on the VM
You will see this message: Leave the setting at YES (This will power on the machine with no NIC plugged in) (The OS should boot and see the new LSI card and install a driver.) Open VM Console and log into server with local admin account. Let server run for a few minutes, OS should find new hardware and ask for reboot. Click yes to reboot Log into server with local admin account again
Page 23 of 1
Click the VM menu, click Install/Upgrade VMware Tools, and choose Typical Install. Follow instructions in txt file that opens up to change Video settings. Click Finish and reboot. Verify New LSI controller shows up in Device manager under SCSI Controllers.
Shut down VM
Edit Setting on the VM once its powered off
Page 24 of 1
Select the 8MB volume you created earlier and select REMOVE
Choose Remove from VM and delete from disk, if you dont choose this option we wont gain back the disk space from the SAN. Click OK Go back into Edit Settings and choose the BUS LOGIC SCSI Adapter, change this adapter to LSI and click ok. Reboot the server, click YES to any the VM Message warning. The server should now be able to boot from the LSI controller, now that it has the driver already installed from the temp controller that we installed and deleted. PHYSICAL SERVER Instructions: _______________________________________________________________________ _________ Log into IBM Blade Center management / ILO at IP xxx.xxx.xxx.xxx, username xxxxx and the password info should be in the DB. Click remote control on the physical server name Click Start Remote Control, verify you have correct java version installed. This will open another window, this new window will allow remote console.
Page 25 of 1
Select the server you want to work on (the physical server) from the Video drop down list. Log into the server as LOCAL admin Edit the NIC Settings, note the current IP etc (so you can put it on the new VM) Set the NIC to DHCP Shut down the Physical Server. ***Put Physical server in whats up maintenance mode or send OPS an email to ignore alerts until you have re-equipped the VM
Page 26 of 1
Edit Settings again on the VM, check the 2 boxes on NIC 1, On the VM, double click the NIC Teaming software in the bottom right corner, it should prompt you to uninstall the software, choose yes. On the VM set the IP info to the info noted from the physical server and reboot. Test RDP and verify services are running.
Page 27 of 1
SME Approval
Version 1.0 Name Title Signature Date
QA Approval
Version Name Title Signature Date
Revision History
Version 1.0 Date 9/07/2009 Author(s) Ravi Shankar Revision Description Drafting the Process in Capgemini Format
Page 28 of 1