Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Guidance for in-place upgrade of SLES 11 to SLES 12 (52222)

Last Updated: 1/18/2018Categories: InformationalTotal Views: 9668Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

In-place upgrade of the guest operating system (between major OS release versions, such as SLES 11 to SLES 12) is not recommended. The best practice is to install a new major OS releases in a new VM.

Support considerations:

Read OS vendor's documentation and release notes to ensure the specific upgrade scenario is supported. If the OS vendor does not support a particular upgrade scenario, then VMware will not be able to provide support for such scenarios due to lack of ability to collaborate with the OS vendor.

In-place upgrade is a feature of the operating system, if problems are encountered, it is best to first contact the OS vendor for assistance. If the OS vendor has narrowed down problem to be specific to VMware software, then VMware can provide assistance.

Support for VMware software distributed by OS vendors (such as open-vm-tools, agents, and drivers) is provided in coordination with the OS vendors. If any fixes or patches are required to VMware software distributed by OS vendors, then these fixes or patches are typically distributed through the OS vendor utilizing their patching mechanism.

Some VMware products do not support in-place upgrade of the guest operating system in a VM. For more details, see VMware support for guest operating system upgrade (2018695).

Check VMware Compatibility Guide to ensure new operating system version is supported as guest on the VMware product.

Check the configuration of VM to ensure that it meets requirements to run new OS release. New major OS releases sometime increase the minimum require amount of memory, video ram, disk space, etc. In addition, performing OS upgrade consumes disk space, so ensure VM has adequate storage to complete the upgrade. It may be necessary to power off the VM to make some of these adjustments before starting the upgrade.

For all applications running in the OS, contact the application vendor to determine their support policies and guidance for conducting operating system upgrades.

Special considerations for SLES 12 upgrade:

Read SLES 12 release notes, located here: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#InstUpgrade.Upgrade

SUSE's supported upgrade scenarios change over time as new SP releases become available. Typically, SUSE requires update to latest SLES 11 SP version before upgrade to SLES 12. Check latest documentation that scenario is supported.

A VM running 32-bit version of SLES cannot be upgraded to SLES 12 because SLES 12 is only available as 64-bit.

VMware virtual machines can be provisioned to select different operating systems to optimize virtualization. There is a unique selection for SLES 11 and SLES 12. For best performance, this section should be changed to SUSE Linux Enterprise 12 (64-bit) after operating system upgrade. This change can only be made when the VM is powered off.

SLES 12 includes open-vm-tools, which is recommended for use with SLES 12. For more details, see VMware support for Open VM Tools (2073803).

SUSE began providing open-vm-tools as an optional package for SLES 11 SP4, but not earlier releases. If VM with SLES 11 SP4 is using open-vm-tools provided by SUSE, do not uninstall open-vm-tools before upgrade. During upgrade to SLES 12, the open-vm-tools package will be upgraded (for example from 9.4.6 to 10.0.7 or a later version).

Legacy VMware Tools (distributed in TAR format on an iso) are not recommended for use with SLES 12. Legacy VMware Tools should be uninstalled prior to upgrading operating system.

