Applies to SUSE Linux Enterprise Server 12

7 Supported Guests, Hosts and Features

Supported virtualization limits for XEN and KVM are available in the Release Notes (http://www.suse.com/releasenotes/).

7.1 Supported VM Guests

This section lists the support status for various guest operating systems virtualized on top of SUSE Linux Enterprise Server 12. All guest operating systems are supported both fully-virtualized and paravirtualized with two exceptions: Windows, which is only supported fully-virtualized, and OES and NetWare operating systems, which are only supported on Xen paravirtualized. All guest operating systems are supported both in 32-bit and 64-bit flavors, unless stated otherwise (see NetWare).

Table 7.1: Paravirtualized OS Support

Operating System

Xen

SUSE Linux Enterprise Server 12

Yes

SUSE Linux Enterprise Server 11 SP3

Yes

SUSE Linux Enterprise Server 10 SP4

Yes

SUSE Linux Enterprise Server 9 SP4

Yes

Open Enterprise Server 11 SP1

Yes

Open Enterprise Server 11 SP2

Yes

Novell Netware 6.5 SP8

Yes (32-bit only)

Red Hat Enterprise Linux 5.10+

Yes (Best Effort)

Red Hat Enterprise Linux 6.5+

Yes (Best Effort)

Red Hat Enterprise Linux 7+

Yes (Best Effort)

Note
Note: Netware and OES Installation Requirements

You need a static IP address for each virtual machine running NetWare or OES. Open Enterprise Server (OES) 2 Linux can only be installed from a network installation source.

Table 7.2: Fully Virtualized OS Support

Operating System

Xen

KVM

SUSE Linux Enterprise Server 12

Yes

Yes

SUSE Linux Enterprise Server 11 SP3

Yes

Yes

SUSE Linux Enterprise Server 10 SP4

Yes

Yes

SUSE Linux Enterprise Server 9 SP4

Yes

Yes

Windows Server 2012+

Yes

Yes

Windows Server 2012 R2+

Yes

Yes

Windows Server 2008 SP2+

Yes

Yes

Windows Server 2008 R2 SP1+

Yes

Yes

Windows 2003 SP2+

Yes

Yes

Windows Vista SP2+

Yes (Best Effort)

Yes (Best Effort)

Windows 7 SP1+

Yes (Best Effort)

Yes (Best Effort)

Windows 8+

Yes (Best Effort)

Yes (Best Effort)

Windows 8.1+

Yes (Best Effort)

Yes (Best Effort)

Red Hat Enterprise Linux 5.10+

Yes (Best Effort)

Yes (Best Effort)

Red Hat Enterprise Linux 6.5+

Yes (Best Effort)

Yes (Best Effort)

Red Hat Enterprise Linux 7+

Yes (Best Effort)

Yes (Best Effort)

Note
Note: Red Hat Guest

The Red Hat* guest Operating Systems will be fully supported if the customer has purchased Expanded Support, otherwise they will be supported on a best-effort basis (fixes if reasonable).

Table 7.3: Technology preview OS Support

Operating System

Xen

KVM

SUSE Linux Enterprise Desktop 11 SP3

Yes (fixes if reasonable)

Yes (fixes if reasonable)

SUSE Linux Enterprise Desktop 12

Yes (fixes if reasonable)

Yes (fixes if reasonable)

Note
Note: Technology Preview

The operating system listed above has been tested to install and run successfully. Bugs can be reported to and will be tracked by SUSE Technical Services, but no support commitments or service level agreements apply. Potential fixes and patches will be evaluated for future inclusion.

7.1.1 Availability of Paravirtualized Drivers

To improve the performance of the guest operating system, paravirtualized drivers are provided when available. Although they are not required, it is strongly recommended to use them. The paravirtualized drivers are available as follows:

SUSE Linux Enterprise Server 12

included in Kernel

SUSE Linux Enterprise Server 11 SP1 / SP2 / SP3

included in Kernel

SUSE Linux Enterprise Server 10 SP4

included in Kernel

SUSE Linux Enterprise Server 9 SP4

not available

RedHat

available in RedHat Enterprise Linux 5.4 and newer

Windows

SUSE has developed virtio-based drivers for Windows, which are available in the Virtual Machine Driver Pack (VMDP). See http://www.suse.com/products/vmdriverpack/ for more information.

7.2 Supported VM Hosts

This section lists the support status of SUSE Linux Enterprise Server 12 running as a guest on top of various virtualization hosts (Hypervisor). Both 32-bit and 64-bit versions are supported. There is full support for SUSE host operating (for both guest and host). There is full support for third party host operating (for guest).

The following SUSE host operating systems are supported:

  • SUSE Linux Enterprise Server 11 SP3 (Xen)

  • SUSE Linux Enterprise Server 11 SP3 (KVM)

  • SUSE Linux Enterprise Server 12 (Xen)

  • SUSE Linux Enterprise Server 12 (KVM)

The following third party host operating systems are supported:

  • VMware ESX 5.1

  • VMware ESXi 5.1

  • Windows 2008 SP2+

  • Windows 2008 R2 SP1+

  • Windows 2012+

  • Windows 2012 R2+

  • Citrix XenServer 6.5

  • Oracle VM 3.2

The following SUSE and 3rd party host operating systems will be supported when released:

  • SUSE Linux Enterprise Server 12 SP1 (Xen)

  • SUSE Linux Enterprise Server 12 SP1 (KVM)

  • VMware ESX 5.2

  • VMware ESXi 5.2

  • Citrix XenServer future releases

  • Microsoft Windows Server OS future releases and service packs

  • Oracle VM 3.2

7.3 KVM Hardware Requirements

Currently, SUSE only supports KVM full virtualization on x86_64 hosts and on System z (only as Technology Preview). On the x86_64 architecture, KVM is designed around hardware virtualization features included in AMD* (AMD-V) and Intel* (VT-x) CPUs. It supports virtualization features of chipsets, and PCI devices, such as an I/O Memory Mapping Unit (IOMMU) and Single Root I/O Virtualization (SR-IOV).

On the x86_64 architecture, you can test whether your CPU supports hardware virtualization with the following command:

egrep '(vmx|svm)' /proc/cpuinfo

If this command returns no output, your processor either does not support hardware virtualization, or this feature has been disabled in the BIOS or Firmware.

The following Web sites identify x86_64 processors that support hardware virtualization: http://ark.intel.com/Products/VirtualizationTechnology (for Intel CPUs), and http://products.amd.com/ (for AMD CPUs).

Note
Note: KVM Kernel Modules Not Loading

The KVM kernel modules only load if the CPU hardware virtualization features are available.

The general minimum hardware requirements for the VM Host Server are the same as outlined in Section “System Requirements for Operating Linux”, Chapter 2, Installation on AMD64 and Intel 64, Deployment Guide. However, additional RAM for each virtualized guest is needed. It should at least be the same amount that is needed for a physical installation. It is also strongly recommended to have at least one processor core or hyper-thread for each running guest.

7.4 Feature Support

7.4.1 Host (Dom0)

Table 7.4: Feature Support - Host (Dom0)

Features

Xen

Network and Block Device hotplugging

Yes

Physical CPU hot-plugging

No

Virtual CPU hot-plugging

Yes

Virtual CPU pinning

Yes

Virtual CPU capping

Yes

Intel* VT-x2: FlexPriority, FlexMigrate (Migration constraints apply to dissimilar CPU architectures)

Yes

Intel* VT-d2 (DMA remapping with Interrupt filtering and Queued Invalidation)

Yes

AMD* IOMMU (I/O Page Table with Guest to Host Physical Address translation)

Yes

The supported features for KVM are the same as the supported features for SUSE Linux Enterprise Server 12.

Note
Note

The addition or removal of physical CPUs at runtime is not supported, however virtual CPUs can be added or removed for each VM Guest.

7.4.2 Paravirtualized Guest

Table 7.5: Feature Support - Paravirtualized Guest

Features

Xen

Virtual Network and Virtual Block Device hotplugging

Yes

Virtual CPU hot-plugging

Yes

Virtual CPU over-commitment

Yes

Dynamic Virtual Memory Resize

Yes

VM Save and Restore

Yes (Excludes SLES 9 SP4 in Multiprocessor mode)

VM Live Migration

Yes Between like virtual host systems with similar resources (Excludes SLES 9SP4 in Multiprocessor mode)

Advanced Debugging with GDBC

Yes

Dom0 metrics visible to VM

Yes

Memory Ballooning

Yes

PCI Pass Through

Yes (Guests excluded are Netware and SUSE Linux Enterprise Server 9 SP4)

For live migration, both source and target system architectures need to match; that is, the processors (AMD* or Intel*) must be the same. Unless CPU ID masking is used --such as Intel's FlexMigration -- the target should feature the same processor revision or a more recent processor revision than the source. If VMs are moved among different systems, the same rules apply for each move. To avoid failing optimized code at runtime or application startup, source and target CPUs need to expose the same processor extensions. Xen exposes the physical CPU extensions to the VMs transparently. To summarize, guests can be 32- or 64-bit, but the VHS must be identical.

Note
Note: Intel* FlexMigration

For machines that have Intel* FlexMigration, CPU-ID masking and faulting allow more flexibility in cross-CPU migration

7.4.3 Fully Virtualized Guest

Table 7.6: Feature Support - Paravirtualized Guest

Features

Xen

KVM

Virtual Network and Virtual Block Device hotplugging

Yes

Yes

Virtual CPU hot-plugging

No

No

Virtual CPU over-commitment

Yes

Yes

Dynamic Virtual Memory Resize

Yes

Yes

VM Save and Restore

Yes

Yes

VM Live Migration

Yes Between like virtual host systems with similar resources (i.e., from 32-bit to 32-bit, 64-bit to 64-bit)

Yes

VM snapshot

Yes

Yes

Advanced Debugging with GDBC

Yes

Yes

Dom0 metrics visible to VM

Yes

Yes

PCI Pass Through

Yes

Yes

Note
Note: PCI Pass Through

IOMMU is needed for PCI Pass Through, which requires underlying support from the hardware (e.g Intel* VT-d extensions or AMD* IOMMU extensions).

Note
Note: Windows Guest

Virtual Network and Virtual block device hotplugging, and Dynamic virtual memory resize, shrinking and restoring, are supported in Xen and KVM only if PV drivers are being used (VMDP).

For KVM, a detailed description of supported limits, features, recommended settings and scenarios and other useful information is maintained in the kvm-supported.txt document, available as a part of the KVM package, and located at /usr/share/doc/packages/kvm path on an installed SUSE Linux Enterprise Server 12.

Print this page