| layout |
|---|
default |
Remember:
VMs are created by instantiating a
template. When you create a VM, the HPC Cloud looks for a place to run it where there actually is enough room. Then it copies theimages there and it starts a hypervisor (in our case, KVM); that is your VM. The hypervisor will look at the drives that exist within theimages and try to boot an operating system from them.
On the OS Booting tab of the template-editing screen you can specify information that you want KVM to know so that your VM boots according to that.
There are 4 subsections on this tab:
- Boot: for general booting options
- Kernel: to boot from specific
kernels - Ramdisk: to attach
ramdisks - Features: other low-level virtual hardware-related options
Our recommendation on this OS Booting tab is that in the Features subsection you check for ACPI: Yes and Localtime: No. That way, your VM will take the time from the hardware where it is running, and it may help it recover the time after you STOP it.
NOTE on the OS Booting options:
The OS Booting options that you can see on the screen are very specific ones that we do not use every day. If you think you need to use them, we recommend you try and learn about them on the official OpenNebula documentation (for example, here). And if you find benefits in using them, please send us an e-mail to let us know: [email protected].