

Can single files be accessed from the main machine (for backups or so) in either XP Mode or VMware? From Jeff Atwood's recent story I understand that backing up VMware is tricky.They don't have to run concurrently - each is for a different task. If I'll be using VMware, I'd love to have several images I can load - development tools, clean OS install, some servers etc.Is there a difference in terms of interaction with the main machine?.Is there a difference in terms of performance between XP Mode and VMware? Dev tools are heavy, and I'd like to get as much as possible from the hardware (couldn't care less about graphics, though).I've never used 7 or VMware, and have wondered: I'm thinking about using either XP Mode or VMware as the dev platform for such tools. I'm a programmer, and am about to upgrade to a new Windows 7 machine (quad, 4GB). It is not currently accepting new answers or interactions. This question and its answers are locked because the question is off-topic but has historical significance. So I decided to reinstall them.Īfter the Reinstall of VMware tools, everything seemed to work fine again.Locked. This could be because of some configuration mismatch of the VMware tools. In the log file of the vm (which can be found in the finder by opening the package content of the vm) I saw lots of configuration errors in the logs, and some conflicts with VMware tools.

Still this didn’t solve the issue for me, but I guess in some cases this trick could work. Then I added a new adapter again and turned on the VM.

So I turned down the VM, and removed the original adapter in the VM settings. Since troubleshooting tools are limited on VMware Fusion, compared to a full vSphere environment, I decided to just try some standard tricks out. Still, the problem looked like an issue that I have experienced on ESXi hosts in the past, where to problem was caused by the network adapter that is set in the VM settings.

After doing all the basic checks (NAT configured, Windows Firewall, Network adapter connected in VM) I didn’t had a clue what was causing the issue. Recently I had a weird issue that a Windows 7 virtual machine on VMware Fusion (10.1) wasn’t able to make any network connections.
