Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 144140

Re: ESXi 5.1: cannot bring up ethernet for guest system

$
0
0

In the first article it seems to me that the issue is with vMottion (I remember another article which referred to vShield) or the usage of too many ports. The other link you gave me contains just an empty sheet (even after registering and login I saw no more).

 

But this is just the first port I want to use.

 

I tried now to reinstall the VMWare guest tools in an older version.

 

http://packages.vmware.com/tools/esx/5.1p01/rhel6/index.html

 

Because the manual says sometihing "don't take the latest - they won't work. So I tried 5.1p01 now but unfortuately the result is the same.

 

I wonder whether it has anything to do with this vswitch stuff. Currentyly it looks line this:

 

Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks  

vSwitch0         128         4           128               1500    vmnic0   

 

  PortGroup Name        VLAN ID  Used Ports  Uplinks  

  VM Network            0        0           vmnic0   

  Management Network    0        1           vmnic0   

 

Is there anything one has to assign or configure about all this or should it work "out of the box"?

 

It is also not clear to me what "Used = 4" means. Does it mean that I have 4 ports in usage? If yes: what ports? From what I understand there is an uplink and the port I use for my VM.

 

In my vmx file I just put this:

 

ethernet0.present = "TRUE"

ethernet0.startConnected = "TRUE"

ethernet0.pciSlotNumber = "-1"

ethernet0.virtualDev="vmxnet"

ethernet0.networkName="ACS"

ethernet0.addressType="generated"

ethernet0.connectionType = "bridged"

 

But as I said I triied with other combinations.

 

Unfortunatly the output of the logfile is of now much use for me since I don't have experience on this.


Viewing all articles
Browse latest Browse all 144140

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>