What is the Intel® Modular Server Virtualization Manager?
The Intel® Modular Server Virtualization Manager is a virtualization solution for the Intel® Modular Server, which enables users to easily create virtualized storage pools and virtualize compute modules with a few mouse clicks, with no additional software to install.
Do I have to buy a license for each compute module I want to virtualize?
You can virtualize up to six compute modules in a single chassis with a single license. Please note the product is no longer available for purchase. See the Intel® Modular Server Virtualization Manager product discontinuance.
Are there any pre-requisites for installing the Intel® Modular Server Virtualization Manager?
The software is only supported on the Intel® Modular Server System MFSYS25V2. The firmware level must be at UFU 11.5 or 11.6, and an Intel® Shared LUN (MFSLUNKEY) license must be activated on the system prior to installing the Intel® Modular Server Virtualization Manager feature.
Can I use the Intel® Modular Server Advanced Management Pack to back up my Intel® Modular Server System MFSYS25 configuration and then import it to an Intel® Modular Server Chassis MFSYS25V2 chassis?
The restoring of a saved configuration will only work if the firmware level is the same, which is not the case between Intel® Modular Server System MFSYS25 and Intel® Modular Server System MFSYS25V2.
What happens when I virtualize a compute module?
A virtual machine storage pool is created, and the included hypervisor is extracted and installed. This process will take 10-15 minutes for the first compute module, and far less time for each subsequent compute module.
Are there any pre-requisites for virtualizing a compute module?
You can virtualize the Intel® Compute Modules MFS5520VI or Intel® Compute Module MFS5520VIR, on an Intel® Modular Server Chassis MFSYS25V2, with a single Storage Control Module (SCM). The virtual machine storage pool requires 4 SAS hard drives or SSDs. Virtualization is not supported on:
- Intel® Modular Server System MFSYS25
- Intel® Modular Server System MFSYS35
- Intel® Modular Server System MFSYS25V2 with dual SCMs
- Intel® Compute Module MFS5000SI
- Intel® Compute Module MFS2600KI
- SATA drives
- Firmware revisions 6.x or 10.x
Can I create more virtual machine pools later, if the first one runs out of capacity?
Additional virtual machine storage pools can be created from the GUI by checking the tick box “Create VM Pool” at the top of the storage pool creation window.
Is it possible to dynamically allocate more storage space in the storage pool to a virtual machine?
Although certain VM settings can be modified, the size of the original allocated storage (LUN0) cannot be increased. However, more storage space can be assigned to a VM in the form of LUN1, 2, 3 etc.
Can I edit my virtual machine settings once the VM is created?
Except for the original LUN0 assigned to the virtual machine, all VM settings can be edited.
Is there any limitation as to how many virtual machines I can create?
The number of virtual machines that can be powered on is limited by the resources on the host. Intel recommends that each VM should be configured for a minimum of 2GB of memory. Actual memory requirements for a VM are dependent on the configured guest operating system and applications running on the VM. The total number of vCPUs created for all VMs on a compute module should be equal to or less than the total number of cores available on a compute module.
It is possible to create many more virtual machines, but only those within the scope of compute module resources can be powered on.
Does the Intel® Modular Server Virtualization Manager support Live Migration?
Existing VMs can be migrated quickly by dragging and dropping them to another virtualized compute module, or by using the available action options in the GUI. This action can be used for offloading or load balancing compute modules, or in case of a hardware error.
If I activate the Intel® Modular Server Virtualization Manager, does this mean I have to virtualize all compute modules in the chassis?
Users can select which compute modules to virtualize and which compute modules to run as standalone servers. However, as virtualized and non-virtualized compute modules cannot share the same storage pool, a separate storage pool needs to be set up for non-virtualized compute modules.
Is dual SCM configuration supported by the Intel® Modular Server Virtualization Manager?
Dual SCM configuration is not supported. If a second SCM is installed in the system, users will be prompted to remove it during the setup process.
Is it possible to backup virtual machines?
There is no backup functionality built into the hypervisor or GUI. Please use other backup methods.
Is it possible to copy or clone a virtual machine?
There is no cloning or copying functionality.
Do you have any Physical-to-Virtual (P2V) or Virtual-to-Virtual (V2V) tools? What about VM import/export and VM cloning?
Download the instructions and registry patch and follow the instructions.
What’s the best way to install an operating system to a virtual machine?
When the first compute module is virtualized a VM storage pool is created. This storage pool contains a reserved space for the hypervisor to run as well as a 40GB ISO store where OS images can be placed. This ISO store can be accessed and configured from the Virtualization > Cluster Share menu on the left hand side of the GUI.
How do I access the Cluster Share to store operating system images?
From the left hand navigation menu in the GUI please go to Virtualization > Cluster Share. Depending on the IP address allocated to the Compute Management Module (CMM2), the path to the Cluster Share will have been automatically named as \\CMM_IP_Address\ISO store. Enable the cluster share in the GUI (set Export cluster share to enabled) and then map a network drive to this share from a computer on the network which contains the operating system images. You also need to create a password to access the share from the client. Once that is done, images and ISOs can be uploaded to the share. For security reasons it is advisable to disable the share when access is no longer required.
Do I need to set up the ISO store prior to creating a VM?
ISO store needs to be setup prior to creating a VM, if you intend to load an Operating System from the ISO store. The easiest way to install an operating system is from the ISO store.
How does networking work if a compute module is virtualized?
When the hypervisor is installed, simplified networking is automatically configured and should work on most networks. If VLANs have been set up on the network, default settings can be edited to match the individual network configuration. Virtual switches can be added as needed.
What are Virtio drivers?
Virtio drivers are available for the Disk Controller and Network Controller for both Linux and Windows. These drivers are designed for enhanced performance in a virtualized environment and improve OS speed by removing the need to emulate hardware by the VM. To use OS native drivers, uncheck the boxes.
Which guest operating systems are currently supported with the Intel® Modular Server Virtualization Manager?
Microsoft Windows 2008* SP2 64-bit
Microsoft Windows 2008 R2* SP1 64-bit
Red Hat Enterprise Linux 6* U1 64-bit
SUSE Linux Enterprise Server 11* SP1 x 64
Is a trial version of the Intel® Modular Server Virtualization Manager available?
A 30-day trial version is integrated into UFU 11.5 and 11.6, and can be activated from the Features menu on the left hand side in the GUI. Please note that for successful virtualization the Intel® Shared LUN key trial version, which can be found in the same place, must also be activated.
How do I activate the feature?
Please see: How do I activate features on the Intel Modular Server?
What must I do to continue using Intel® Modular Server Virtualization Manager after the 30-day trial period expires?
Please note the product is no longer available for purchase. See the Intel® Modular Server Virtualization Manager product discontinuance.
How do I map the front USB ports on the Compute Module to a VM?
USB devices are not supported by the VMs.