VMware Communities
nohill
Contributor
Contributor

VMware Fusion 2.0.2 – can't install Tools - Fusion still crashing entire machine on reboot

Hi there,

I've just downloaded 2.0.2 (light). First installation didn't complete: "this machine is not supported". Second installation worked, but I get an error message when trying to update the Tools within the virtual machine:

Internal Error 2229? What's even more disturbing: a reboot or shutdown of WinXP still causes the host to Kernel Panic. iMac 2.4 C2D, 4 GB RAM, X.5.6

Any hints, please?

Jason

One more thing: after "manually" deinstalling the Tools via the software control panel of XP and reinstalling the current Tools, this part is working now. But I do still experience Kernel Panics with every shutdown of XP.

Message was edited by: nohill

Tags (1)
0 Kudos
9 Replies
admin
Immortal
Immortal

Jason - crashing the host is something that we don't like...

Here's some links that might help you give us the information we need to look at this:

HOWTO: Ask (and answer) questions

and

Thanks -

Kevin

0 Kudos
nohill
Contributor
Contributor

Hi Kevin. Thanks for responding. I've attached the details.

If something's missing, please point it out to me.

Jason

0 Kudos
admin
Immortal
Immortal

Hi Jason,

Are you running a none English version of Windows? If so you will need to first uninstall tools and then reinstall them inorder to get them to upgrade properly, we are aware of the issue and are

looking into it. This issue seems to only reproduce on none English

language versions of Windows only. I

1. Take a snapshot of your virtual machine or create a backup

2. Power on your Windows virtual machine

3. Log into the vm with an administrator level account.

4. Navigate to start->control panel-> add or remove programs

5. Within add remove programs chose to remove VMware tools

6. Upon completion of the tools uninstall you will be prompted to reboot the VM please reboot it.

7. When the vm boots up lo back in with and administrator level account

8. The found new hardware wizard will be open, chose to cancel it, this

may happen twice, you will then be prompted to restart your computer

tell it no

9. Navigate to the VMware Fusion Virtual Machine Menu and select Install VMware Tools

10. The tools should begin to install, if they do not then from with in

the virtual machine navigate to my computer and double click on the

VMware tools cdrom

11. This should start the tools installation.

12. At this point follow the prompts to install the tool.

13. Once completed you will be asked to restart your virtual machine again.

14. Once the virtual machine has rebooted you should see that the tools

are up to date, you should no longer see the exclamation mark on the

tools icon in the windows tray.

0 Kudos
nohill
Contributor
Contributor

Thanks, jagged18!

As I have already indicated in my initial post, I was able to install the Tools after removing the old version. I basically did what you pointed out. And yes, I'm using a german WinXPproSP3. The annoying problem with the complete lockup of the host Mac still persists.

0 Kudos
admin
Immortal
Immortal

Jason -

Can you post your panic.log file. Also please post your trap/panic message.

Please check for a PM.

Thanks -

Kevin

0 Kudos
nohill
Contributor
Contributor

I've enclosed the panic logs. Where can I find the messages?

0 Kudos
HPReg
VMware Employee
VMware Employee

The specific "USB-related host panic on guest shutdown" issue is now being discussed at http://communities.vmware.com/message/1172972#1172972 .

0 Kudos
admin
Immortal
Immortal

These panic logs indicate a known Apple bug with 10.5.6 and USB devices. We've reported it to them and they've said it's a duplicate of bug 6462681.

0 Kudos
admin
Immortal
Immortal

Jason -

As noted, this is an Apple bug, filed with them.

Possible workarounds include unplugging USB devices when shutting down/rebooting the VM. This might not work, though, as it seems to be triggered by certain drivers. From reading our own internal bug reports, just having the drivers shouldn't crash the system, but your mileage might vary. Apparently, we were seeing problems simply running some devices, as opposed to you seeing the crash on VM shutdown.

You can see a mention of this bug at cocoabuilder discussion .

Kevin

0 Kudos