Ubuntu
linux package

  1. Bug #1339768
  2. Comment #13

Comment 13 for bug 1339768

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

Thanks for testing all that Daniel. I think we've got the problem identified now: It does revolve around the virtualHW.version specified in the .vmx file (7 versus 10)... I find that if I edit my .vmx and change my virtualHW.version from 10 to 7, then I do see the problem behavior.

Thomas Hellstrom from VMware explains whats happening and provides suggested remedies here:
https://communities.vmware.com/message/2398873#2398873

Daniel, please edit your .vmx and bump up your virtualHW.version from 7 to 10 (that's Thomas's solution "1b"). Does that fix it?