Shutdown surprise!

[paulinpaloalto]

My apologies if this has already been reported or covered elsewhere,

but the VMTN search engine leaves a little to be desired.

I am running VMware Fusion Beta3 on a Core2 Duo MacBook.

I had two VMs currently open: one running Vista and one running

XP Pro. The Vista VM was in full screen mode and I hit the little

red "power" button on the Vista "start" menu. What I thought

would happen was that Vista would shut down. What actually

happened was VMware quit and apparently suspended my other

open VM (the XP Pro one) as well.

Color me surprised. This seems to me to violate the "Principle

of Least Astonishment", a hallowed principle of user interface

design. Why should powering down one VM affect another

currently active VM?

I'd report this as a bug, if only I were smart enough to figure

out how to do that on the VMTN website.

Regards,

Paul

[admin]

Why should powering down one VM affect another currently active VM?

It shouldn't, and I haven't heard of this happening before. This is a bug and you should report it.

I'd report this as a bug, if only I were smart enough to figure out how to do that on the VMTN website.

There used to be a sticky with the link, but it disappeared - hopefully it'll be back soon. In the meantime, the link is http://www.vmware.com/r/support_requests.html

[paulinpaloalto]

Thanks for the quick response.

Well, I just tried to reproduce the problem several times and cannot.

Sigh. I'm sure I didn't imagine it.

[admin]

Color me surprised. This seems to me to violate the "Principle

of Least Astonishment", a hallowed principle of user interface

design. Why should powering down one VM affect another

currently active VM?

It shouldn't, and doesn't, in general.

Probably what happened is Fusion crashed. (Likely just the UI process crashed, and your XP Pro VM continued to run invisibly in the background.) Look for logfiles in ~/Library/Logs/VMware Fusion to see if there's any evidence of a crash? If you've been using Fusion for days since then, maybe the relevant logs have already been overwritten though.