I have upgraded from WS 5 to WS 6 and I find that the login to my XP guest has become much slower (2-3 minutes) than was the case with WS 5. The time from initiation of login to the Windows login sound is normal, but shortly thereafter the host Task Manager shows the CPU usage going to zero. Nothing unusual shows up on the guest Event Viewer.
Comments and suggestions would be much appreciated.
I have found (on my own) the solution to my problem. On my WS 5 virtual machine, I had a share folder. When I upgraded to WS 6, sharing was automatically disabled, but my share folder was still listed in VirtualMachineSettings|Options|SharedFolders. The slow login went away when I either enabled shared folders or removed the folder entry in the Folders box.
I wonder if this is a bug, or a "feature"?
I have upgraded from WS 5 to WS 6 and I find that the
login to my XP guest has become much slower (2-3
minutes) than was the case with WS 5. The time from
initiation of login to the Windows login sound is
normal, but shortly thereafter the host Task Manager
shows the CPU usage going to zero. Nothing unusual
shows up on the guest Event Viewer.
Comments and suggestions would be much appreciated.
If you are running the guests on a machine where you are the local administrator, try disabling the vmware-authd service.
I see the same thing - get very fast past the login dialog then wait for 2 min+ for icons to show up on desktop. Enabling shared folders fixed the problem. Looks like a bug to me.
Maude Herr-Chodt,
I had experienced similar problems with slow logins and extremely slow shared folders, from my experience the problem seems to be
related to "Large Send Offload" being enabled on the host network
adapter. This seems to be VERY common among machines with an
Intel-based gigabit ethernet adapter in the host machine. It seems to
be common on Windows, Apple Mac OS X, and Linux users that all seem to
have a Gigabit Ethernet adapter (usually an Intel 1000 based adapter)
or they have a network adapter that supports Large Send Offload, and
for some reason this seems to be enabled by default, and it seems to
cause problems with VMWare products. I posted the correct solution to
this problem with detailed instructions here:
http://communities.vmware.com/message/1191790#1191790
I hope this helps, I believe this should solve your problem. Please
close this thread out, and mark it as "Answered" and If you find
this answer helpful, please do take the time to award me the "Correct Answer" points.
Thank-you!
Mark