VMware Cloud Community
RMR_1968
Contributor
Contributor
Jump to solution

Fatal Error: A specified parameter was not correct

Hi,

I am trying to P2V a winbox server (ProLiant DL360 G5 10Gb RAM 136HD 4CPU) with Microsoft Windows Server 2003 R2 Enterprise Edition and Citrix installed. I installed the converter on the machine and run it from there. The ESX Host is a HP ML370 G5 8 CPU 32GB RAM and internal storage of 500Gb with ESX 3.5.0.70356 installed.

The process goes smoothly and it creates the virtual clone. If I do not install the vmware tools right away the newly created machine stars ok but after few clicks inside it goes black and doesn't start anymore giving a fairly general error of "A specified parameter was not correct". If I look at the events, when I power on I get:

- Task: Power on Virtual Machine

- Migration from esxhost.domain to esxhost.domain: Device "USB Controller" is not supported. This is a general limitation of the host

- Virtual Machine is starting

- Failed to Power on: A specified parameter is not correct

If I check in the converter "Install VMWare Tools" the VM never starts after convertion. I also tried to edit out the USB controller but to no avail.

Anybody has any idea? I googled around but no real answers

Reply
0 Kudos
1 Solution

Accepted Solutions
theanykey
Virtuoso
Virtuoso
Jump to solution

To be honest I cant find any issues in the logs ... if this is a converter fault, it could be driver conflicts - would make sense considering what happens when you install vm-tools. I would suggest going into safe mode and trying to clean up the machine as detailed under "After a conversion" at http://kb.vmware.com/kb/1004588

This looks to me more like an ESX issue

http://www.google.com/search?hl=en&q=site%3Avmware.com%22Aspecifiedparameterwasnotcorrect%22&btnG=Search

I also have some internal information I can share ...

Problem:

Recent Tasks display the error: "A specified Parameter was not correct. Spec.memoryAllocation.reservation"

When connected to VirtualCenter the following error is being reported every two seconds or so:

A specified parameter was not correct. Spec.memoryAllocation.reservation

Note: Before you begin please refer to http://kb.vmware.com/kb/1003490 for important information on restarting the mgmt-vmware service.

Symptoms:

  • The task looks to be initiated by vpxuser.

  • Observed every two seconds or so.

Resolution/Workaround:

1. Disconnect and remove the host from the cluster.

2. Remove any memory reservations on virtual machines.

3. Remove the vpxa agent using the rpm -e command.

4. Type service mgmt-vmware restart to restart the ESX Server management service.

5. Add the host back to VirtualCenter

View solution in original post

Reply
0 Kudos
5 Replies
theanykey
Virtuoso
Virtuoso
Jump to solution

I need to see the agent logs - they are on the physical 2003 server you are converting (in C:\Windows\Temp\vmware-temp\). Please attach all .log files (you can attach a .zip for all of them).

RMR_1968
Contributor
Contributor
Jump to solution

Here is the zip of all log files you requested.

Thnx

Reply
0 Kudos
RMR_1968
Contributor
Contributor
Jump to solution

I also like to add that the converted machine stays locked on the ESX Host and in order to erase it and make a new attempt with the same name I need to restart the ESX box.

Reply
0 Kudos
theanykey
Virtuoso
Virtuoso
Jump to solution

To be honest I cant find any issues in the logs ... if this is a converter fault, it could be driver conflicts - would make sense considering what happens when you install vm-tools. I would suggest going into safe mode and trying to clean up the machine as detailed under "After a conversion" at http://kb.vmware.com/kb/1004588

This looks to me more like an ESX issue

http://www.google.com/search?hl=en&q=site%3Avmware.com%22Aspecifiedparameterwasnotcorrect%22&btnG=Search

I also have some internal information I can share ...

Problem:

Recent Tasks display the error: "A specified Parameter was not correct. Spec.memoryAllocation.reservation"

When connected to VirtualCenter the following error is being reported every two seconds or so:

A specified parameter was not correct. Spec.memoryAllocation.reservation

Note: Before you begin please refer to http://kb.vmware.com/kb/1003490 for important information on restarting the mgmt-vmware service.

Symptoms:

  • The task looks to be initiated by vpxuser.

  • Observed every two seconds or so.

Resolution/Workaround:

1. Disconnect and remove the host from the cluster.

2. Remove any memory reservations on virtual machines.

3. Remove the vpxa agent using the rpm -e command.

4. Type service mgmt-vmware restart to restart the ESX Server management service.

5. Add the host back to VirtualCenter

Reply
0 Kudos
RMR_1968
Contributor
Contributor
Jump to solution

Thanks. I re-verified and it seems that the insight manager of HP was very upset not to be able to recognize the new virtual hardware and was causing the freeze. I re-p2v the machine and before anything i configured the HW and left only the bare minimum. Without installing the VMWare Tools I disabled the HP Services and then proceded with the elimination of unwanted SW and Ghosted Devices. Now everything works like a charm. Thanks a Lot

Romano

Reply
0 Kudos