Note that these are the default values and could be overridden in the IMAGE and VM templates!
The addon could use fstrim/fsthaw to create consistent snapshots/backups. The option enables the host side of the setup. The qemu-guest-agent
must be running inside the VM.
(default)
FEATURES = [ PAE = "no", ACPI = "yes", APIC = "no", HYPERV = "no", GUEST_AGENT = "no" ]
(suggested)
FEATURES = [ PAE = "no", ACPI = "yes", APIC = "no", HYPERV = "no", GUEST_AGENT = "yes" ]
Add defaults for io
and discard
.
(default)
DISK = [ driver = "raw" , cache = "none"]
(suggested)
DISK = [ driver = "raw" , cache = "none" , io = "native" , discard = "unmap" ]
or /var/lib/one/remotes/vmm/kvm/kvmrc for OpenNebula before version 5.6
Uncomment to enable.
(default)
#DEFAULT_ATTACH_CACHE=none
(suggested)
DEFAULT_ATTACH_CACHE=none
Uncomment to enable
(default)
#DEFAULT_ATTACH_DISCARD=unmap
(suggested)
DEFAULT_ATTACH_DISCARD=unmap
Uncomment and set to native
(default)
#DEFAULT_ATTACH_IO=
(suggested)
DEFAULT_ATTACH_IO=native
!!! Warning !!! These features are changing the defalt behavior of OpenNebula and should be used when the StorPool addon is the only storage driver and used for both SYSTEM and IMAGE datastores!
The feature is working only with recent version of StorPool. Please contact StorPool Support for details.
The StorPool addon can re purpose the OpenNebula's interface for VM snapshots to do atomic snapshots on all VM disks at once. In addition there is an option to enable FSFREEZE before snapshotting and FSTHAW after the snapshots are taken.
To enable the feature do the following changes.
ARGUMENTS = "-t 15 -r 0 kvm -l snapshotcreate=snapshot_create-storpool,snapshotrevert=snapshot_revert-storpool,snapshotdelete=snapshot_delete-storpool",
KEEP_SNAPSHOTS = "yes",
VMSNAPSHOT_OVERRIDE=1
VMSNAPSHOT_FSFREEZE=1
Please restart the opennebula
service to activate the changes.
To tell the OpenNebula's scheduler to deploy the VMs only on StorPool backed SYSTEM datastores set
SCHED_DS_REQUIREMENTS
in the VM template
SCHED_DS_REQUIREMENTS="TM_MAD=storpool"
Using sunstone it is located in "Update VM template" -> "Scheduling" -> "Placement" -> "Datastore Requirements".
Set the "Expression" to TM_MAD=storpool
Define an OpenNebula cluster selecting only StorPool backed SYSTEM and IMAGE datastores. Keep in mind that in this case the images used in the VM templates must be on the datastore selected in the cluster!