VMware Workstation error: virtual machine's policies are too old...

0 Shares

I recently upgraded my VMware Workstation to version 9 and today when I went to open a few of my VMs to do some quick testing I got an error related to “virtual machine’s policies are too old…”. Grr. Nothing changed but the upgrade.

After a bit of Googling I found a link with a solution that worked for me:

1. Edit the vmx-file and remove all lines starting with policy*
2. Rename the vmpl file if it exists

I don’t know why I (and apparently other people) had to perform these steps after this v9 upgrade, but I did. I hope this helps someone else out there scratching there head in potential panic mode about possible “lost” VMs.

More from my site

0 Shares

virtualization

7 comments on “VMware Workstation error: virtual machine’s policies are too old…”

getupaaaah says:

September 23, 2012 at 3:15 pm

Thanks m8. It looks like it’s working now thanks.

steven says:

November 7, 2012 at 12:08 am

THX!I remove the lines starting policy* and delete the file .vmpl.Then，it worked.

Scott Edmondson says:

November 12, 2012 at 1:34 am

:mrgreen: Thanks, Man!

This worked for me with VMWare Workstation 9.0.1 for Linux 64-bit. I had to remove two .vmpl files from the VM’s directory and all the policy.* entries from the .VMX file.

It’s running fine now.
Cheers,
Scott

Moshe Goldstein says:

November 27, 2012 at 9:17 am

Thank you very much!!!!!
This solved the problem immediately.
This should be fixed automatically by the VMware player (or by the VMware Workstation) instead of leaving it to the users to be solved, and waste their time.
Thank you very much again.

I have another problem that may be you also already solved:
I bought a new laptop which runs with Win7 Home Premium 64 bits. When run my virtual machine on this laptop, the following warning message is displayed:

Binary translation is incompatible with long mode on this platform. Disabling long mode. Without long mode support, the virtual machine will not be able to run 64-bit code. For more details see http://vmware.com/info?id=152

I went to that URL but I did not understand what I need to do. My laptop has an intel i5 processor and 8 Gb of main memory. Also, the virtual machine was created with VMware workstation 5.x running in a WinXP 32 bit computer. Is this the reason of the warning? May the VM converter colve the problem?

Thank you very much.
— Moshe Goldstein, PhD

Madaiah says:

March 10, 2013 at 11:57 pm

Hi Brad,

I have only one virtual file and there are no VMX or VMPL file. So any suggestion how to fix this issue. On my Vm folder I have only one file ie., VMDK.

Regards,
Madaiah

Brad Kingsley says:

March 11, 2013 at 9:15 am

I’m not familiar with that configuration but it sounds like the vmdk (disk file) is located in a different folder from the configuration (vmx) file. The vmx file has to exist somewhere because that’s where VMware stores the configuration for each VM. You’ll need to search your local disk and find out there it is located.

akarabal says:

June 27, 2013 at 4:31 pm

thank you very much!
>I don’t know why I (and apparently other people) had to perform these steps after this v9 upgrade, but I did.
I have 3 boxes runin on my VMWorkstation 7.1. I found that only 1 VM image has .vmpl file and records “policy*” in .vmx. Correct: I needed to do changes for this 1 VM and the rest were fine (becasue thay have no such a records and vmpl file)

getupaaaah says:

September 23, 2012 at 3:15 pm

Thanks m8. It looks like it’s working now thanks.
steven says:

November 7, 2012 at 12:08 am

THX!I remove the lines starting policy* and delete the file .vmpl.Then，it worked.
Scott Edmondson says:

November 12, 2012 at 1:34 am

:mrgreen: Thanks, Man!

This worked for me with VMWare Workstation 9.0.1 for Linux 64-bit. I had to remove two .vmpl files from the VM’s directory and all the policy.* entries from the .VMX file.

It’s running fine now.
Cheers,
Scott
Moshe Goldstein says:

November 27, 2012 at 9:17 am

Thank you very much!!!!!
This solved the problem immediately.
This should be fixed automatically by the VMware player (or by the VMware Workstation) instead of leaving it to the users to be solved, and waste their time.
Thank you very much again.

I have another problem that may be you also already solved:
I bought a new laptop which runs with Win7 Home Premium 64 bits. When run my virtual machine on this laptop, the following warning message is displayed:

Binary translation is incompatible with long mode on this platform. Disabling long mode. Without long mode support, the virtual machine will not be able to run 64-bit code. For more details see http://vmware.com/info?id=152

I went to that URL but I did not understand what I need to do. My laptop has an intel i5 processor and 8 Gb of main memory. Also, the virtual machine was created with VMware workstation 5.x running in a WinXP 32 bit computer. Is this the reason of the warning? May the VM converter colve the problem?

Thank you very much.
— Moshe Goldstein, PhD
Madaiah says:

March 10, 2013 at 11:57 pm

Hi Brad,

I have only one virtual file and there are no VMX or VMPL file. So any suggestion how to fix this issue. On my Vm folder I have only one file ie., VMDK.

Regards,
Madaiah
- Brad Kingsley says:
  
  March 11, 2013 at 9:15 am
  
  I’m not familiar with that configuration but it sounds like the vmdk (disk file) is located in a different folder from the configuration (vmx) file. The vmx file has to exist somewhere because that’s where VMware stores the configuration for each VM. You’ll need to search your local disk and find out there it is located.
akarabal says:

June 27, 2013 at 4:31 pm

thank you very much!
>I don’t know why I (and apparently other people) had to perform these steps after this v9 upgrade, but I did.
I have 3 boxes runin on my VMWorkstation 7.1. I found that only 1 VM image has .vmpl file and records “policy*” in .vmx. Correct: I needed to do changes for this 1 VM and the rest were fine (becasue thay have no such a records and vmpl file)

a.