VM Tools in OSP Format (distributed on-line from https://www.vmware.com/support/packages.html) are not available for SLES 12. OSP Format tools should be uninstalled prior to upgrading operating system.

If starting point is SLES 11 SP4, install open-vm-tools provide for SLES 11 SP4, which will be updated during operating system upgrade. If starting point is older SP release, then open-vm-tools should be done during or after the operating system upgrade upgrade.

If optional open-vm-tools-deploypkg package downloaded from vmware.com has been install on open-vm-tools distributed by SUSE, then the optional open-vm-tools-deploypkg package should be uninstalled prior to upgrade. The newer version of open-vm-tools provided by SUSE for SLES 12 will include open-vm-tools-deploypkg.

SLE 12 does not support gtkmm2, however, open-vm-tool versions prior to 10.0.7 have a dependency on gtkmm2 for some functionality. Therefore, use of open-vm-tool version 10.0.7 or later is recommended.

If no X installed on a server, then open-vm-tools-desktop does not need to be installed.

Video and mouse Xorg drivers installed by VM Tools for SLES 11 are incompatible with the xorg-server included in SLES 12. Leaving these drivers installed during upgrade to SLES 12 may interfere with operation of compatible xorg drivers included in SLES 12 and result in poor video and mouse performance. Uninstallation of VMware Tools prior to upgrade will prevent this issue. For more details, see VMware mouse and video drivers not working after upgrading to SLE12 (2120590).

SLES 12 introduces in-kernel paravirtual vmware graphics driver (vmwgfx).

SLES 12 introduces in-kernel vmci driver and vsock kernel module. For SLES 11, these were distributed and install by VMware Tools. The uninstallation of VMware Tools before upgrade will remove this driver and kernel module. After upgrade, the SLE 12 in-kernel vmci driver and vsock kernel module should be utilized.

SLES 11 includes several in-kernel paravirtual vmware drivers (pvscsi, vmxnet3 and vmw_balloon). After operating system upgrade, SLES 12 will include newer versions of these drivers with enhancements and bug fixes.

VMware recommends use of the vmxnet3 paravirtual NIC on both SLES 11 and SLES 12. The vmxnet3 NIC is the only NIC option that is supported on both SLES 11 and SLES 12, so this is best option to use during upgrade process.

The e1000e NIC is a new supported option for use in a VM running SLES 12. On vSphere, the e1000e NIC can only be selected after changing OS selection to "SUSE Linux Enterprise 12 (64-bit)".

The e1000 and vmxnet2 NICs are not supported by VMware on SLES 12. If the SLES 11 VM is using a e1000 or vmxnet2 NIC, change these NICs to vmxnet3. After changing OS selection to "SUSE Linux Enterprise 12 (64-bit)", the e1000 or vmxnet2 NIC are not longer available in vSphere for selection. Using e1000 or vmxnet2 NICs in a VM configured for "SUSE Linux Enterprise 12 (64-bit)" will generate errors on vSphere.

Purpose

This article provides guidance on how to perform in-place upgrade of SLES 11 to SLES 12 in a VM.

Resolution

Recommended procedure:

Create a test VM to practice the upgrade process and gain confidence that the procedure will be successful. The test VM could be a clone of a VM that is planned for upgrade, however, this is not recommended if the VM is interacting with external systems, such as a database. The best practice is to create the test VM by installing old OS release and applications in a newly created VM.

Save a snapshot or backup of VM before making any changes. If upgrade fails, you can revert VM to saved snapshot and try again.

Check configuration of VM to ensure that it meets requirements to run new OS release and adjust if necessary. Ensure that:

VM has adequate storage space to perform the upgrade.

VM is not using e1000 or vmxnet2 NICs.

If VM includes open-vm-tools distributed by SUSE, then do not uninstall open-vm-tools. The update to SLES 12 will update open-vm-tool.

If VM includes open-vm-tools distributed by SUSE and optional open-vm-tools-deploypkg package downloaded from vmware.com, uninstall only the open-vm-tools-deploypkg package.

If VM include legacy VMware Tools, uninstall VMware Tools:

To uninstall legacy VMware Tools, run the uninstall script: /usr/bin/vmware-uninstall-tools.pl

To uninstall OSP Format Tools, run the command: zypper remove 'vmware-tools-*'

Perform upgrade.

While VM is powered-off, change virtual machine's OS selection to SUSE Linux Enterprise 12 (64-bit) (sles12-64)

Check the following items:

Ensure vmci driver is loaded.
# modinfo vmw_vmci

Ensure vsock driver is loaded.
# modinfo vsock

Ensure open-vm-tools packages are installed. Install the packages if not installed.
# zypper info libvmtools0 open-vm-tools open-vm-tools-desktop   ## should be Installed:Yes

Ensure vmtoolsd system service is running
# ps aux | grep vmtoolsd | grep -v vmusr
# systemctl status vmtoolsd

Ensure VGAuth service is running
# systemctl status vgauthd

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant