Previously we talked about Aruba Cloud’s 1 Euro 1 GB server. Aruba Cloud’s higher plans supports all features VMware provides. If you are using VMWare vSphere, your Webhost may have no restriction to virtual BIOS setup. Here is How To Enter VMware Virtual Server BIOS.
What is Virtual Server BIOS Setup?
When there is operating system, there will be some kind of BIOS. BIOS is for virtual hardware. It is basically needs what some hosts say “dedicated cloud”. It does sound promising like KVM Switch over IP, but obviously it is no way closest to real hardware tweak. While a Virtual Server BIOS is similar to a BIOS on a physical server, its functionality is often limited when compared to the BIOS of a physical machine and in most cases the only available setting accessible from a VM BIOS is the boot order.
Advertisement---
How To Enter VMware Virtual Server BIOS Setup
You need VMware vSphere Client and the Console. Start up the Cloud Server Instance and before the Cloud Server loads the operating system quickly press F2 to access the BIOS of the Cloud Server. To complete this operation successfully you need to be very quick as the amount of time available is very little. Also you can try several times using the Send Ctrl-Alt-del command found in the VM Menu. Screen looks pathetic.
Specifically for Aruba Cloud or your own installation of VMWare, on the left hand side section of control panel, you’ll get the download link of vSphere Client, details are written here :
1 | http://kb.arubacloud.com/en/computing/access-to-cloud-servers/connecting-to-the-cloud-server-service-via-vmware-vsphere-client.aspx |
Another way to force the virtual machine to enter the BIOS setup once only, is to add :
1 | bios.forceSetupOnce = "TRUE" |
to virtual server’s .vmx file.
or set :
1 | bios.bootDelay = "xxxx" |
in the .vmx file, where xxxx is the number of milliseconds during which the VM will wait for the F2 signal. Official documentation is here :
1 | https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004129 |
