Network not available in Guest after Upgrade to 3.0.2

[EmreB]

Hi,

I did an upgrade on a cluster pair of ESX Server from 3.0 to 3.0.2.

To perform the upgrade on the second sevrver I moved the guest systems to the updated server with VMotion.

One of the virtual machines (sigh) suffers from a network failure after being moved to the updated server.

The guest system Debian Linux Etch shows the following message on the console:

NETDEV WATCHDOG: eth0: transmit timed out

eth0: transmit timed out, status 0073, resetting.

I trieda couple of things to restore networking, like reinstalling VMWare Tools, editing the appropriate udev file, and yes, also rebooting the guest but no success.

Anyone have an idea what the problem might be?

Cheers,

Emre

[Veee]

Hi EmreB,

I suppose Debian linux is not supported on ESX 3.x. Even Ubuntu is only supported on ESX 3.0.2 (Ubuntu Linux 7.04 only). So your problem may be due to some compatibility issue. Check out list of supported Guest OS list: http://www.vmware.com/pdf/GuestOS_guide.pdf

Regards,

- Veee

[EmreB]

Hi Vee,

thanks for the hint and the quick reply.

We have been using Debian on VMWare ESX 3.X for quite some time now so it is basically possible.

There about a dozen other virtual machines that work perfect even after the upgrade to 3.0.2.

Only a single machine (that has initially been cloned from another server that is also working right now) makes trouble.

The error is strange indeed ...

Cheers,

Emre

[Emre]

Hi,

the problem is solved.

Looking through the settings of the vSwitch on the ESX server I noticed that it had been configured with 24 ports. The last virtual server that did not get any network connectivity after vmotion obviously did not have a "port" left on the "switch".

Cheers,

Emre