diff --git a/xml/virt_support.xml b/xml/virt_support.xml index 9123f99163..f3341f307a 100644 --- a/xml/virt_support.xml +++ b/xml/virt_support.xml @@ -4,13 +4,11 @@ %entities; ]> - - Supported Guests, Hosts and Features + Supported Hosts, Guests, and Features - - + @@ -18,749 +16,262 @@ outlined in the Release Notes. - - Supported VM Guests - - - This section lists the support status for various guest operating systems - virtualized on top of &productname; &productnumber;. All guest operating - systems are supported both fully virtualized (FV in the - following table) and paravirtualized (PV in the following - table) with two exceptions: Windows, which is only supported - fully virtualized, 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). - - - - - Paravirtualized OS Support - - - - - - - - Operating System - - - - - FV Support (&xen;/&kvm;) - - - - - PV Support (&xen;) - - - - - - - - - - &slsa; 10 SP4 - - - - - Full - - - - - Full - - - - - - - &slsa; 11 SP3 - - - - - Full - - - - - Full - - - - - - - &slsa; 11 SP4 - - - - - Full - - - - - Full - - - - - - - &slsa; 12 - - - - - Full - - - - - Full - - - - - - - &slsa; 12 SP1 - - - - - Full - - - - - Full - - - - - - - &slsa; 12 SP2 - - - - - Full - - - - - Full - - - - - - - &slsa; 12 SP3 - - - - - Full - - - - - Full - - - - - - - &slsa; 12 SP4 - - - - - Full - - - - - Full - - - - - - - &slsa; 15 - - - - - Full - - - - - Full - - - - - - - &sleda; 12 SP2 - - - - - Technology preview1 - - - - - Technology preview1 - - - - - - - &sleda; 12 SP3 - - - - - Technology preview1 - - - - - Technology preview1 - - - - - - - OES 11 SP3 - - - - - Full - - - - - Full2 - - - - - - - OES 2015 - - - - - Full - - - - - Full2 - - - - - - - OES 2015 SP1 - - - - - Full - - - - - Full2 - - - - - - - Netware 6.5 SP8 - - - - - None - - - - - Full (32-bit only)2 - - - - - - RHEL 5.11+ - - - - Full/best effort3 - - - - - Full/best effort3 - - - - - - RHEL 6.9+ - - - - Full/best effort3 - - - - - Full/best effort3 - - - - - - RHEL 7.3+ - - - - Full/best effort3 - - - - - Full/best effort3 - - - - - - - Windows Server 2008 SP2+ - - - - - Full - - - - - None - - - - - - - Windows Server 2008 R2 SP1+ - - - - - Full - - - - - None - - - - - - - Windows Server 2012+ - - - - - Full - - - - - None - - - - - - - Windows Server 2012 R2+ - - - - - Full - - - - - None - - - - - - - Windows Server 2016 - - - - - Full - - - - - None - - - - - - - Windows Vista SP2+ - - - - - Best effort - - - - - None - - - - - - - Windows 7 SP1+ - - - - - Best effort - - - - - None - - - - - - - Windows 8+ - - - - - Best effort - - - - - None - - - - - - - Windows 8.1+ - - - - - Best effort - - - - - None - - - - - - Windows 10+ - - - Best effort - - - None - - - - -
- - - - 1 Technology preview: The operating system has - been tested to install and run successfully. Bugs can be reported 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. - - - 2 You need a static IP address for each virtual - machine running NetWare or OES. - - - 3 RedHat* guest operating systems are - fully supported with Expanded Support. Otherwise, - they will be supported on a best-effort basis (fixes if reasonable). - - - - - 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: - - - - &productname; - - - Included in kernel - - - - - &sls; 12 / 12 SP1 / 12 SP2 - - - Included in kernel - - - - - &sls; 11 / 11 SP1 / 11 SP2 / 11 SP3 / 11 SP4 - - - Included in kernel - - - - - &sls; 10 SP4 - - - Included in kernel - - - - - 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). - For more information, see - . - - - - - - - Supported &vmhost;s for &productname; &productnumber; &vmguest;s + Host Environments (Hypervisors) + This section lists the support status of &productname; &productnumber; - running as a guest on top of various virtualization hosts (). Both 32-bit and 64-bit versions are - supported for the host if available. The support status is defined as - follows: + running as a guest on top of various virtualization hosts + (). + + The following &suse; host environments are supported (&xen; + &kvm;): + + + SLES 11 SP4 + + - Full support for all &suse; host systems and &productname; - &productnumber; &vmguest;s + SLES 12 SP1, SP2, SP3, SP4, SP5 - Full support for &productname; &productnumber; &vmguest;s on third-party - host systems + SLES 15 SP0, SP1, SP2 - - - The following &suse; host operating systems are supported: - - - + + The following 3rd party host environments are supported: - &sls; 11 SP4 (&kvm;/&xen;) + VMware ESXi 6.5, 6.7 - &sls; 12 SP1 (&kvm;/&xen;) + Microsoft Windows 2008 R2 SP1+, 2012+, 2012 R2+, 2016, 2019 - &sls; 12 SP2 (&kvm;/&xen;) + Citrix XenServer 7.0, 7.1, 8.0 - + - &sls; 12 SP3 (&kvm;/&xen;) + Oracle VM 3.4 - + + + + The level of support is as follows: + + + Support for SUSE host operating systems is full L3, both for the guest and + host. + + + - &sls; 12 SP4 (&kvm;/&xen;) + Support for 3rd party host environments is full L3 for the guest and needs + the host vendor cooperation and support for the host. - + + + Support for Third Party Virtualization Hosts + + &suse; only provides full L3 support if both the virtualization host and + guest are using &suse; products. + + + If the virtualization host uses third party software, &suse; only + guarantees L3 support for the guest. For the host, the cooperation of the + vendor is required. + + + + + Guest Environments + - The following third party host operating systems are supported: + This section lists the support status for various guest operating systems + virtualized on top of &productname; &productnumber;. All guest operating + systems are supported both fully-virtualized (FV in the + following table) and paravirtualized (PV in the following + table) with two exceptions: Windows, which is only supported + fully-virtualized, 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). + The following guest operating systems are fully supported (L3): - KVM for IBM &zseries; 1.1.0 - - - - PowerKVM + + SLES 10 SP4 + - - VMware ESX 5.5 + SLES 11 SP3, SP4 - VMware ESXi 6.0 + SLES 12 SP0, SP1, SP2, SP3, SP4, SP5 - + VMware ESXi 2016 - Windows 2008 SP2+ + SLES 15 SP0, SP1, SP2 - Windows 2008 R2 SP1+ + OES 11 SP2, 2015, 2015 SP1, 2018, 2018 SP1, 2018 SP2 - Windows 2012+ + Netware 6.5 SP8 (32-bit only) - Windows 2012 R2+ + Windows Server 2008 SP2+, 2008 R2 SP1+, 2012+, 2012 R2+, 2016, 2019 + + + + The following guest operating systems are supported as a technology preview (L2, fixes if reasonable): - Microsoft Windows 2016 + SLED 15 SP1 + + + + The following Red Hat guest operating systems are fully supported (L3) if the customer has purchased Expanded Support, otherwise they will be supported on a best-effort basis (L2, fixes if reasonable): - Citrix XenServer 6.5 + RHEL 5.11+, 6.9+, 7.7+, 8.0+ + + + + The following guest operating systems are supported on a best-effort basis (L2, fixes if reasonable): - Oracle VM 3.3 + Windows 8+, 8.1+, 10+ + + + 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: + + + + &productname; + + + Included in kernel + + + + + &sls; 12 / 12 SP1 / 12 SP2 + + + Included in kernel + + + + + &sls; 11 / 11 SP1 / 11 SP2 / 11 SP3 / 11 SP4 + + + Included in kernel + + + + + &sls; 10 SP4 + + + Included in kernel + + + + + 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). For more + information, see + . + + + + + &kvm; Hardware Requirements - Currently, &suse; supports &kvm; full virtualization on - &x86-64; and &arm64; hosts, and on &zseries;. + Currently, &suse; supports &kvm; full virtualization on &x86-64; and &arm64; + hosts, and on &zseries;. + - 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 - () and Single Root I/O - Virtualization (). You can test whether - your CPU supports hardware virtualization with the following command: + 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 () and + Single Root I/O Virtualization (). You can + test whether your CPU supports hardware virtualization with the following + command: - -egrep '(vmx|svm)' /proc/cpuinfo - +&prompt.user;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: @@ -772,14 +283,12 @@ On the &arm64; architecture, virtualization support was initially added to - ARMv7-A processors starting with Cortex-A15 and including Cortex-A7 - and Cortex-A17. ARMv8-A processors include support for virtualization. + ARMv7-A processors starting with Cortex-A15 and including Cortex-A7 and + Cortex-A17. ARMv8-A processors include support for virtualization. - - &kvm; Kernel Modules Not Loading @@ -790,13 +299,14 @@ The general minimum hardware requirements for the - &vmhost; are the same as outlined in . The general - minimum hardware requirements for the &vmhost; are the same as for a - physical machine. 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. + &vmhost; are the same as outlined in + . + The general minimum hardware requirements for the &vmhost; are the same as + for a physical machine. 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. @@ -889,8 +399,8 @@ - Intel* VT-x2: FlexPriority, FlexMigrate (migration constraints - apply to dissimilar CPU architectures) + Intel* VT-x2: FlexPriority, FlexMigrate (migration constraints apply + to dissimilar CPU architectures) @@ -928,9 +438,9 @@ - - @@ -1091,20 +601,20 @@ 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 with Intel 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 start-up, 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-bit or - 64-bit, but the must be identical. + CPU ID masking is used, such as with Intel 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 start-up, 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-bit or 64-bit, but the + must be identical. Intel FlexMigration - For machines that support Intel FlexMigration, CPU-ID masking and - faulting allow more flexibility in cross-CPU migration. + For machines that support Intel FlexMigration, CPU-ID masking and faulting + allow more flexibility in cross-CPU migration. @@ -1314,387 +824,17 @@ Windows Guest Hotplugging of virtual network and virtual block devices, and resizing, - shrinking, and restoring dynamic virtual memory are supported in - &xen; and &kvm; only if PV drivers are being used (VMDP). + shrinking, and restoring dynamic virtual memory 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 kvm-supported.txt. - This file is part of the &kvm; package and can be found in + maintained in kvm-supported.txt. This file is part of + the &kvm; package and can be found in /usr/share/doc/packages/kvm. - -