KVM Specifications Memory foot print – Similar to any embedded virtualization layer, KVM is very thin and takes very less resources. PCI pass-through – Sometimes, the hardware might not be virtualized; therefore, the hardware must be redirected into the virtual machine (VM) for its direct control. This feature is called PCI pass-through, and there are several flavors for it: 1-1 memory mapping, para-virtual PCI, and hardware support using VT-d. For information about the KVM bits, and to make the PCI devices pass through, refer to the user documents of the respective operating systems. HBA – WarpDrives and Host Bus Adapters (HBA) connecting the back-end must be a pass-through so that the VM can have direct mapping and control of the WarpDrives and the HBAs in the server. PCI resources – The PCI resources cannot be shared across the VMs, that is, the WarpDrives and HBAs cannot be shared across the VMs. Virtual machine management – Virtual machine management (VMM) does not need external tools running in the privileged VMs or the Hypervisor to manage the VMs.
KVM Specifications
Memory foot print – Similar to any embedded virtualization layer, KVM is very thin and takes very less resources.
PCI pass-through – Sometimes, the hardware might not be virtualized; therefore, the hardware must be redirected into the virtual machine (VM) for its direct control. This feature is called PCI pass-through, and there are several flavors for it: 1-1 memory mapping, para-virtual PCI, and hardware support using VT-d.
For information about the KVM bits, and to make the PCI devices pass through, refer to the user documents of the respective operating systems.
HBA – WarpDrives and Host Bus Adapters (HBA) connecting the back-end must be a pass-through so that the VM can have direct mapping and control of the WarpDrives and the HBAs in the server.
PCI resources – The PCI resources cannot be shared across the VMs, that is, the WarpDrives and HBAs cannot be shared across the VMs.
Virtual machine management – Virtual machine management (VMM) does not need external tools running in the privileged VMs or the Hypervisor to manage the VMs.