Skip to main content

P2V Conversion step by step



Remote Logon to that Converter client Software installed machine.
Go to start menu à Program files àVMware à Converter Standalone Client
This will open the new window.

Click Convert Machine.
In this window we can choose which type of machine machine we are going to convert.
For this conversion we are selecting Power on Machine

In the below panel we have to provide Admin or root Username name and password for the conversion machine and click à Next.

In this window we have to provide the IP address of the ESX / VC Machine ,username and password


Click à Next


In this window we can specify the Name of the Virtual Machine and we have to choose Storage Details.


Click à Next



In this option we can customize the VM Hardware.
For linux machine while converting we should not disturb the HDD Related Informations.
And also we have to provide the IP Address and Config details for the helper machine network.


Click à Edit

Provide the IP And DNS Details.
Click à Next

Finally click Finish To complete the Task.


Conversion process has been started.
Once completed VM is ready for the Operation in the Specified VC / ESX Host.
To Export the Disks Kindly follow the Steps.
Before Going for the Export we have to identify what are all the HDD has been used by the VM and also the Exact Path of that HDD Files in Storage and where this files needs to be exported.
For example Kindly the Details
usplsvpea004.vmdk
usplsvpea004_1.vmdk
usplsvpea004_2.vmdk

The above said files are the HDD Used by the VM.
And Path of the Files are as follows
/vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/usplsvpea004/usplsvpea004.vmdk
/vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/usplsvpea004/usplsvpea004_1.vmdk
/vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/usplsvpea004/usplsvpea004_2.vmdk
To mount USB Drive kindly follow the Procedure
First we need to identify Device Name. then we need to mount the USB Drive as follows.
mkdir /mnt/usb
mount /dev/[device_name] /mnt/usb -t ext3
Once we find all the Details we need to use vmkfstools command to export the Disks.
For the Above said Disks find the Command to export HDD files to usb Drive.
vmkfstools -i /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/usplsvpea004/usplsvpea004.vmdk /mnt/usb/USPLSVPEA004/usplsvpea004.vmdk -d 2gbsparse
vmkfstools -i /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/usplsvpea004/usplsvpea004_1.vmdk /mnt/usb/USPLSVPEA004/usplsvpea004_1.vmdk -d 2gbsparse
vmkfstools -i /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/usplsvpea004/usplsvpea004_2.vmdk /mnt/usb/USPLSVPEA004/usplsvpea004_2.vmdk -d 2gbsparse

To import the above said disks to some other Location kindly follow the procedure.
In this example we are using  USPLSVPEA004 as a VM Name and the Path of the Exported disk files is  as follows.
/mnt/usb/USPLSVPEA004/
We are going to import the files in to the Below said path of the ESX host.
/vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/test-usplsvpea004/
To import
vmkfstools -i /mnt/usb/USPLSVPEA004/usplsvpea004.vmdk      /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/test-usplsvpea004/usplsvpea004.vmdk 


vmkfstools -i /mnt/usb/USPLSVPEA004/usplsvpea004_1.vmdk /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/test-usplsvpea004/usplsvpea004_1.vmdk 

vmkfstools -i /mnt/usb/USPLSVPEA004/usplsvpea004_2.vmdk /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/test-usplsvpea004/usplsvpea004_2.vmdk 
if we want to copy VM config files in the same way we can copy the files in to USB and again move back to the Path in where we need to import.
For the above said example we have done the same as follows.
Exporting Log and Other files :
cp *.vmx *.log *.nvram *.vmxf *.vmsd /mnt/usb/USPLSVPEA004
Importing Log and Other files :
cd /mnt/usb/[dir_name]
cp *.vmx *.log *.nvram *.vmxf *.vmsd /vmfs/volumes/4be9aff4-0357020a-03b8-0014c2c3446a/test-usplsvpea004
Once all this things done then the VM is ready to add to Inventory.
We can done this using Command Line or thru Vi client.
Kindly follow the Procedure for the above said Task.
To register that Machine:
To register a virtual machine in vCenter Server:
                Open the vSphere / VMware Infrastructure (VI) Client and log in with appropriate credentials.
                If connecting to vCenter Server, click on the desired host.
                Click the Configuration tab.
                Click Storage.
                Right-click on the appropriate datastore and click Browse Datastore.
Navigate to the folder named after the virtual machine, and locate the <virtual machine>.vmx file. 
                Right-click the .vmx file and click Add to inventory. The Add to Inventory wizard opens. 
                Continue to follow the wizard to add the virtual machine.
                To register a virtual machine from a command line:
Log in as root to the ESX host with an SSH client.
From command Line:
                vmware-cmd -s register <full path to virtual machine>\<virtual machine name>.vmx

Comments

Post a Comment

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more