Oracle VM Consulting
view counter

Oracle VM: How to update an Oracle VM Server

This section will review how to update an Oracle VM Server. We will begin with a brief overview of Oracle VM to help explain the options available to update an Oracle VM Server. Following the Oracle VM overview, we will walk through the process to register and update an Oracle VM Server from the Unbreakable Linux Network (ULN) using the up2date command.
 
Oracle VM Overview
Oracle VM is a freely downloadable Open Source Enterprise server virtualization solution. Oracle VM is an integral piece of Oracle Grid, which provides centralized management of Oracle and none Oracle workloads from pools of physical and virtual resources. Oracle VM follows the Open Source model of free to use and distribute with or without commercial support. Oracle offers commercial support for Oracle VM via the Oracle Unbreakable Linux support program. 
 
Oracle VM consists of two components, the Oracle VM Server and the Oracle VM Manager. Oracle VM Server is Oracle’s enhanced Xen hypervisor that is responsible for running the virtual machines. Oracle VM Manager is a middleware component that provides web based centralized life cycle management for an Oracle VM environment.
 
Figure 1.0 shows a single x86 Oracle VM server with four virtual machines, two RAC nodes, one Oracle VM Manager Template and one 11g Template.
 
The Oracle Unbreakable Linux support program allows customers to open Oracle VM and Linux Service Requests (SRs) 24/7 as well as access to the ULN network. Existing Oracle support customers use the same support infrastructure i.e. phone number and web portal to log and track Oracle VM Service Requests (SR) as with Tech and App SRs. ULN is an online resource for Oracle Unbreakable Linux subscribers that offers access to Linux and Oracle VM software patches, updates and fixes. ULN can be access from registered Linux and Oracle VM hosts with the up2date program as well as with a web browser by pointing the browser to http://linux.oracle.com
 
Note: ULN and My Oracle Support (formally Metalink) are two separate systems, accessed by different URLs and user name and passwords. ULN is used to access Oracle VM and Linux patches, updates and fixes and My Oracle Support is used to manage SRs. 
 
Figure 1.1 shows the ULN portal.

 
Oracle VM Update Options
There are two options to update an Oracle VM Server. The first option is to use the up2date command from the Oracle VM Server’s console. Using the up2date command requires ULN access. The second option is to upgrade the system to the latest version using bootable Oracle VM media. Oracle VM media is freely downloadable from Oracle’s eDelivery system at http://edelivery.oracle.com/linux.
 
Figure 1.2 shows the Oracle VM update options.
 
The difference between the two Oracle VM update methods is a) the ability to perform incremental updates or b) platform upgrades. Using the up2date command with ULN allows the Oracle VM server to receive incremental updates, patches, security fixes as well as new revisions. Using the bootable media requires the machine to be restarted and to select the update option from the boot prompt. Selecting the update option from the boot prompt will update the Oracle VM Server to the version of the bootable media, e.g. from 2.1.1 to 2.1.2.
 
Figure 1.3 shows the System to Upgrade boot prompt. From the System to Upgrade boot prompt administrators can select to reinstall the system or to upgrade.
 
When the up2date command is executed from the Oracle VM Server’s console, up2date connects to the ULN repository and downloads the requested packages in RPM format. Up2date then installs the packages on the registered Oracle VM server. Please consult up2date’s man page by executing “man up2date” from the Oracle VM Server’s console as root for a comprehensive list of command augments.
 
Oracle VM Server Registration & Update Example
This section will walk through the process or registering and updating an Oracle VM Server. The examples will all be performed from the Oracle VM Server’s console using the up2date command as the root user.
 
Before we update the Oracle VM Server, lets review how to determine the Oracle VM Server release number and Xen version. Determining the Oracle VM Server release number and Xen version will help track the life cycle of the update process.
 
Oracle VM Release Number
To determine the Oracle VM Server release number, we will read the /etc/ovs-release file using the cat command from the Oracle VM Server console as show in the next example. 
# cat /etc/ovs-release
Oracle VM server release 2.1.1
#
 
Reading the /etc/ovs-release file shows that the Oracle VM Server is release 2.1.1.
 
