Home XenServer 6.2: Installing update using the xe Command Line Interface
Post
Cancel

XenServer 6.2: Installing update using the xe Command Line Interface

Installing the update using the xe Command Line Interface

  1. Download the update file to a known location.
  2. Extract the xsupdate file from the zip.
    In this example I am patching the xenserver with the XS62E002 update
  3. Upload the xsupdate file to the Pool Master by entering the following commands:
    (Where hostname is the Pool Master’s IP address or DNS name.)</p> <pre class="theme:terminal nums:false nums-toggle:false lang:default decode:true">xe patch-upload -s <hostname> -u root -pw <password> file-name=<path_to_update_file>\XS62E002.xsupdate</pre>
1
2
3
XenServer assigns the update file a UUID which this command prints. Note the UUID.

> <tt>59128f15-92cd-4dd9-8fbe-a0115d1b07a2</tt>
  1. Apply the hotfix to all hosts in the pool, specifying the UUID of the hotfix: <pre class="theme:terminal nums:false nums-toggle:false lang:default decode:true ">xe -s <hostname> -u root -pw <password> patch-pool-apply uuid=59128f15-92cd-4dd9-8fbe-a0115d1b07a2</pre>
1
2
3
4
5
6
7
8
&nbsp;</li> 

  * Verify that the update was applied by using the **patch-list** command. <pre class="theme:terminal nums:false nums-toggle:false lang:default decode:true ">xe patch-list -s &lt;hostname&gt; -u root -pw &lt;password&gt; name-label=XS62E002</pre>
    
    If the update has been successful, the <tt>hosts</tt> field will contain the UUIDs of the hosts this patch was successfully applied to. This should be a complete list of all hosts in the pool.</li> 
    
      * To verify in XenCenter that the update has been applied correctly, select the Pool, and then click the **General** tab. This displays the Pool properties. In the **Updates** section, ensure that the update is listed as **Fully Applied**.
      * The hotfix is applied to all hosts in the pool, but it will not take effect until each host has been rebooted. For each host, migrate the VMs that you wish to keep running, and shutdown the remaining VMs before rebooting the host.</ol>
This post is licensed under CC BY 4.0 by the author.