if you have x3100 M4, you install new bios (UEFI):
I have the same problem with Supermicro X9SCL-F board.
I've searched for Video Memory option in the Bios, but there is nothing like that!
Just this : Boot graphic adapter priority [onboard vga]
any idea ?
I am having the same issue with 5.1. I have a proliant ML150 G6 and it is on the HCL list. I have tried using the VMWare Custom CD from HP - i get further, but still ends with the same message of "relocating modules and starting up the kernel". The only onboard video options I have are "auto detect or "always enabled". Tried both settings - same result. Anyone have suggestions?
Sorry to bring this up again but I have a similar issue and was hoping someone could help.
i get the same message but in my system there is no option in bios to change onboard video.
we have IBM X3250 M4 which is on the hcl. I have tried both 5 and 5.1
I am having the same problem here.
Asus KFSN4-DRE/SAS mobo on BIOS version 1010
No onboard video settings that I can find to change the memory, have tried ESX 4 and 5 with the same issue. Even tried loading Windows Server 2008 and it just reboots after loading the Windows installation files. Tried new hard drive, tried loading from CD-ROM and USB, tried decreasing the RAM.
Anyone have any ideas?
I never managed to sort this problem, so I gave up in the end. If you manage to get some help and figure it out I would love to hear how you resolved it.
I was going to install windows server back onto the server and try and remotely install it.
I'm also running into the same issues as many of you are - "Relocating modules and starting up the kernel"
I'm pretty convinced it is a video memory issue based off most of your responses - however my only options on adjustments of my onboard video memory is Auto, 32mb, 64mb, and up to 1024mb. Nothing close to the 8mb as noted for many. I'm thinking about looking for a video card that might do the trick and disable my onboard video with lack of other options that I can see up to this point. Any recommendations on a PCIe video card that might do the trick?
Also I have to say I really do think this community is great! It's really too bad such a small issue is preventing many of us from booting our systems.
Hi kustomise, I think I have the same problem as you, I solved it by disabling the intel virtualization technology from BIOS, then install vmware, and once installed re-enable this option. I' m sorry for my English, is very bad. regards
1 person found this helpful
I have just been looking into this issue and have found that this may be expected behaviour with some servers which are reporting themselves as "headless" i.e. servers with no video display device either local or remote.
Following startup, if networking is configured, the ESXi host is reachable on the network using Ping, SSH, the vSphere Client, and vCenter Server. Virtual machines can be started and managed normally. Can you check if this is the case?
Some systems which have a video display device can be configured to report themselves as headless via the configuration, usually in the system BIOS. For these systems, it is usually preferable to use a non-headless configuration.
Systems which are known to expose a Headless configuration option in the system BIOS include:
Oracle Sun x5220 - Section 184.108.40.206 of the X5220 Server Service Manual
Oracle Sun x6270 - Section B.2.0.4 of the X6270 Server Service Manual
Oracle Sun x4600 - Section 220.127.116.11 of the X4600 Server Service Manual
For other servers, consult the hardware vendor.
You may also try the following:
If the server hardware platform has a display device but claims to be headless in the ACPI configuration and does not provide a way to configure it in the BIOS, use an advanced VMkernel boot-time configuration option to ignore the ACPI configuration and use the local console anyway.
- Press Shift+O during startup of an ESXi 5.5 installation.
- Append the boot option
- Press the Enter key to continue boot.
- Once installation is completed, set the VMkernel boot-time parameter in persistent configuration using the command:
esxcfg-advcfg -k TRUE ignoreHeadless
Setting the headless option to dis-abled in the (ACPI portion of the ) bios did the trick for me. I was able to get vsphere 5.5 loaded on a legacy AMD system.
Same here, could not install ESXi 5.5 on H8DGi-F and was struggling for couple of hours. All my troubles went away after disabling headless ACPI option in BIOS.
Hello and thanks for posting this tip, booting with manual shift+O mode works for me since there is no ACPI option in my bios on x4170 M2.
Altho, i cannot get esxcfg-advcfg -k TRUE ignoreHeadless to work.
Since 5.5 vCLI this is the command i use:
esxcli -s serverip system settings kernel set -s=ignoreHeadless -v=TRUE
It changes the value to TRUE as i can check with kernel list -o IgnoreHeadless
BUT, when i reboot it still doesnt boot until i SHIFT+O and type IgnoreHeadless=TRUE, i check the value again in esxcli and its now FALSE.
That tells me the value is not getting saved when i reboot, got any tips?
I managed to overcome this issue by issuing the following command in the ESXi local console, as the command mentioned above, esxcfg-advcfg -k TRUE ignoreHeadless, didn't work for me either:
After restarting the server, the change seems to be persistent and the server itself boots with no problems.
Hope it helps.
this error relates to the amount of memory modules being to high.
try installing less than 16gb or ram during the esxi 5.5 install process, then when its all done increase to 64gb.
try to use esx4 dvd boot disc as a hardware health check, as that is the full install, version 5 is a cutdown esxi hyperviser, by using esx4 install dvd you can quickly discover any actual hardware issues with your servers, as this dvd contains alot more drivers and is compatable with a higher variety of boards.
then once those are fixed try esxi 5.5 update 1 cd.