Note: Please note if the system is updated to a new release number the Oracle VM Server may need to be restarted to reflect the updated Oracle VM Server release number. 
 
Xen Version
Next we will review two methods to determine the Xen version of the Oracle VM Server. First we will use the xm dmesg command from the Oracle VM Server console followed by the xm info command.
 
Note: Please note if Xen was updated the Oracle VM Server may need to be restarted to reflect the updated Xen version. 
# xm dmesg
 __ __            _____ _   _____
 \ \/ /___ _ __   |___ / / | |___ /
 \ // _ \ '_ \    |_ \ | |   |_ \
 / \ __/ | | | ___) || |_ ___) |
 /_/\_\___|_| |_| |____(_)_(_)____/
 
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory
 
 Xen version 3.1.3 (mockbuild@us.oracle.com) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) Wed Mar 5 14:28:01 EST 2008
 
As show in the above example, we can quickly determine the Xen version (3.1.3) by the xm dmesg banner as well as reading the first string of text “Xen version 3.1.3” under the University of Cambridge Computer Laboratory acknowledgement.
 
Next we will run the xm info command from the Oracle VM Server console to determine the Xen version.
# xm info
host                   : ovm02.sf.seo.com
release                : 2.6.18-8.1.15.0.16.el5xen
version                : #1 SMP Wed Mar 5 13:03:41 EST 2008
machine                : i686
nr_cpus                : 8
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2660
hw_caps                : bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001
total_memory           : 16383
free_memory            : 15311
xen_major              : 3
xen_minor              : 1
xen_extra              : .3
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xfec00000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
cc_compile_by          : mockbuild
cc_compile_domain      : us.oracle.com
cc_compile_date        : Wed Mar 5 14:28:01 EST 2008
xend_config_format     : 4
#
 
We can determine the Xen version by looking at the xen major, minor and extra strings. As show in the above example, xen major 3, xen minor 1 and xen extra 3 show the Xen version 3.1.3.
 
Oracle VM Server Update
This section will start with an overview of the registration process, followed with the procedure to register and update an Oracle VM server using up2date and ULN.
 
The registration process will require you to enter a user name, password and a valid Oracle VM Support Identifier (CSI) number. The user name and password that is used during the registration process will be become the default ULN user name and password. Both the user name and password can be changed after the registration process via the ULN portal. 
 
Note: ULN and My Oracle Support (formerly Metalink) are separate systems with separate user name and password.
 
The first step is to import Oracle’s GPG key using the rpm command. From the Oracle VM Server console run the following command.
#rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY
Once the Oracle’s GPG key has been imported, we can register the Oracle VM Server with ULN. From the Oracle VM Server console run the up2date command as show in the next example.
#up2date
 
Once the up2date command is executed you will invoke the ULN registration process. The ULN registration process is comprised of six different steps.
 
List 1.1 shows the six steps:
  1. Review the Unbreakable Linux Privacy Statement
  2. Register a User Account
  3. Register a system Profile - Hardware
  4. Register a system Profile – Packages
  5. Send Profile Information to the Unbreakable Linux Network
  6. Finished Registration
 
Before you can register the Oracle VM Server, you will need to select a user name, password and have a valid Oracle VM CSI number. The user name and password that is used during the registration process will be the ULN user name and password. Both the user name and password can be changed after the registration process via the ULN portal.
 
Step 1 Review the Unbreakable Linux Privacy Statement
From the Review the Unbreakable Linux Privacy Statement section use the Alt key to highlight the Next tab, once the Next tab is highlighted hit the enter key to proceed.  
 
Figure 1.4 shows the Review the Unbreakable Linux Privacy Statement section.

 
Step 2 Register a User Account
From the Register a User Account section enter a User name, password, password confirmation and a valid Oracle VM CSI number. Use the Alt key to highlight the Next tab, and then hit the Enter key to proceed.
 
Figure 1.5 shows the Register a User Account section.

 
Step 3 Register a system Profile – Hardware
From the Register a system Profile – Hardware section accept the defaults and use the Alt key to highlight the Next tab. Once the Next tab is highlighted hit the Enter key to proceed.
 
