new1234.jpg

Archive

Posts Tagged ‘VMware Converter’

VMware: The device or operation specified at index ‘2’ is not supported for the current virtual machine version

April 19th, 2012 3 comments

Last week I was migrating some servers from ESX 3.02 to a vSphere 5 cluster, after importing the the exported VM’s I received this error message:

The device or operation specified at index ‘2’ is not supported for the current virtual machine version ‘vmx-04’.  A minimum version of ‘vmx-06’ is required for this operation to succeed.

A general system error occurred: Invalid fault

image


Solution
:

The VMware Converter I used was version 4.3.0 build-292238

image

After installing VMware Converter 5.0.0 build-470252 I was able to start the import virtual machine in the new vSphere 5 cluster

image

image

The import finished successfully

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: HP Proliant Support Pack Cleaner v1.5

May 17th, 2011 No comments

Last year I posted an article about the “Proliant Support Pack Cleaner” (PSP), last month I did 28 P2V’s migrations and this software was really helpful. During the VMware Converter Wizard I disabled on the “destination server” the HP PSP Startup services, after the P2V process I runned the PSP Cleaner to remove drivers, services etc.

Guillermo Musumeci released in 08/11/2010 version 1.5

 

Support both x86 and x64 versions of HP Proliant Support Pack.

Run in Unattended mode using /NOGUI parameter.

To run HP Proliant Support Pack Cleaner, you must run as administrator, or disable UAC on Windows 2008.

Software: Download

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: FAILED: Unable to obtain the IP address of the helper virtual machine

March 30th, 2011 33 comments

After migrating the last Linux Suse Enterprise 32-bit physical machine with VMware Converter Standalone 4.3 I received a error:

FAILED: Unable to obtain the IP address of the helper virtual machine

image

Solution:

The solution is simple, by converting the physical machine to a virtual machine the VM will start directly. By starting the VM the mounted Converter ISO will boot with a VM HelperNetwork. In case you’re VLAN doesn’t have DHCP functionality you need to configure a static IP for the VM HelperNetwork.

To  assign a static IP address to the Helper virtual machine, select Use the following IP address: and specify the IP address, subnet mask, and default gateway. Be sure the IP address you specify for the Helper virtual machine is not already in use on the network. 
     
(Optional) To configure the DNS server address manually, select Use the following DNS server address: and type the preferred DNS server address. Optionally, type and alternate DNS server address. 
    
Select another option to set or click Next to view a summary of the conversion task. Converter Standalone uses the IP address and DNS server you specified to copy data from the source Linux machine to the destination virtual machine during conversion.

image

 

The VM will boot with the configured network settings:

image

 

P2V status:

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Import Appliance > Device ‘VirtualCdrom’ uses a controller that is not supported

April 19th, 2010 No comments

Today tried to import the ESX Deployment Appliance (EDA) in vCenter 4, but after File > Deploy OVF template > selecting destination host I received this error message:

Device ‘VirtualCdrom’ uses a controller that is not supported. This is a general limitation to the virtual machine’s virtual hardware version on the selected host

To modify the VMware Hardware Version from default version 7 to 4 you can use the VMware vCenter Converter Standalone 4.0.1 Now I was able to import the EDA Appliance in my vCenter.

image

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: How to downgrade VM hardware level 7 to 4

April 9th, 2010 5 comments

After some problems with my ESX 4.0 host I want to move some critical VM’s to my ESX 3.5 u4 host.. but my upgraded hardware level (7) is not compatible with my ESX 3.5 u5 host. The following is a step-by-step guide on how to perform this downgrade:

I want to downgrade my Windows 2008 64-bit with XenApp 6 with hardware level 7 to hardware level 4.

image 

Time to downgrade:

Download and start: VMware vCenter Converter Standalone 4.0.1

VMpros.nl

– Click: Convert Machine
Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn