Stuck on Upgrade to RC (50460)

[Speedbird]

I was in the process of upgrading my latest beta to this RC, following the instructions found in the announcement page (http://www.vmware.com/community/ann.jspa?annID=365), windows (XP SP2) booted, then started scanning for all my devices and when it got to the "Found New Hardware - PCI standard PCI-to-PCI bridge" "balloon" message (bottom-right), it just stays there and the VM just sits there not allowing me to do anything.

In addition, the VM poorly responds to mouse events, the clock mouse icon shows up whenever I am hovering over the windows bar (bottom bar), the "Found new hardware" popup is always visible, trying to install the tools just does not work (never comes up the installation program).

Is this something somebody already experienced? - I am on a MacBook C2D, 2.0Ghz, 2Gb RAM

TIA,

\-- sb

[rhind]

How long did you leave it for when it 'hung'? Mine took minutes to install the tools because of this, and appeared 'hung' for that time, but it did recover and finish installing the tools.

I then shutdown the guest, exited and re-started fusion then the guest as described in the steps, and it has been fine since.

Cheers

Russell

[Speedbird]

It's been "up" for at least 30 min, I am noticing an extremely poor performance, unfortunately I am not being able to run anything inside (to see what's going on, etc).

There is nothing installed in this VM, I use to test that my apps run also on IE (web app programs), it is basically a tock windows install, btw.

Thanks.

\-- sb

[rhind]

Yep, definitely sounds hung then.

Not sure what the best way to proceed would be. I'd just power off the VM, but it depends on how it recovers. If you have a backup, great, otherwise you could boot in to XP's safe mode and uninstall the tools and try again.

I'd probably just try re-booting and trying again, and while its installing, don't do anything until its completed.

Othewise, trying safe mode would be my next bet.

Cheers

Russell

[Speedbird]

Well, I will mark this as "solved" but I am still puzzled by the behavior of the VM after upgrade.

It basically took three boots until the problem "magically" disappeared, from what I can tell, the installation should had been left alone for the entire 40/45 min (the system was almost unresponsive during the time but it \*was* responding to events), the shutdown in the second reboot took almost 5 full minutes, at the third boot, I was able to login normally, upgrade VM tools and I am back in the game, thanks for the responses.

I also run a CentOS 4.5 VM in the same MacBook, this VM was "upgraded" without any problems, in fact I am noticing it being way more snappier than with previous versions, kudos to the VMWare team.

\-- sb