This package supports the use of fli4l as a virtual machine. Using a 64 bit kernel for the x86_64 architecture is required.
For virtualization of a fli4l using Xen, KVM, VMware or Hyper-V this package loads the necessary kernel modules. Furthermore you can set additional options, which may be useful for the use as virtual machine.
The activation of this variable ensures that the Xen-specific kernel modules are loaded on fli4l. This is necessary if the fli4l system is virtualized using Xen.
The following drivers are loaded:
Default Setting: OPT_XEN='no'
Example: OPT_XEN='yes'
The activation of this variable ensures that the KVM-specific kernel modules are loaded on fli4l. This is necessary if the fli4l system is virtualized using KVM.
The following drivers are loaded:
Default Setting: OPT_VIRTIO='no'
Example: OPT_VIRTIO='yes'
You can start the QEMU Guest Agent4.13 on the virtualized fli4l with this option. This way the host can execute certain management functions, which need support from within the guest system. Retrieving statistics or triggering a clean shutdown or suspend is possible for example.
This option requires correspondent configuration of the virtual machine on the host side. See the documentation of KVM, virt-manager4.14 or Proxmox4.15 for that.
Default Setting: VIRTIO_QEMU_GUEST_AGENT='no'
Example: VIRTIO_QEMU_GUEST_AGENT='yes'
Activating this variable triggers loading of the specific kernel modules required for virtualizing fli4l using VMware.
The following drivers are loaded:
Default setting: OPT_VMWARE='no'
Example: OPT_VMWARE='yes'
Activating this variable ensures that Hyper-V specific kernel modules are loaded. This is necessary for the fli4l system running virtualized using Hyper-V.
The following drivers are loaded:
Default setting: OPT_HYPERV='no'
Example: OPT_HYPERV='yes'