Note: The information gathered from the system profile steps are saved on the ULN network. 
 
Figure 1.6 shows the Register a system Profile – Hardware section.

 
Step 4 Register a system Profile – Packages
From the Register a system Profile – Packages section accept the defaults and use the Alt key to highlight the Next tab. Once the Next tab is highlighted hit the Enter key to proceed.
 
Note: The information gathered from the system profile steps are saved on the ULN network.
 
Figure 1.7 shows the Register a system Profile – Packages section.

 
Step 5 Send Profile Information to the Unbreakable Linux Network
From the Send Profile Information to the Unbreakable Linux Network section accept the defaults and use the Alt key to highlight the Next tab. Once the Next tab is highlighted hit the Enter key to proceed.
 
Figure 1.8 shows the Send Profile Information to the Unbreakable Linux Network section.

 
Step 6 Finished Registration
From the Finished Registration section accept the defaults and use the Alt key to highlight the Next tab. Once the Next tab is highlighted hit the Enter key to proceed.
 
Figure 1.9 shows the Finished Registration section.

 
You have sucessfully registered your Oracle VM Server. Now logon to ULN using the user name and password from step 2 the Register a User Account section. Once logged into ULN validate that the Oracle VM Server is displayed in the Recently Registered Systems table as show in Figure 1.10.
 

Next click on the Oracle VM Server to view the default channel selection (Oracle VM Latest) as shown in Figure 1.11.
 
 
After successfully registering the system with ULN lets return to the Oracle VM Server console to perform an update. From the Oracle VM console as root, type “up2date –u” to update the system as show in the following example.  
# up2date -u
 
Fetching Obsoletes list for channel: ovm2_i386_latest...
########################################
 
Fetching rpm headers...
########################################
 
Name                                    Version        Rel
----------------------------------------------------------
anaconda                                11.1.2.36      1.1.65            i386
anaconda-runtime                        11.1.2.36      1.1.65            i386
compat-python-virtinst                  0.99.0         3.el5.2.9         noarch
device-mapper                           1.02.24        1.el5             i386
e2fsprogs                               1.39           10.el5_1.1        i386
e2fsprogs-libs                          1.39           10.el5_1.1        i386
enterprise-linux-ovs                    5              0.13              i386
hwdata                                  0.211          1.1.2             noarch
initscripts                             8.45.16.EL     1.1.10            i386
iscsi-initiator-utils                   6.2.0.868      0.7.el5           i386
kpartx                                  0.4.7          17.el5            i386
libvirt                                 0.2.3          9.0.1.el5.0.1     i386
libvirt-python                          0.2.3          9.0.1.el5.0.1     i386
libvncserver                            0.9.1          3                 i386
ovs-agent                               2.2            51                noarch
ovs-release                             2.1            0.13              i386
ovs-utils                               1.0            26                i386
xen                                     3.1.4          0.1.16.el5       i386
xen-64                                  3.1.4          0.1.16.el5        noarch
xen-devel                               3.1.4          0.1.16.el5        i386
xen-tools                               3.1.4          0.1.16.el5        i386
 
 
Testing package set / solving RPM inter-dependencies...
########################################
anaconda-11.1.2.36-1.1.65.i ########################## Done.
anaconda-runtime-11.1.2.36- ########################## Done.
compat-libvirt-python-0.1.8 ########################## Done.
compat-python-virtinst-0.99 ########################## Done.
device-mapper-1.02.24-1.el5 ########################## Done.
dnsmasq-2.39-2.el5.i386.rpm ########################## Done.
e2fsprogs-1.39-10.el5_1.1.i ########################## Done.
e2fsprogs-libs-1.39-10.el5_ ########################## Done.
enterprise-linux-ovs-5-0.13 ########################## Done.
hwdata-0.211-1.1.2.noarch.r ########################## Done.
initscripts-8.45.16.EL-1.1. ########################## Done.
iscsi-initiator-utils-6.2.0 ########################## Done.
kpartx-0.4.7-17.el5.i386.rp ########################## Done.
libvirt-0.2.3-9.0.1.el5.0.1 ########################## Done.
libvirt-python-0.2.3-9.0.1. ########################## Done.
libvncserver-0.9.1-3.i386.r ########################## Done.
ovs-agent-2.2-51.noarch.rpm ########################## Done.
ovs-release-2.1-0.13.i386.r ########################## Done.
ovs-utils-1.0-26.i386.rpm: ########################## Done.
p2v-util-0.10-1.i386.rpm:   ########################## Done.
xen-3.1.4-0.1.16.el5.i386.r ########################## Done.
xen-64-3.1.4-0.1.16.el5.noa ########################## Done.
xen-devel-3.1.4-0.1.16.el5. ########################## Done.
xen-tools-3.1.4-0.1.16.el5. ########################## Done.
compat-libvirt-0.1.8-15.el5 ########################## Done.
Preparing              ########################################### [100%]
 
