Correct - I have had this happen on a couple of occasions, when I have to shutdown the host system hard due to host software lockup, not associated with VMware.
Re-running the config script will not blow out your config, as it asks if you want to keep it the same for networking, and wha-la - your VM hosts will be talking to the network again. I have not done any further research to see if this is a defect in VMware Server, or if it's host dependent(*nix, osx, win). If you find there is a defect, please let us know as well.
Hope this helped.
Thanks
Daniel Parraz
Bryan O'Neal <
BONeal@cornerstonehome.com> wrote: This happens to me from time to time on my PC's. I just rerun the
configuration script and it has always worked. Usually some upgrade or
configuration change on the host OS is the culprit though.
-----Original Message-----
From:
plug-discuss-bounces@lists.plug.phoenix.az.us
[
mailto:plug-discuss-bounces@lists.plug.phoenix.az.us] On Behalf Of Lynn
David Newton
Sent: Friday, April 27, 2007 9:16 AM
To: PLUG
Subject: virtual machines not on the net
I'm sure there are some VMware experts out there.
I'm running VMware Fusion Beta on my Macbook Pro. I
have three virtual machines: Ubuntu 7.04, openSUSE
10.2, and Windows XP, all working fine, or they were.
Yesterday something the external drive on my iMac
(which mostly sits idle) briefly went south for some
unknown reason. I had stuff shared off that system,
e.g., my iTunes library and the main disk drive, so
this caused correspondingly bogus behavior on my MBP,
noticed at first within two of my virtual machines.
Eventually the only thing I could do was to kill VMware
from a command line, since it became inoperable. Things
remained sluggish until I finally realized that the
real culprit was (evidently) the iMac, which I was only
able to recover by pulling the plug out of the socket.
After that, I brought up all three virtual machines two
or three times, but have been unable to get a network
connection on any of them.
On one VM (Ubuntu), ifup keeps fetching me addresses
like 169.254.2.158 rather than a 192.168.N.N. On the
SUSE VM it tells me that DHCP is running in the
background looking for leases, but never finds one.
Windows is no better, but I know almost nothing about
Windows or how to fix it. In any case, I don't believe
that the VMs themselves are the problem, but that
VMware itself is confused. I've tinkered with the
Settings to no avail.
Any ideas where to go from here? All of my machines are
useless to me in that condition. My real machines are
all fine.
--
Lynn David Newton
Phoenix, AZ
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)