Home » VMware » VCP550D » Which virtual machine boot option should the administrator configure to resolve this issue?
A server administrator reports that a virtual machine has displayed the following message twice in the past 12 months:
No boot device found
Which virtual machine boot option should the administrator configure to resolve this issue?
A. Failed Boot Recovery
B. Force BIOS Setup
C. Boot Delay
D. Network Boot Retry
Correct Answer: A
Explanation/Reference:
Explanation:
The question states that a virtual machine has displayed the “No boot device found” message twice. This message would have occurred during a boot up of the VM and the VM would have failed to boot.
We can use the “Failed Boot Recovery” to configure the VM to automatically reboot and try again after a configured period of time (the default is 10 seconds). On rebooting, the VM might be able to find the boot device (disk) and successfully boot. This will save the administrator having to manually reboot the VM.
This setting could be useful if a storage device such as a SAN is taking longer to boot up than the VM. In this case, if the VM was attempting to boot from a disk on the storage device, the disk would be unavailable and therefore, ‘not found’ by the VM.
Incorrect Answers:
B: The Force BIOS Setup option will configure the VM to go into the BIOS configuration screen on boot up. This will not resolve a “No boot device found” error. Therefore, answer is incorrect.
C: The Boot Delay option is used to configure the VM to spend longer on the initial BIOS boot sequence. This can be useful if you need to press a key to change the boot options. However, it will not resolve a “No boot device found” error. Therefore, answer is incorrect.
D: The Network Boot Retry option configures the VM to retry a network boot. This is only useful if the VM is configured to boot from the network. If the VM is configured to boot from a disk (which is far more likely) then this option won’t help. Therefore, this answer is incorrect.
References:
http://www.virtualizetips.com/2010/07/30/failed-boot-recovery-option-a-new-feature-in-esxi-4-1/