NOTICE: Rackspace Engineers will be performing a scheduled maintenance on the infrastructure for support.rackspace.com and developer.rackspace.com on October 23, 2018 and October 24, 2018. During this maintenance, both sites will be down for a few hours between 10:00 PM CDT and 8:00 AM CDT, and customers will not be able to access the How-To or the API documentation. If you have any questions or concerns in regard to this maintenance, please do not hesitate to contact a member of our support team.

Converting your server from PV to PVHVM

  • Last updated on: 2018-03-05
  • Authored by: Brian King

XenServer, which is the virtualization platform used by the Rackspace public cloud, supports multiple virtualization modes. For better performance and security, convert your Rackspace cloud server from the older paravirtualization (PV) mode to the newer paravirtualization with full hardware virtualization (PVHVM) mode. Newer distributions, such as CentOS 7 and Ubuntu 16, are offered as only PVHVM, so conversion is unnecessary.

In general, PVHVM offers better performance than PV, especially for disk and network I/O operations.

The following operating systems can be converted from PV to PVHVM:

  • Ubuntu 12/14
  • RHEL/CentOS 6
  • Debian 7

If your server cannot be converted, we recommend that you deploy a new server from an existing base image and migrate your data to the new server.

To learn more about the conversion process, see this Rackspace Community article.

Some advantages and disadavantages of PVHVM are described in the following sections.

Performance

PVHVM performance considerations include the following:

  • Network and disk I/O are faster with PVHVM images because Quick Emulator (QEMU) emulation is bypassed.
  • PVHVM requires a bit more memory overhead than PV.
  • Work-optimized Rackspace servers, such as Compute, I/O, and Memory, require PVHVM images.

If you try to create a work-optimized server by using a non-PVHVM image, the following error message is displayed:

Image cannot be built with provided flavor.

File system

File system considerations include the following:

  • The lower-performance ext3 filesystem is used for all PV Linux images.
  • The higher-performance ext4 filesystem is used on PVHVM Linux images.

Boot loader

Boot loader considerations include the following:

  • PV images boot by using pygrub.
  • PVHVM images boot by using the boot loader in the master boot record of the operating system.

Disk configuration

Automatic disk configuration can be used with PV images but not with PVHVM images.

If you try to use automatic disk configurtion with a PVHVM image, the following error message is displayed:

ERROR: Requested image $UUID has automatic disk resize disabled. (HTTP 400)

Continue the conversation in the Rackspace Community.