I'm using Windows Vista x64, when I have a VMWare Server 2.0 Virtual Machine opened, and then start up a Microsoft Virtual PC 2007 Virtual Machine, the VMWare Machine will exit/die. If I already have an MS VPC 2007 machine open, then when I try to start a VMWare VM, I get the following message:
Unable to connect to the MKS: There is no VMware process running for config file C:\Users\Rusty\Documents\VMWare Virtual Machines\Ubuntu\Ubuntu.vmx
Either run "C:\Program Files (x86)\VMware\VMware Server\x64\vmware-vmx.exe C:\Users\Rusty\Documents\VMWare Virtual Machines\Ubuntu\Ubuntu.vmx" manually on the server,
or register the config file.
Sorry, it seems that when I pressed Enter for a line break, the message got posted instead.
If I start a VM from the VMWare internet control panel while an MS Virtual PC 2007 VM is on, it will indicate boot successful, but then the machine will switch off instantly (the shutdown isn't indicated in the task log in the VMWare Web Access control panel.
I have tried uninstalling VMWare Server 2.0 and then installing it again, but still have the same problem. Any ideas?
P.S. The reason I use MS VPC 2007 is that MS has free disk images with IE6 and IE7 installed, which I need to use for website testing.
Thanks
Dave
It is likely that VPC 2007 leaves the CPU in VMX operation, which prevents VMware Server from switching between legacy mode and long mode. Unfortunately, that mode switch is required for the majority of host/guest configurations under VMware Server 2.
I don't know if it is possible to disable VT-x support in VPC 2007, but if it is, that may be a workaround for this issue.
Thanks for the help - MS Virtual PC 2007 has an option to disable/enable hardware virtualization, so disabling that now means I can use both Virtual PC and VMWare at the same time.
Thanks again!
Dave