If you’ve used any of VMware’s products you’ve probably been frustrated by trying to boot a VM from CD. Not when you install the OS, but after the VM has been operating. For example when you need to grow the size of the virtual disk and you try to boot the VM from the GParted LiveCD. The VM’s BIOS is set to boot from disk first, so you need to change the boot device order. The problem is that the boot process is so fast it seems you have less than a second to hit F2 and enter Setup, and you have to be really quick with your mouse getting the cursor inside the VM. I bet you never thought you could get aggravated over a server booting too fast! Here’s the two methods I know of to catch the VM during boot so you can enter Setup.
The first method is to
keep your mouse inside the VM’s console window and start pressing F2 upon rebooting. Start from the running VM and reboot it or use CRTL + ALT + INS if you can. Watch for the black screen with the white VMware logo. That’s when you need to hit F2. Hitting F2 repeatedly is your best bet if it’s too quick. Simple, but effective.
Recently I discovered a second method from vinternals.com which requires modifying the .vmx file of the VM to delay the boot. VM boot screen timeout is a post which explains that you can add the following line to any .vmx file
For example, a setting of 15000 gives you 15 seconds to hit F2. I add the setting usually somewhere at the top of the .vmx file, but I do not think the position of the setting matters.
- Increase the size of a virtual disk on ESX
When I need to increase the size of a virtual disk (.vmdk) I use the console command vmkfstools and the Gparted LiveCD. If you did not know, Gparted is an open source Partition Magic […]
- Increase the size of a virtual machine disk on VMware Server and Workstation
If you have a VM running on the free VMware Server or VMware Workstation that is running out of disk space then you can use the command line tool vmware-vdiskmanager to grow the virtual […]
- Use VMware Converter to Solve ESX Snapshot Issues
Carlo Costanzo over at ipmer.com has a great post about how to quickly and easily solve issues resulting from VM snapshots. As Carlo points out, too many administrators misunderstand […]
- ESX 3.0.1 VMs reboot when adding host to VC 2.5
Last week I was helping a client upgrade to VI 3.5 and experienced some unexpected VM reboots. Unfortunately I did not discover the reason it happened until after the upgrade. I was […]
- Virtual Machine Sniffer on ESX Hosts
If you thought that because all ESX virtual machines (VM) share a virtual portgroup on a virtual switch (vSwitch) inside an ESX host you could easily sniff all VM traffic with a protocol […]
- Use the VI Client to grow a virtual disk
Some of the following text and instructions were copied in part from the post VMware ESX 3.5 and VirtualCenter 2.5 small features guide by Eric Siebert found on […]
- Use the VI Client to bulk upgrade VM tools
The last steps of the VI3 upgrade process involve the virtual machines. Upgrading the VM hardware and the installed VM tools complete the virtual infrastructure migration, but can be a […]
- Mass Import VMs to New ESX Host by .VMX files
One of the advantages of running virtual machines (VMs) on shared storage is that if you need to rebuild your ESX host(s) you won't lose your VMFS volumes or the VMs. But, what if you […]
- Search for VM Snapshots from the Service Console
There are several ways to determine if you have virtual machines with snapshots. Why you would want to know has been covered In various other posts both here at VM /ETC as well as on the […]
- Why do I need to install VMware Tools?
It happens more frequently than I would ever imagine, but from time to time I find clients have not installed the VMware tools in their virtual machine's (VM) operating system. I find it […]