Installing...
   1:device-mapper          ########################################### [100%]
   2:e2fsprogs-libs         ########################################### [100%]
   3:libvncserver           ########################################### [100%]
   4:ovs-utils              ########################################### [100%]
   5:e2fsprogs              ########################################### [100%]
   6:kpartx                 ########################################### [100%]
   7:enterprise-linux-ovs   ########################################### [100%]
   8:initscripts            ########################################### [100%]
   9:dnsmasq                ########################################### [100%]
 10:p2v-util               ########################################### [100%]
 11:anaconda               ########################################### [100%]
 12:anaconda-runtime       ########################################### [100%]
 13:ovs-release            warning: /etc/issue created as /etc/issue.rpmnew
########################################### [100%]
 14:iscsi-initiator-utils ########################################### [100%]
 15:hwdata                 ########################################### [100%]
 16:xen-devel              ########################################### [100%]
 17:compat-libvirt         ########################################### [100%]
 18:xen-tools              ########################################### [100%]
 19:compat-libvirt-python ########################################### [100%]
 20:compat-python-virtinst ########################################### [100%]
 21:xen                    ########################################### [100%]
 22:libvirt                ########################################### [100%]
 23:libvirt-python         ########################################### [100%]
 24:ovs-agent              ########################################### [100%]
 25:xen-64                 ########################################### [100%]
The following Packages were marked to be skipped by your configuration:
 
Name                                    Version        Rel Reason
-------------------------------------------------------------------------------
kernel-BOOT                             2.6.18         8.1.15.1.20.el5Pkg name/pattern
kernel-ovs                              2.6.18         8.1.15.1.20.el5Pkg name/pattern
system-config-securitylevel-tui         1.6.29.1       1.el5.1.12Config modified
system-config-securitylevel             1.6.29.1       1.el5.1.12Config modified
 
The following packages were added to your selection to satisfy dependencies:
 
Name                                    Version        Release
--------------------------------------------------------------
compat-libvirt-python                   0.1.8          15.el5.1.1.3
dnsmasq                                 2.39           2.el5
p2v-util                                0.10           1
compat-libvirt                          0.1.8          15.el5.1.1.3
 
#
 
You have just successfully updated as well as upgraded the Oracle VM Server. If we examine the updated package list from our example you can see that Xen (xen) as well as the Oracle VM release (ovs-release) was updated. The Oracle VM Server would need to be restarted to reflect the new version and revision numbers. For example if you were to run xm dmesg or xm info from the Oracle VM Server’s console, the Xen version and Oracle VM release numbers would not have changed.
 
The default update configuration for Oracle VM Server is not to update the kernel. If we review the output from the up2date command in our example, note the “The following Packages were marked to be skipped by your configuration:” section. This is where the list of skipped packages is displayed. The skipped packages list can be configured by running the “up2date-config –nox” command from the Oracle VM Server console as root.
 
The primary advantage of the default skip list is to avoid a 'blind' upgrade, which could affect any software, utilities, third-party drivers that are dependent on a specific kernel version. If the skip list is modified to allow kernel updated, a kernel update will retain the previous kernel so the system can be rebooted into the previous kernel in the event that things go wrong. 
 
