home

Supported platforms

Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers
Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Show On this page:

thumbnailSupported platforms

Upgrading Guests

Overview

You can use the upgrade virtualization guest and upgrade virtualization xml commands to upgrade a guest.

The guest, which is created automatically, is specified by three files that can be modified by the upgrade virtualization xml command:
  • The libvirt domain XML file defines the guest parameters, such as the number of CPUs, amount of RAM, and the details for the bridge and vhost interfaces.
  • The guest image must be in the QCOW2 format and specifies the guest operating system.
  • The ISO configuration file specifies the guest configuration.
The upgrade commands are described in the following paragraphs:
upgrade virtualization guest

The upgrade virtualization guest command replaces the disk image of a virtual disk for a guest with a different image. The command also powers the guest off and on. The image may be local or remote. You can upgrade multiple disks for a guest in one command. Any existing images that conflict with the new images are overwritten during an upgrade. The configuration is saved after an upgrade. Any images which were previously used by the disks being upgraded are deleted after an upgrade, if they are not overwritten during the upgrade. The keep-old-images option prevents the deletion of old images.

upgrade virtualization xml

After you provision a guest automatically, you can use the upgrade virtualization xml command to upgrade a guest.

The upgrade virtualization xml command uses a libvirt domain XML file and, optionally, a new disk image, configuration ISO file, or both.

The command reconfigures an existing guest according to the parameters defined within the specified XML file. The XML file used must contain the same guest name as the guest being upgraded. If a disk image is not specified in the command, then the current guest image is retained for the new configuration. If an ISO file is not specified in the command, the current ISO image of the guest is retained for the new configuration. The files may be local or remote. The existing images are overwritten if there is a conflict with the location where the new images are moved during the upgrade. If the existing guest configuration has more than one disk or one cdrom drive then the extra disks are lost during the upgrade. The keep-old-images option prevents the deletion of old images.

Note: During a deployment or upgrade, the disk images are moved from their current, specified location, and not copied, if they are local.
Note: Location of the remotely located files can be influenced by the keyword routing-instance.

For a configuration example about upgrading a guest XML file, refer to Upgrading a guest by using a libvirt domain XML file.

For a configuration example about upgrading multiple guest image files, refer to Upgrading multiple guest images for a guest.

For a configuration example about using the keep-old-images option, refer to Upgrading a guest and keeping the old files.

Last updated: May 7, 2021