Hi,
Have setup my ESXi successfully and checked configuration.
Both networkcards show up in ESXi but only one of them in
OpenSuse.
Can it be a problem with not installed VMware tools yet?
Have to figure out how to install VMware tools over a console window
(not so Linux experienced)
The network adapters are
One onboard adapter (wich works OK)
One PCI card adapter wich doesn’t show up at all
Any ideas?
Sincerely,
DB
Hi there,
If I understand you correctly, you have installed ESXi on a box, and then installed OpenSuse as a guest. Suse see’s one NIC and you are expecting it to see two.
If that is the case then here is the deal - the NIC the guest sees is a virtual NIC, and is configured in the VMWare settings for the guest. You can even select the type of NIC, set the MAC address etc. If you want OpenSuse to have another NIC you have to create one in the Virtual machine settings of that Guest.
Cheers,
Lews Therin
Thanks for the fast reply.
Dora that mean that I can define as many NICs
as I want?
How about mac address; does it have to be unique?
Or just unique in My network?
Sincerely
DB
Ps. Still learning the very consept of virtualizing
I think there is a limit but generally You can define a lot of NICs for one VM. Be sure to check the ESXi manual for the exact numbers.
The mac address needs to be unique only in your network.
Best regards,
Greg
On 01/25/2011 04:06 PM, dominicus wrote:
>
> Hi,
>
> Have setup my ESXi successfully and checked configuration.
> Both networkcards show up in ESXi but only one of them in
> OpenSuse.
> Can it be a problem with not installed VMware tools yet?
> Have to figure out how to install VMware tools over a console window
> (not so Linux experienced)
>
> The network adapters are
> One onboard adapter (wich works OK)
> One PCI card adapter wich doesn’t show up at all
>
> Any ideas?
VMware ESX/ESXi have VERY strict requirements when it comes to hardware. It’s
one of the reason I now run Xen (SLES style). In my situation, ESX 4.0 works,
but the NEWER versions won’t and since my platform isn’t on their compatibility
list, it never will work again with ESX/ESXi.
So… for me, I was faced with either, doing something else, or buying a VERY
expensive “supported” platform (mind you, in VMware terms, supported means
“temporarily supported”).
If your NIC is NOT on the official VMware HCL (you can find that through their
web site), then it simply may never work. VMware is NOT Linux and it’s not even
Xen… it’s their own thing and it’s OWNED (driver wise) by the most expensive
hardware suppliers… shoot even then, most of Dell, HP and even possibly even
IBM hardware is NOT supported with ESX/ESXi. Just the way it is.
Best advice, use a different hypervisor if at all possible. If you HAVE to use
VMware ESXi, then make sure you buy something on their HCL list (and hope it’s
still supported when 5.0 comes out).
Although to cjcox’s post I’d shout “Amen!”
Your first post leads me to believe that you may not be seeing an ESXi HCL issue.
Explain more fully, how did you determine that both NICs are properly working in ESXi, eg Did you ping the ESXi box from another machine?
Yes, VMware tools might help, it did once for me running on another VMware product years ago.
AFAIK installing VMware tools shouldn’t require ESXi access, you should be able to do it completely from within your GuestVM. If it’s not automatically available as a virtual optical device, you can either install it mounted on another VMware product or transfer the Tools file to the GuestVM and execute the file. Exact instructions will depend on whether your GuestVM was originally created on the ESXi or not, whether the Tools is Open Source (which would automatically be installed without prompting in a fresh OpenSuSE VMware VM install) or proprietary (distributed by VMware), and whether the file is a Package (eg RPM) or Source (tar file).
Also a reminder if you do transfer a VM created on another VMware product, be sure to align your partitions…
HTH,
Tony