To edit the skip list from the Oracle VM Server console as root enter up2date-config –nox and edit line 19 and 20 as shown in the following example.
[root@ovm02 ~]# up2date-config --nox
0. adminAddress       ['root@localhost']
1. debug              No
2. disallowConfChange ['noReboot', 'sslCACert', 'useNoSSLForPackages', 'noSSLSe
3. enableProxy        No
4. enableProxyAuth    No
5. enableRollbacks    No
6. fileSkipList       []
7. forceInstall       No
8. gpgKeyRing         /etc/sysconfig/rhn/up2date-keyring.gpg
9. headerCacheSize    40
10. headerFetchCount   10
11. httpProxy
12. isatty             Yes
13. keepAfterInstall   No
14. networkRetries     5
15. noBootLoader       No
16. noReboot           No
17. noReplaceConfig    Yes
18. noSSLServerURL     http://linux-update.oracle.com/XMLRPC
19. pkgSkipList        ['kernel*']
20. pkgsToInstallNotUp ['kernel', 'kernel-modules', 'kernel-devel']
21. proxyPassword
22. proxyUser
23. removeSkipList     ['kernel*']
24. retrieveOnly       No
25. retrieveSource     No
26. rhnuuid            3cfb2ee2-6a22-11dd-9022-001c23b73c3a
27. serverURL          https://linux-update.oracle.com/XMLRPC
28. showAvailablePacka No
29. sslCACert          /usr/share/rhn/ULN-CA-CERT
30. storageDir         /var/spool/up2date
31. systemIdPath       /etc/sysconfig/rhn/systemid
32. updateUp2date      Yes
33. useGPG             Yes
34. useNoSSLForPackage No
35. useRhn             Yes
36. versionOverride
 
 
Enter number of item to edit <return to exit, q to quit without saving>: 19
 
Attribute: pkgSkipList
Comment: A list of package names, optionally including wildcards, to skip
Current value: kernel*;
   < return for default, C to clear list, items are ';' separated >
New Value: C
 
0. adminAddress       ['root@localhost']
1. debug              No
2. disallowConfChange ['noReboot', 'sslCACert', 'useNoSSLForPackages', 'noSSLSe
3. enableProxy        No
4. enableProxyAuth    No
5. enableRollbacks    No
6. fileSkipList       []
7. forceInstall       No
8. gpgKeyRing         /etc/sysconfig/rhn/up2date-keyring.gpg
9. headerCacheSize    40
10. headerFetchCount   10
11. httpProxy
12. isatty             Yes
13. keepAfterInstall   No
14. networkRetries     5
15. noBootLoader       No
16. noReboot           No
17. noReplaceConfig    Yes
18. noSSLServerURL     http://linux-update.oracle.com/XMLRPC
19. pkgSkipList        []
20. pkgsToInstallNotUp ['kernel', 'kernel-modules', 'kernel-devel']
21. proxyPassword
22. proxyUser
23. removeSkipList     ['kernel*']
24. retrieveOnly       No
25. retrieveSource     No
26. rhnuuid            3cfb2ee2-6a22-11dd-9022-001c23b73c3a
27. serverURL          https://linux-update.oracle.com/XMLRPC
28. showAvailablePacka No
29. sslCACert          /usr/share/rhn/ULN-CA-CERT
30. storageDir         /var/spool/up2date
31. systemIdPath       /etc/sysconfig/rhn/systemid
32. updateUp2date      Yes
33. useGPG             Yes
34. useNoSSLForPackage No
35. useRhn             Yes
36. versionOverride
 
 
Enter number of item to edit <return to exit, q to quit without saving>: 20
 
Attribute: pkgsToInstallNotUpdate
Comment: A list of provides names or package names of packages to install not update
Current value: kernel;kernel-modules;kernel-devel;
   < return for default, C to clear list, items are ';' separated >
New Value: C
 
0. adminAddress       ['root@localhost']
1. debug              No
2. disallowConfChange ['noReboot', 'sslCACert', 'useNoSSLForPackages', 'noSSLSe
3. enableProxy        No
4. enableProxyAuth    No
5. enableRollbacks    No
6. fileSkipList       []
7. forceInstall       No
8. gpgKeyRing         /etc/sysconfig/rhn/up2date-keyring.gpg
9. headerCacheSize    40
10. headerFetchCount   10
11. httpProxy
12. isatty             Yes
13. keepAfterInstall   No
14. networkRetries     5
15. noBootLoader       No
16. noReboot           No
17. noReplaceConfig    Yes
18. noSSLServerURL     http://linux-update.oracle.com/XMLRPC
19. pkgSkipList        []
20. pkgsToInstallNotUp []
21. proxyPassword
22. proxyUser
23. removeSkipList     ['kernel*']
24. retrieveOnly       No
25. retrieveSource     No
26. rhnuuid            3cfb2ee2-6a22-11dd-9022-001c23b73c3a
27. serverURL          https://linux-update.oracle.com/XMLRPC
28. showAvailablePacka No
29. sslCACert          /usr/share/rhn/ULN-CA-CERT
30. storageDir         /var/spool/up2date
31. systemIdPath       /etc/sysconfig/rhn/systemid
32. updateUp2date      Yes
33. useGPG             Yes
34. useNoSSLForPackage No
35. useRhn             Yes
36. versionOverride
 
 
Enter number of item to edit <return to exit, q to quit without saving>:
 
Lets reboot the server to validate the Xen and Oracle VM revision changes. Before we reboot the Oracle VM Server lets ensure that there are no running guests on the Oracle VM Server. 
 
From the Oracle VM Server console as root type xm list as show in the following example.
# xm list
Name                                        ID   Mem VCPUs      State  Time(s)
Domain-0                                     0   835     8     r----- 100143.0
 
The xm list example shows that there are no running guest domains.
 
Note: Domain-0 is the privileged domain not a guest domain. A guest domain (also called virtual machines) in Xen terminology is called an unprivileged domain. The server can be restarted with Domain-0 running.
 
From the Oracle VM Server console as root, type reboot as show in the following example.
# reboot
 
Broadcast message from root (pts/0) (Sun Sep 28 18:22:53 2008):
 
The system is going down for reboot NOW!
 
Oracle VM Release Number
To validate the Oracle VM Server release number, we will read the /etc/ovs-release file using the cat command from the Oracle VM Server console as show in the next example.
 
Reading the /etc/ovs-release file shows that the Oracle VM Server was updated from 2.1.1 to release number 2.1.2.
 
Xen Version
Next we will use the xm dmesg command from the Oracle VM Server console followed by the xm info command to validate the Xen version.
# xm dmesg
 __ __            _____ _ _ _
 \ \/ /___ _ __   |___ / / || || |
 \ // _ \ \047_ \    |_ \ | || || |_
 / \ __/ | | | ___) || ||__   _|
 /_/\_\___|_| |_| |____(_)_(_) |_|
 
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory
 
 Xen version 3.1.4 (root@localdomain) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) Thu Aug 28 00:06:27 PDT 2008
 
As show in the above example, we can quickly determine from xm dmesg that the Xen version changed from 3.1.3 to 3.1.4 by the xm dmesg banner as well as reading the first string of text “Xen version 3.1.4” under the University of Cambridge Computer Laboratory acknowledgement.
 
Next we will run the xm info command from the Oracle VM Server console to validate the Xen version.
# xm info
host                   : ovm02.sf.seo.com
release                : 2.6.18-8.1.15.0.16.el5xen
version                : #1 SMP Wed Mar 5 13:03:41 EST 2008
machine                : i686
nr_cpus                : 8
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2660
hw_caps                : bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001
total_memory           : 16383
free_memory            : 15311
xen_major              : 3
xen_minor              : 1
xen_extra              : .4
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xfec00000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)
cc_compile_by          : root
cc_compile_domain      : localdomain
cc_compile_date        : Thu Aug 28 00:06:27 PDT 2008
xend_config_format     : 4
#
 
We can determine that the Xen version was updated by looking at the xen major, minor and extra strings. As show in the above example, xen major 3, xen minor 1 and xen extra 4 show the Xen version 3.1.4.
view counter