• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

VMware ESX 3i 3.5.0

T

tgray96

[H]ard|Gawd
Joined
Dec 13, 2010
Messages
1,055
Ok so i installed it, and i cant configure networking... any ideas? it tells me to download tools to manage this host from: http://0.0.0.0/ (STATIC)..... any ideas? Thanks Guys
 
NIc not recognized.
If you aren't running Intel or Broadcom NICs
you will likely need to load a driver for whatever NIC you do have - if one is available.

If you really want to tinker ... try the vm-help.com site as many folks there have
done non Intel/Broadcom NIC setups.

Honestly, $30 for an Intel gigabit NIC is money well spent.
 
where do i find the drivers and how do i load them? i kno know....... i am a n00b to this.... thanks dude
 
ok i changed to a system with realtek cards, anyway when it gets to the yellow install/config screnn it goes to a purple screen with serveral lines of crap... the last on reading " Remote Debugger activated. Local Debugger no longer available" any ideas?
 
i am gonna call it " The Purple Screen of Death" since i cant get past it....
 
tgray96 said:
ok i changed to a system with realtek cards, anyway when it gets to the yellow install/config screnn it goes to a purple screen with serveral lines of crap... the last on reading " Remote Debugger activated. Local Debugger no longer available" any ideas?
Click to expand...

You changed to a different system, so you got a different result.
I am not surprised by this for some odd reason.

You may want to post your hardware specs of the systems
you are working with.

Even with the Realtek NICs you need to do some customizing and that
info is available on the vm-help site ..search for it ...customizing oem.tgz
or something similar.

Did i already mention that $30 for an Intel nic would be money well spent??
But then again...the rest of your hardware may make that a pointless venture
as well.
 
Have you tried installing the tools? You can install tools from the menu while your virtual machines are off. Other wise you can get the tools from the website. If that does not work, go with what other people suggested. We had this issue at KSU with virtual machines that were Windows 7 based, but we did not get the purple screen of death. What we had was the network adapters in windows 7 would not find the internet.
 
roaf85 said:
Have you tried installing the tools? You can install tools from the menu while your virtual machines are off. Other wise you can get the tools from the website. If that does not work, go with what other people suggested. We had this issue at KSU with virtual machines that were Windows 7 based, but we did not get the purple screen of death. What we had was the network adapters in windows 7 would not find the internet.
Click to expand...

ESX is crashing (purple screen of death), not VMs. ESX/ESXi have a VERY limited hardware compatibility list. ESX/ESXi is not Windows, where running on every hardware combnation known to man is a design goal.

If your components are not on that list, it takes hardcore tweaking with user drivers to get it to work. If you aren't comfortable with working with Linux modules for drivers, and custom building gzipped tarballs; stick with hardware that is actually supported. That being said, always use the very latest version of ESX/ESXi that is avaiable. ESXi 4.1 supports a much greater range of hardware than previous revisions, quite a bit greater even than ESXi 4.0.

I'm comfortable doing those sorts of things, but I buy $30 Intel NICs because its not worth the time to me to spend doing that stuff, and because running on supported hardware is completely reliable.

Netwerkz101 is giving excellent advice.
 
nessus said:
ESX is crashing (purple screen of death), not VMs. ESX/ESXi have a VERY limited hardware compatibility list. ESX/ESXi is not Windows, where running on every hardware combnation known to man is a design goal.

If your components are not on that list, it takes hardcore tweaking with user drivers to get it to work. If you aren't comfortable with working with Linux modules for drivers, and custom building gzipped tarballs; stick with hardware that is actually supported. That being said, always use the very latest version of ESX/ESXi that is avaiable. ESXi 4.1 supports a much greater range of hardware than previous revisions, quite a bit greater even than ESXi 4.0.

I'm comfortable doing those sorts of things, but I buy $30 Intel NICs because its not worth the time to me to spend doing that stuff, and because running on supported hardware is completely reliable.

Netwerkz101 is giving excellent advice.
Click to expand...

I misread sorry. Netwerkz101 advice is spot on.
 
Thanks guys :), i went ahead and downloaded 4.1, and i just have to replace a fualty stick of ram and i'll be in business....... Thanks for sll the help!
 
You must log in or register to reply here.
Back
Top