Try doing this:
vSphere Client -> ESX/vCenter -> Left-click on the ESX server -> Configuration -> Advanced Settings -> Vmkernel -> vmkernel.boot.usenumainfo -> uncheck (this may require a reboot if it doesnt take effect right away)
thanks for the reply
but still im getting same message after adding numa=off in grub.conf
Same issue here with ESX 4 U1 running in Workstation. Was not there when using ESX 4.
Does not seem to stop it working though...
Try doing this:
vSphere Client -> ESX/vCenter -> Left-click on the ESX server -> Configuration -> Advanced Settings -> Vmkernel -> vmkernel.boot.usenumainfo -> uncheck (this may require a reboot if it doesnt take effect right away)
thanks. im not getting that message again.
I'm also getting this error on a newly rebuilt host using the ESX 4.0 Update 1 iso (build 208167). On all other hosts using previous 4.0 iso's this has never come up. Does anyone know what specifically this error is referring to or why it's coming up now?
Thanks, Nick
this is kind of work around does anybody know what this error is allabt
I found this article on Dell's site. It might shed some light on it.
-Polen
Polen,
Those release notes completely answered my question. I hadn't mentioned it before but my error is happening on Dell hardware. Seems strange that a big red error can be safely ignored but the workaround posted earlier takes care of that. I'm also surprised that searching Dell's site didn't find that article but after digging for a bit I found where that PDF was kept. Thanks for the reply.
Nick
Just so you know, this also happens on my HP DL580 G4. I was wondering whether or not it was in relation with the fact that this server, using Intel Xeon 7130M CPUs does not support EVC.
Thanks......the solution given by dmadden works fine.
Hi I got he dhcp IP address on my esx 4.0 U2 but the same is not pinging with my desktop pc. I have installed esx on workstation.
my workstation vlan ip address is 192.168.168.1 and 192.168.132.1 from esx worksation vllan ip are pingable.