Sorry for the inconvenience. We do monitor these threads, but it's not a paid support mechanism, so we aren't able to guarantee replies.

Can you please post your VMware Tools logs and vmware.log?

Is this virtual machine imported from Parallels, or did you create it with VMware Fusion 1?

Does this reproduce on a new virtual machine, or only the one you brought in from Fusion 1?

Thanks,

Ben

Thanks for posting your vmware.log! The one with Tools installed definitely shows a one minute gap during the boot:

Jan 12 08:31:46.599: vcpu-0| Guest: toolbox: Version: build-128865
Jan 12 08:31:46.600: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Jan 12 08:31:46.946: vcpu-0| TOOLS state change 3 returned status 1
Jan 12 08:32:46.580: vcpu-0| MKS Backdoor get pointer: first time, notify tools are running
Jan 12 08:32:47.180: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

This is a very large gap. There should be only a small delay between the "TOOLS state change 3" line and the next line. In my VMs, I usually see just a few seconds' gap here:

Jan 05 15:17:53.549: vcpu-0| Guest: toolbox: Version: build-XXXXXX
Jan 05 15:17:53.549: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Jan 05 15:17:54.380: vcpu-0| TOOLS state change 3 returned status 1
Jan 05 15:17:58.768: vcpu-0| MKS Backdoor get pointer: first time, notify tools are running
Jan 05 15:17:59.572: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

Can you enable VMware Tools debug logging and send us the logs from inside the guest? Here's instructions on how to do that (see the section "Collect Tools installation logs"):

http://communities.vmware.com/docs/DOC-8720

Thanks,

Ben

Mr. Gerzfield, I was wondering if you saw something in these logs or my comments to explain the slow boot times? I was wondering if this had to do with installing VMWare tools into a converted VM and maybe the old VMWare tools is not allowing the new ones (v 2.0.1) to install properly. I did try to de-install and re-install VMware tools into the converted XP VM.
Rob

Begin forwarded message:

From: Rob Tholemeier <rob_tholemeier@ix.netcom.com<mailto:rob_tholemeier@ix.netcom.com>>
Date: 13 January 2009 16:05:54 EST
To: bgertzfield <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>
Subject: Re: VMware Fusion New message: "Bug hunt: Extremely slow boot times" 19AUXZ-1iW3-4Noi

Ok, I am not much of a Windows guy. Much better on Mac, Unix or Vax/VMS.

I could not find tools.conf where the link below suggested. I figured out how to search Windows for the file "tools.conf" and it was found in c:\Documents and Settings\All Users\Application Data\VMware\VMware Tools.

I made the additions to this file to capture the logs and here they are:

I converted this VM from Fusion v 1.1.2 to Fusion v.2.0.1. As part of
the upgrade to Fusion v.2.0.1 instructions. It has never been a
Parallels or Boot Camp VM.