OVM 3.1.1 upgrade to OVM 3.2.2 summary

Storage uses local repository and OVM Manager 3.1.1 "ovm311-m" runs on OVM 3.1.1 host "ovm311",
Configuration summary of OVM 3.1.1 host,
[root@ovm311 ~]# dmidecode --type 1
# dmidecode 2.10
SMBIOS 2.6 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Oracle Corporation
Product Name: SUN FIRE X4170 M2 SERVER
Version:
Serial Number: XXXXXXXXXX
UUID: FF200008-FFFF-FFFF-FFFF-002128F90DA0
Wake-up Type: Power Switch
SKU Number: 30543821+1+1
Family:
[root@ovm311 ~]# xm info | grep total_memory
total_memory : 147447
[root@ovm311 ~]# cat /etc/ovs-release
Oracle VM server release 3.1.1
[root@ovm311 ~]# df -T -k
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sda1 ext3 69163868 52869052 12724776 81% /
tmpfs tmpfs 974600 0 974600 0% /dev/shm
none tmpfs 974600 792 973808 1% /var/lib/xenstored
/dev/mapper/3600605b0043831601771adda5ecc0980
ocfs2 3434262528 892317696 2541944832 26% /OVS/Repositories/0004fb00000300001e2b4833cceadfb1
[root@ovm311 ~]# xm list
Name ID Mem VCPUs State Time(s)
0004fb00000600000f000553a436e435 12 1024 1 -b---- 4632.7
0004fb000006000024fcdbdd5a671e41 18 4096 2 -b---- 35931.5
0004fb00000600004de585ff2caf9aad 16 2048 1 -b---- 98482.9
0004fb000006000064b3e879d5c3a419 10 1024 1 -b---- 6063.1
0004fb0000060000779dd9141d3208bf 7 4096 2 -b---- 3009.1
0004fb00000600007e0582a43ebb876a 14 2048 2 -b---- 6750.0
0004fb000006000084edfea7ba79187f 15 2048 1 -b---- 2261.0
0004fb0000060000aa89b5bbbe8566c4 17 4096 2 -b---- 37069.5
0004fb0000060000ac0e7f2aafb524cc 5 4096 2 -b---- 2588.8
0004fb0000060000b125f3818169434d 27 2304 1 -b---- 8876.5
0004fb0000060000b20f4a1aa38509f9 28 2304 1 -b---- 11866.5
0004fb0000060000b4333b8bd864fb2f 20 16384 10 -b---- 68.0
0004fb0000060000b58ffc8db4ce7d00 11 1024 1 -b---- 14526.2
0004fb0000060000c476ce3212a40398 4 2304 1 -b---- 29018.4
0004fb0000060000cf30d5d39f1b7d35 9 1024 1 -b---- 6392.9
0004fb0000060000e3a8ee9af9e4f811 26 4096 2 -b---- 2763.4
0004fb0000060000e4e04fdfd6baeda6 24 2048 1 -b---- 3174.8
0004fb0000060000ed3d35a0cdefe136 21 2048 1 -b---- 2043.1
Domain-0 0 2039 24 r----- 290960.0
ovm311-m 1 4096 1 r----- 63205.4
[root@ovm311 ~]# tail -2 /etc/ovs-agent/agent.ini
[server]
fakeuuid=ff:20:00:08:ff:ff:ff:ff:ff:ff:a0:0d:f9:28:21:00
Configuration uses "fakeuuid" to workaround prior issues when SMBIOS was updated on x4170 M2. Reference separate posts in that regard
and Bjorn Naessens "Tips and Tricks Fakeuuid it", http://bjornnaessens.wordpress.com/2012/08/10/best-practices-in-ovm-2-fakeuuid-it/
Task summary:
1) Shutdown VM's managed by OVM Manager 3.1.1
2) Shutdown and disable "ovmm" on "ovm311-m"
3) Shutdown "ovm311-m"
4) Reboot "ovm311"
5) Boot off OVM 3.2.2 ISO
6) Install/Upgrade
Post upgrade configuration summary,
[root@ovm311 ~]# cat /etc/ovs-release
Oracle VM server release 3.2.2
[root@ovm311 ~]# cat upgrade.log
Upgrading xen-tools-4.1.3-25.el5.3.x86_64
warning: xen-tools-4.1.3-25.el5.3: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Upgrading util-linux-2.13-0.52.100.1.el5_4.2.x86_64
Upgrading ovs-agent-3.2.1-183.2.x86_64
warning: /etc/ovs-agent/agent.ini created as /etc/ovs-agent/agent.ini.rpmnew
warning: /etc/ovs-agent/passwdfile created as /etc/ovs-agent/passwdfile.rpmnew
Upgrading kpartx-0.4.9-46.100.5.el5.x86_64
Upgrading 4:perl-5.8.8-38.el5.x86_64
Upgrading iscsi-initiator-utils-6.2.0.872-6.100.1.el5.x86_64
Upgrading lm_sensors-2.10.7-9.el5.x86_64
Upgrading ocfs2-tools-1.8.2-4.el5.x86_64
Upgrading 1:net-snmp-libs-5.3.2.2-17.0.1.el5_8.1.x86_64
Upgrading mailx-8.1.1-44.2.2.x86_64
Upgrading device-mapper-multipath-libs-0.4.9-46.100.5.el5.x86_64
Upgrading device-mapper-multipath-0.4.9-46.100.5.el5.x86_64
Upgrading 1:net-snmp-5.3.2.2-17.0.1.el5_8.1.x86_64
Upgrading 1:net-snmp-utils-5.3.2.2-17.0.1.el5_8.1.x86_64
Upgrading elfutils-libs-0.137-3.el5.x86_64
Upgrading kexec-tools-2.0.3-4.0.7.el5.x86_64
Upgrading ovmwatch-1.0-20.x86_64
Upgrading devmon-1.0-28.x86_64
Upgrading osc-plugin-manager-1.2.8-26.el5.noarch
Upgrading enterprise-linux-ovs-5-5.208.9.x86_64
Upgrading initscripts-8.45.30-2.100.27.el5.x86_64
Upgrading 4:vixie-cron-4.1-81.el5.x86_64
Upgrading 1:smartmontools-5.42-2.100.2.el5.x86_64
Upgrading nash-5.1.19.6-71.100.1.el5_7.5.x86_64
Upgrading mkinitrd-5.1.19.6-71.100.1.el5_7.5.x86_64
Upgrading kernel-uek-firmware-2.6.39-300.29.1.el5uek.noarch
Upgrading kernel-uek-2.6.39-300.29.1.el5uek.x86_64
Upgrading kmod-openvswitch-uek-1.6.90-2.x86_64
Upgrading openvswitch-1.6.90-7.x86_64
Upgrading grub-0.97-13.5.100.3.x86_64
Upgrading ovs-release-3.2-5.208.9.x86_64
warning: /etc/issue created as /etc/issue.rpmnew
Upgrading python-urlgrabber-3.9.1-9.100.3.el5.noarch
Upgrading sos-1.7-9.49.100.1.el5.noarch
Upgrading osc-oracle-generic-1.1.0-74.el5.noarch
Upgrading ovm-consoled-0.1-11.noarch
Upgrading osc-plugin-manager-devel-1.2.8-26.el5.noarch
Upgrading osc-oracle-ocfs2-0.1.0-38.el5.noarch
Upgrading vmpinfo3-sosreport-1.0.0-6.el5.noarch
Upgrading xen-4.1.3-25.el5.3.x86_64
Upgrading vbox-img-1.0-6.x86_64
Upgrading xen-devel-4.1.3-25.el5.3.x86_64
Upgrading ntp-4.2.2p1-9.100.1.el5_4.1.x86_64
warning: /etc/ntp.conf created as /etc/ntp.conf.rpmnew
warning: /etc/monitor/config.yml saved as /etc/monitor/config.yml.rpmsave
It should be noted that Anaconda wants to "initialize" the OCFS repository on the local storage which you should decline. Anaconda wants a
partition table but OCFS repository is laid down directly on the block device without partitioning.
[root@ovm311 ~]# fdisk -l
Disk /dev/sdb: 3516.6 GB, 3516684828672 bytes
255 heads, 63 sectors/track, 427545 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sda: 77.3 GB, 77309411328 bytes
255 heads, 63 sectors/track, 9399 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1        8889    71400861   83 Linux
/dev/sda2            8890        9399     4096575   82 Linux swap / Solaris
You should also skip the install of the boot loader.

Updating OVM 3 host to use "brbond0" vs "xend" managed bridge to allow direct hosting of OVM Manager VM.
Update "ifcfg-bond0",
[root@ovm322 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
BONDING_OPTS="mode=1 miimon=250 use_carrier=1 updelay=500 downdelay=500 primary=eth0"
ONBOOT=yes
BRIDGE=brbond0
Create "ifcfg-brbond0",
[root@ovm322 ~]# cat /etc/sysconfig/network-scripts/ifcfg-brbond0
DEVICE=brbond0
BOOTPROTO=bridge
ONBOOT=yes
IPADDR=A.B.C.D # IP address of ovm322
NETMASK=255.255.254.0
NETWORK=A.B.C.0
GATEWAY=A.B.C.1
Update "/etc/xen/xend-config.sxp",
# Enable network-bridge, JAP 20120618
# Disable network-bridge, JAP 20131223
#(network-script network-bridge)
Update "vif" for OVM Manager 3 "vm.cfg",
[root@ovm322 ~]# grep ^vif /etc/xen/auto/ovm322-m
vif = ['type=netfront, bridge=brbond0']

Similar Messages

OVM 3.2.1 upgrade issues

Hi all,
I have upgraded the Oracle VM manager and server from 3.0.3 to 3.2.1. OVM server and manager upgrade ran fine but the guest machine which are created using OVM 3.0.3 versions are hanging. At OVM 3.0.3 while creating a server pool, I used the same OVM server ip address instead of a new virual ip address. When I try to create a server pool with the same ip address I am getting an error like ORMRU_000044E cannot se the virtual IP address because the IP address is already in use of the server. I have tested this on development still facing the same problem. I have tried even upgrading to OVM manager and server to 3.2.2, still it is not allowing me create a server pool with the same OVM server ip address.
Please let me know if anyone faced the same problem. I have 7 different OVM 3.0.3 production servers with critical guest machines running. I used RAW disk space of the server to create the virtual machines.
Thanks
Rao

Hi all,
I have upgraded the Oracle VM manager and server from 3.0.3 to 3.2.1. OVM server and manager upgrade ran fine but the guest machine which are created using OVM 3.0.3 versions are hanging. At OVM 3.0.3 while creating a server pool, I used the same OVM server ip address instead of a new virual ip address. When I try to create a server pool with the same ip address I am getting an error like ORMRU_000044E cannot se the virtual IP address because the IP address is already in use of the server. I have tested this on development still facing the same problem. I have tried even upgrading to OVM manager and server to 3.2.2, still it is not allowing me create a server pool with the same OVM server ip address.
Please let me know if anyone faced the same problem. I have 7 different OVM 3.0.3 production servers with critical guest machines running. I used RAW disk space of the server to create the virtual machines.
Thanks
Rao

OVM 3.2.2 Upgrade - OVS account password

I just downloaded the OVM 3.2.2 upgrade and started running the runUpgraded.sh script. I can't seem to get past the password prompt for the ovs user account for MySQL.
I've tried every password I could possibly think of. Is there a pre-defined password for the ovs account in MySQL?
./runUpgrader.sh
2013-03-19 11:27:53
2013-03-19 11:27:53 Starting Oracle VM Manager upgrade...
2013-03-19 11:27:53
2013-03-19 11:27:53 Oracle VM Manager 3.2.2.520 upgrade utility
2013-03-19 11:27:53
2013-03-19 11:27:53
2013-03-19 11:27:53 It is highly recommended to do a full database repository backup prior to upgrading Oracle VM Manager ...
2013-03-19 11:27:53
2013-03-19 11:27:53 Press [Enter] key to continue ...
2013-03-19 11:27:54
2013-03-19 11:27:54 Oracle VM Manager is running ...
2013-03-19 11:28:14 Verifying installation status ...
2013-03-19 11:28:14 Read Oracle VM Manager config file ...
2013-03-19 11:28:14 Found Oracle VM Manager install files ...
2013-03-19 11:28:14 Found Oracle VM Manager upgrader ...
2013-03-19 11:28:14 Found Oracle WebLogic Server ...
2013-03-19 11:28:14 Found Java ...
2013-03-19 11:28:14 Using the following information :
2013-03-19 11:28:14 Database type : MySQL
2013-03-19 11:28:14 Database Host : localhost
2013-03-19 11:28:14 Database SID : ovs
2013-03-19 11:28:14 Database LSNR : 49500
2013-03-19 11:28:14 Oracle VM Schema : ovs
2013-03-19 11:28:14 Oracle VM Manager UUID : 0004fb0000010000f9cdd3f46621fd16
2013-03-19 11:28:14 Current Build ID : 3.2.1.516
2013-03-19 11:28:14 Upgrade from version : 3.2.1
2013-03-19 11:28:14 Upgrade to version : 3.2.2
2013-03-19 11:28:14 Using /tmp/workdir.OsQPV18773 for backup and export location.
2013-03-19 11:28:14 Using /tmp/patchdir.NhUx18775 for patching.
Enter password for user ovs :
2013-03-19 11:28:16 Invalid Oracle VM Manager Database Credentials... Exiting upgrade process.

Nevermind, uninstalled and installed 3.2.2
Once I read this during the install, I knew what I had done wroing with the upgrade password.
One password is used for all users created and used during the installation.
Enter a password for all logins used during the installation:
Invalid password.
Passwords need to be between 8 and 16 characters in length.
Passwords must contain at least 1 lower case and 1 upper case letter.
Passwords must contain at least 1 numeric value.
Edited by: esinger on Mar 20, 2013 9:43 AM

OVM 3.0.3 import VirtualBox OVM Manager 3.0.3 OVA template

VirtualBox Template for Oracle VM Manager 3.0.3,
http://www.oracle.com/technetwork/server-storage/vm/template-1482544.html
The OVM 3.0.3 host should be configured with enough space to accommodate import of OVA template. In
this case 36G was allocated for "sda",
[root@ovm303 ~]# fdisk -l /dev/sda
Disk /dev/sda: 38.6 GB, 38654705664 bytes
255 heads, 63 sectors/track, 4699 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 4189 33648111 83 Linux
/dev/sda2 4190 4699 4096575 82 Linux swap / Solaris
Post OVA import disk usage,
[root@ovm303 ~]# df -T -t ext3
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sda1 ext3 32594216 24105604 6806208 78% /.
[root@ovm303 ~]# cat /etc/motd
Warning: making manual modifications in the management domain
might cause inconsistencies between Oracle VM Manager and the server.
[root@ovm303 ~]# head -4 /etc/ovs-info
OVS summary
release: 3.0.3
date: 201111300901
build: 123
The contents of "ovs-info" also include package information.
The "vbox-img" package is something new in OVM 3.0.3,
[root@ovm303 ~]# grep vbox-img /etc/ovs-info
vbox-img-1.0-2
[root@ovm303 ~]# rpm -ql vbox-img
/usr/bin/vbox-img
/usr/share/doc/vbox-img-1.0
/usr/share/doc/vbox-img-1.0/COPYING
[root@ovm303 ~]# vbox-img --help
Oracle VM VirtualBox Disk Utility 4.1.3
(C) 2005-2011 Oracle Corporation
All rights reserved.
Usage: vbox-img
setuuid --filename <filename>
[--format VDI|VMDK|VHD|...]
[--uuid <uuid>]
[--parentuuid <uuid>]
[--zeroparentuuid]
convert --srcfilename <filename>
--dstfilename <filename>
[--stdin]|[--stdout]
[--srcformat VDI|VMDK|VHD|RAW|..]
[--dstformat VDI|VMDK|VHD|RAW|..]
[--variant Standard,Fixed,Split2G,Stream,ESX]
info --filename <filename>
compact --filename <filename>
createcache --filename <filename>
--size <cache size>
Download "OracleVMManager3" OVA,
[root@ovm303 xen]# mkdir /etc/xen/ovm303-m
[root@ovm303 ~]# cd /etc/xen/ovm303-m
[root@ovm303 xen]# wget http://download.oracle.com/otn-pub/otn_software/OracleVMManager3.ova
--2012-03-14 17:06:01-- http://download.oracle.com/otn-pub/otn_software/OracleVMManager3.ova
Length: 4234452992 (3.9G) [text/plain]
Saving to: `OracleVMManager3.ova'
100%[====================================>] 4,234,452,992 834K/s in 55m 36s
2012-03-14 18:01:38 (1.21 MB/s) - `OracleVMManager3.ova' saved [4234452992/4234452992]
[root@ovm303 xen]# md5sum OracleVMManager3.ova
75fc334422eda6c3425a2f09fb88f9e0 OracleVMManager3.ova
Unpack OVA,
[root@ovm303 xen]# tar tvf OracleVMManager3.ova
-rw------- someone/someone 59626 2012-01-12 17:42:49 OracleVMManager3.ovf
-rw------- someone/someone 1987182592 2012-01-12 17:48:06 OracleVMManager3-disk1.vmdk
-rw------- someone/someone 2247208960 2012-01-12 17:51:24 OracleVMManager3-disk2.vmdk
[root@ovm303 ovm303-m]# tar xvf OracleVMManager3.ova
OracleVMManager3.ovf
OracleVMManager3-disk1.vmdk
OracleVMManager3-disk2.vmdk
Use "vbox-img" to show "OracleVMManager3-disk1.vmdk",
[root@ovm303 ovm303-m]# vbox-img info --filename OracleVMManager3-disk1.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "OracleVMManager3-disk1.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=52428800
Header: uuidCreation={f3859e00-962c-440f-a63d-feb7b731d5da}
Header: uuidModification={00000000-0000-0000-0000-000000000000}
Header: uuidParent={00000000-0000-0000-0000-000000000000}
Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
Convert "OracleVMManager3-disk1.vmdk" to RAW,
[root@ovm303 ovm303-m]# vbox-img convert srcfilename OracleVMManager3-disk1.vmdk dstfilename OracleVMManager3-disk1.img srcformat VMDK dstformat RAW
Converting image "OracleVMManager3-disk1.vmdk" with size 26843545600 bytes (25600MB)...
[root@ovm303 ovm303-m]# file OracleVMManager3-disk1.img
OracleVMManager3-disk1.img: x86 boot sector; partition 1: ID=0x83, active, starthead 1, startsector 63, 208782 sectors; partition 2: ID=0x8e, starthead 0, startsector 208845, 52211250 sectors, code offset 0x48
[root@ovm303 ovm303-m]# fdisk -l OracleVMManager3-disk1.img
last_lba(): I don't know how to handle files with mode 8180
You must set cylinders.
You can do this from the extra functions menu.
Disk OracleVMManager3-disk1.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
OracleVMManager3-disk1.img1 * 1 13 104391 83 Linux
OracleVMManager3-disk1.img2 14 3263 26105625 8e Linux LVM
Partition 2 has different physical/logical endings:
phys=(1023, 254, 63) logical=(3262, 254, 63)
Use "vbox-img" to show "OracleVMManager3-disk2.vmdk",
[root@ovm303 ovm303-m]# vbox-img info --filename OracleVMManager3-disk2.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "OracleVMManager3-disk2.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=20971520
Header: uuidCreation={abc43be0-7a43-4ba2-a205-eaf37184a4d3}
Header: uuidModification={00000000-0000-0000-0000-000000000000}
Header: uuidParent={00000000-0000-0000-0000-000000000000}
Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
Convert "OracleVMManager3-disk2.vmdk" to RAW,
[root@ovm303 ovm303-m]# vbox-img convert srcfilename OracleVMManager3-disk2.vmdk dstfilename OracleVMManager3-disk2.img srcformat VMDK dstformat RAW
Converting image "OracleVMManager3-disk2.vmdk" with size 10737418240 bytes (10240MB)...
[root@ovm303 ovm303-m]# file OracleVMManager3-disk2.img
OracleVMManager3-disk2.img: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 20964762 sectors, extended partition table (last)\011
[root@ovm303 ovm303-m]# fdisk -l OracleVMManager3-disk2.img
last_lba(): I don't know how to handle files with mode 8180
You must set cylinders.
You can do this from the extra functions menu.
Disk OracleVMManager3-disk2.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
OracleVMManager3-disk2.img1 1 1305 10482381 83 Linux
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(1304, 254, 63)
Update disk image "/boot" configuration using loopback mount,
[root@ovm303 ovm303-m]# mkdir boot
[root@ovm303 ovm303-m]# kpartx -l OracleVMManager3-disk1.img
loop1p1 : 0 208782 /dev/loop1 63
loop1p2 : 0 52211250 /dev/loop1 208845
loop deleted : /dev/loop1
[root@ovm303 ovm303-m]# kpartx -a OracleVMManager3-disk1.img
[root@ovm303 ovm303-m]# mount /dev/mapper/loop1p1 boot
Update "/boot/grub/device.map",
[root@ovm303 ovm303-m]# cat boot/grub/device.map
# this device map was generated by anaconda
(hd0) /dev/hda
Update "/boot/grub/grub.conf" to use non-UEK kernel to avoid issues with OL5u7 default UEK boot and HVM,
[root@ovm303 ovm303-m]# grep default boot/grub/grub.conf
default=1
Mount "/" logical volume,
[root@ovm303 ovm303-m]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
[root@ovm303 ovm303-m]# vgchange -ay VolGroup00
2 logical volume(s) in volume group "VolGroup00" now active
[root@ovm303 ovm303-m]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 -wi-a- 19.06G
LogVol01 VolGroup00 -wi-a- 5.81G
[root@ovm303 ovm303-m]# mkdir root
[root@ovm303 ovm303-m]# ls /dev/VolGroup00/
LogVol00 LogVol01
[root@ovm303 ovm303-m]# mount /dev/VolGroup00/LogVol00 root
Update "/etc/inittab" to boot single user,
[root@ovm303 ovm303-m]# grep id root/etc/inittab
id:1:initdefault:
Update "/etc/fstab" to ignore "/u01" block device mount,
[root@ovm303 ovm303-m]# grep sdb root/etc/fstab
#/dev/sdb1 /u01 ext3 defaults 1 1
Unmount "/boot" and "/",
[root@ovm303 ovm303-m]# umount boot
[root@ovm303 ovm303-m]# umount root
[root@ovm303 ovm303-m]# vgchange -an VolGroup00
0 logical volume(s) in volume group "VolGroup00" now active
[root@ovm303 ovm303-m]# kpartx -d OracleVMManager3-disk1.img
loop deleted : /dev/loop1
The OVM 3.0.3 network bridge configuration uses "bond0" vs "xenbr0".
Configure "vm.cfg",
[root@ovm303 ovm303-m]# cat vm.cfg
# (H)ardware (V)irtual (M)achine configuration
# /etc/xen/xmexample.hvm
kernel = 'hvmloader'
builder = 'hvm'
memory = '4096'
# The number of cpus guest platform has, default=1
#vcpus=1
# PXE boot
#bootloader = '/usr/bin/pypxeboot'
#bootloader = '/usr/bin/pygrub'
# Virtual block device configuration using file:
# dd if=/dev/zero of=/$VM_PATH/$VM_NAME/System.img bs=1M count=$MB
# disk = [ 'file:/$VM_PATH/$VM_NAME/System.img,ioemu:hda,w', ]
# Configuration using physical disk logical volume:
# lvcreate --size ${GB}G --name $VM_NAME $VG_NAME
# disk = [ 'phy:/dev/$VG_NAME/$VM_NAME,xvda,w',]
# CDROM configuration using file:
# disk = [ 'file:/$BOOT_ISO_NAME,hdc:cdrom,r', ]
disk = [ 'file:/etc/xen/ovm303-m/OracleVMManager3-disk1.img,ioemu:hda,w', 'file:/etc/xen/ovm303-m/OracleVMManager3-disk2.img,ioemu:hdb,w', ]
# Domain name
name = "ovm303-m"
# Networking
# Network bridge status:
# /etc/xen/scripts/network-bridge status
# 'bridge' should be proper interface e.g. xenbr0
vif = ['type=ioemu, bridge=bond0']
# boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot = "cdn"
# Enable HV VNC console
# Uses avaiablle next VNC port $OVM_SERVER_HOST:0 == 5900, :1 == 5901 etc
# Use "xm list -l" to determince VNC port "location"
vnc=1
vncunused=1
vnclisten="0.0.0.0"
vncpasswd=''
sdl=0
# Set the real time clock to local time [default=0 i.e. set to utc]
# Allows Win VM clock to work with UTC on OVM host system.
#localtime=1
Start VM,
[root@ovm303 ovm303-m]# xm create vm.cfg
Using config file "./vm.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Current bridge,
[root@ovm303 ~]# brctl show
bridge name bridge id STP enabled interfaces
Update "/etc/xen/xend-config.sxp" to enable "network-bridge",
[root@ovm303 ovm303-m]# cp /etc/xen/xend-config.sxp /etc/xen/xend-config.sxp.orig
[root@ovm303 ovm303-m]# diff /etc/xen/xend-config.sxp /etc/xen/xend-config.sxp.orig
165,167d164
< # Enable network-bridge, JAP 20120322
< (network-script network-bridge)
<
[root@ovm303 ~]# service xend restart
Restarting xend...
xend daemon (pid 8848) is running...
[root@ovm303 ~]# brctl show
bridge name bridge id STP enabled interfaces
bond0 8000.002128d5ce86 no pbond0
Start VM,
[root@ovm303 ovm303-m]# xm create vm.cfg
Using config file "./vm.cfg".
Started domain ovm303-m (id=1)
Determine VNC console session,
[root@ovm303 ovm303-m]# xm list -l ovm303-m | grep location
(location 0.0.0.0:5900)
(location 3)
VNC console session. The "oraclevm-template" tools are not run in single user so hostname is "localhost",
[root@localhost ~]# who -r
run-level S 2012-03-23 09:09 last=1
Update "/etc/fstab" for "/u01" mount to use label,
[root@localhost ~]# grep /u01 /etc/fstab
#/dev/sdb1 /u01 ext3 defaults 1 1
[root@localhost ~]# blkid
/dev/mapper/VolGroup00-LogVol01: TYPE="swap"
/dev/mapper/VolGroup00-LogVol00: UUID="2751f1b2-836b-4786-ae71-8b402e0f8503" TYPE="ext3"
/dev/VolGroup00/LogVol00: UUID="2751f1b2-836b-4786-ae71-8b402e0f8503" SEC_TYPE="ext2" TYPE="ext3"
/dev/VolGroup00/LogVol01: TYPE="swap"
/dev/hda1: LABEL="/boot" UUID="8701866e-5ed5-49f7-9597-bb9709d22359" TYPE="ext3"
/dev/hdb1: UUID="5f9a7bef-3a6d-4a83-b288-638537424fa7" SEC_TYPE="ext2" TYPE="ext3"
[root@localhost ~]# e2label /dev/hdb1 u01
[root@localhost ~]# grep u01 /etc/fstab
LABEL=u01 /u01 ext3 defaults 1 1
[root@localhost ~]# mount /u01
[root@localhost ~]# df /u01
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hdb1 10317828 4250832 5542880 44% /u01
As configured the default run level will be elevated to "5" by the "/etc/rc.local" script. This enables a
console desktop for user "ovm". This is unneeded and will be implemented by VNC session for user
"ovm".
Update "/etc/inittab" to enable full multiuser mode run level 3,
[root@localhost ~]# grep id /etc/inittab
id:3:initdefault:
Disable "/etc/rc.local" run level elevation,
[root@localhost ~]# tail -2 /etc/rc.local
# Disable local forced runlevel 5, JAP 20120404
#telinit 5
Disable firewall to allow VNC connections,
[root@localhost ~]# chkconfig --list iptables
iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@localhost ~]# chkconfig iptables off
[root@localhost ~]# chkconfig --list ip6tables
ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@localhost ~]# chkconfig ip6tables off
Reboot,
[root@localhost ~]# reboot
Broadcast message from root (pts/0) (Mon Apr 2 09:22:17 2012):
The system is going down for reboot NOW!
Post "oraclevm-template" configuration e.g. defining FQDN and static IP addresss etc. OVM Manager 3.0.3 is up.
Configure VNC for "ovm",
[root@ovm303-m ~]# su - ovm
[ovm@ovm303-m ~]$ vncserver
You will require a password to access your desktops.
Password: Welcome1
Verify: Welcome1
xauth: creating new authority file /home/ovm/.Xauthority
New 'ovm303-m:1 (ovm)' desktop is ovm303-m:1
Creating default startup script /home/ovm/.vnc/xstartup
Starting applications specified in /home/ovm/.vnc/xstartup
Log file is /home/ovm/.vnc/ovm303-m:1.log
[ovm@ovm303-m ~]$ vncserver -kill :1
Killing Xvnc process ID 12499
Update "xstartup",
[ovm@ovm303-m ~]$ cat /home/ovm/.vnc/xstartup
#!/bin/sh
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
#[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
#[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
#xsetroot -solid grey
#vncconfig -iconic &
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &
[ovm@ovm303-m ~]$ vncserver
New 'ovm303-m:1 (ovm)' desktop is ovm303-m :1
Starting applications specified in /home/ovm/.vnc/xstartup
Log file is /home/ovm/.vnc/ovm303-m:1.log
Configure "/etc/sysconfig/vncservers",
[root@ovm303-m ~]# chkconfig --list vncserver
vncserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[root@ovm303-m ~]# chkconfig vncserver on
[root@ovm303-m ~]# chkconfig --list vncserver
vncserver 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@ovm303-m ~]# tail -2 /etc/sysconfig/vncservers
# Start VNC session for ovm, JAP 20120404
VNCSERVERS="1:ovm"

Thanks Jim - looks great!

VM live migration during OVM server upgrade

Hi Guys,
I'm planning to upgrade OVM 3.1.1 to 3.2.7.
There are 4 OVM Servers in server pool and all is using the same CPU family which means the live migration is possible.
I just wondering if I upgrade one OVM server to 3.2.7 first and then is it still available to live migrate VMs from 3.1.1. servers to new 3.2.7 server?
Thanks in advance.
Jay

Hi Jay,
I'd do the following:
- free up one OVS by migrating all guests to the remaining OVS
- upgrade OVM Manager straigh to 3.2.8
- upgrade the idle OVS to 3.2.8
- live migrate your guests from one 3.1.1 OVS to the new, idle 3.2.8 OVS - if not using OVMM, then using xm
- round robin upgrade your remaining OVS
I've done that a couple of times…
Cheers,
budy

Failed OVM Server Upgrade from 3.0.2 to 3.1.1

I was trying to upgrade my OVM Server environment from *3.0.2* to *3.1.1* using the CD. I got the following error message after choosing the Upgrade option: Oracle VM server 3.0.2 (cciss/c0d0p2). The other option was to Reinstall System.
+"Error mounting device sda2 as /:+
+Device or resource busy+
+This most likely means this+
+partition hast not been formatted.+
+Press OK to reboot your system."+
My hardware is a HP BL465c G7 server, which is certified by Oracle to run the OVM 3.1.
http://linux.oracle.com/pls/apex/f?p=117:2:3396212307219555::NO::P2_CERT_ID:1871
Any advice that can help me find the way to upgrade my servers?
Thanks in advance,
Andrés L.

Hi,
I tried "yum update -y" and after reboot I encountered a kernel panic after the following message: switchroot: mount failed: No such file or directory.
So I got to reinstall ovm 3.0.3 from scratch.
Maybe the hard disk drivers in 3.1.1 kernel version (uek2) are not compatible with my server disks.
If someone has an accurate explanation to this issue, could be helpfull.
Best Regards,
Andres Loaiza.

OVM and OCFS2 1.6

Ok this question may be a little complicated so I'll start by explaining what I'm trying to achive.
I have 3 OVM 2.2.1 servers in 1 Server pool running OCFS2 on an EMC SAN.
I also ave an Oracle Enterprise Linux server which connects to the same ocfs2 cluster for performing backups of the VMs.
Currently I have to pause all VMS and backup the shared storage in order to backup all of my VMs.
I would like to use reflink so I can do this without pausing them.
Can I achieve this by
1 upgrading all OVM servers and my OEL Server to OCFS2 1.6 or is the Kernel upgrade not supported in OVM 2.2.1
or
2 Upgrading my OEL server to OCFS2 1.6 and doing the reflinks there, but leave the OVM machines on 1.4 as the doco states the 1.4 and 1.6 are compatible with one another.
Thanks in advance

Hi,
unfortunately OCFS2 1.6 is not yet supported on OVM 2.2.1.
I am waiting all day that Oracle will finally release OVM 3.0, which will incorporate the new OCFS2 1.6 with all it functions.
This would also resolv your problem then...
Regarding your second option, I don't know if this will work. But it seems the only solution you have right now...
Sebastian

Oracle VM 3.1.1 Manager - OVM Servers in "Starting" status

Hi,
today I've downloaded Oracle VM Manager 3.1.1(Upgrade only) from e-delivery, and upgraded my previous version of OVMM 3.0.3 without any problems. My servers are still running on OVM Server 3.0.3 version.
Usually, my practice for upgrading was:
- first upgrade OVMM
- login into OVMM
- migrate some VMs to free-up one OVM server
- then I upgrade that server to newer version of OVM Server
- bring back VMs to updated server to free-up another one and so on.
After login into new OVMM 3.1.1, I see all my servers, storage and VMs running on these servers as they was set before. But, my servers are in Starting state. I cannot manage any of my VMs, nothing! Later on, I've manually restarted one server(S1) and tried to upgrade it to OVM 3.1.1 version but I had some problems with mounting ISO, so I've only restated it. After that, that server(S1) showed as Running and OK. Then I tried to do that with another server(S2), migrated VMs to S1 server, restarted S2 but it remained Starting.
So now my situation is:
- have one server(S1) in Running state with several VMs
- other servers are in Starting state also with some VMs
I cannot shutdown servers, as theirs status is not Running, cannot migrate or manage VMs at all.
Please, how can I set right status for my servers without shutting VMs?
Thanks in advance.

Hi,
now I've got very serious situation. I've reinstalled OVMM 3.1.1 with -uuid option, and tried to rediscover servers. Only one server shows up, S1, no other servers, they cannot be added. Error from ovs-agent log on these servers show this message when I try to rediscover it:
ERROR (OVSCommons:143) catch_error: rpmdb open failed
Luckly, my VMs are working fine, but now I'm not sure till when they will.
Is there any possible solution to resolve this?
Best regards,
I resolved ERROR (OVSCommons:143) catch_error: rpmdb open failed by executing two commands on each server that I couldn't add:
rm -rf /var/lib/rpm/__db*
rpm --rebuilddb
after this my servers automatically were added in OVMM. Then, I rediscovered repository and my VMs showed up as well. So, could it be possible that corrupted rpm database caused all this?
Thanks.
Edited by: DBagy on May 15, 2012 10:34 AM

OVM 3.1.1, PVM guests time skewed?

We recently upgraded from OVM 3.0.3 to 3.1.1, and our Oracle Enterprise Linux 5.6 PVM (OVM Templates) guests time is getting set ahead hours at a time, not just running slow, but hours.
Anyone have any ideas how to prevent that, or what may be causing it?

By default PVM Xen guests try and synchronise their clock with that of their hypervisor so one thing to check is what the "local" time is. The dance for configuring the OVM manager as the NTP server is rather error prone.
We get much better results by disabling this synchronisation in RedHat 5 guests via /etc/sysctl.conf
xen.independent_wallclock = 1
This means that the guests will then rely on their own ntp daemon and the kernel tick from the hypervisor to keep the correct time.

Unable to Boot OVM Manager ISO from iLOM

Hi all,
I am trying to boot the OVM Manager ISO on a Fire X4150 using the console redirection but all that comes up is "Grub" and allows no further interaction. I've tried downloading the ISO multiple times, using an older version of the OVM installation ISO, and upgraded the iLOM firmware to the latest and greatest. When I use the OVM Server ISO, it boots up normally and starts the installation process. The machine that I am running the remote console from and has the ISO image is in the same rack as the server where I would want to install OVM Manager.
Getting physical access to pop a DVD in the drive is limited so really trying to figure out a way I can do this remotely.
Any one else have this issue and knows of a workaround?
Thanks,
Peter

FYI, update the FIRWARE on your Sun Fire X4150s. I was on a project a couple weeks ago and we where unable to use the ILOM to mount ISO files. After 10 hours of FUN, we discovered that its was a BUG! Update each server to the latest FIRMWARE, i.e. download the FIRWARE, and update each node from its web portal.
Sun x86 is FUN!
Roddy

OVM 3.0.3 SDK

Any ideas when the OVM 3.0.3 SDK will be posted on edelivery?
I've always found the OVM SDK to be a problem due to the fact that you require an up and running OVM environment to actually build drivers. For example imagine you needed to build a driver for a NIC on your server, how exactly do you do that without having a functional OVM environment running to deploy this SDK template? I wish oracle allowed an option to add development packages just to make driver building easy. :( Not to mention if I wanted to build a driver say today for OVM 3.0.3, without the OVM 3.0.3 SDK I'm stuck.
Thanks for your help and input,
Roger

Roger wrote:
Any ideas when the OVM 3.0.3 SDK will be posted on edelivery?It'll be up in the next couple of weeks.
I wish oracle allowed an option to add development packages just to make driver building easy. :( Not to mention if I wanted to build a driver say today for OVM 3.0.3, without the OVM 3.0.3 SDK I'm stuck.We would never allow development packages into Dom0 as this could potentially impact the security and size of that environment. Dom0 is meant to be highly controlled. We would rather try and incorporate the drivers into the Oracle VM 3.0 kernel. We are currently merging the kernel development for the Oracle Linux UEK2 and Oracle VM, so that driver submissions from partners for Oracle Linux would automatically transfer into Oracle VM as well. Coupled with the fact that Oracle VM will soon use the UEK2 as the Dom0 kernel which is based off Linux 3.0.6, so it'll have much newer drivers for existing hardware and far greater hardware support.
Keep in mind that you don't have to run the SDK template on the same version of Oracle VM, i.e. you can install the 3.0 SDK on Oracle VM 2.x. Or the 3.0.3 SDK on 3.0.1 or 3.0.2, which means once the SDK is released, you can build the drivers you need in your test or development environment and test those on the latest release of Oracle VM before upgrading production.
Though, you do make an excellent point. I might see if I can get the Oracle VM SDK Template to boot on VirtualBox. :) No promises, though!

Guest VM become stalled randomly on OVM 3.3.2

I upgrade my OVM to 3.3.2. Some guest VM halted without any error event.
I can't ping the guest vm. But the status is still "Running" from VM manager.
Any idea?
HP DL360 G7
Guest VM: Oracle Linux 6.6
Domain Type: XEN_PVM
BTW, I already applied patch xen-4.3.0-55.el6.22.18 as mentioned in Migration of domU broken in 3.3.2?

Oops, the vm got hang again. I can login vm through manager console. But the network is dead. The /var/log/messages from VM Server shows as follow:
Apr 28 18:05:49 ovs6 kernel: vif vif-7-0 vif7.0: txreq.offset: cfa, size: 3846, end: 7168
Apr 28 18:05:49 ovs6 kernel: vif vif-7-0 vif7.0: fatal error; disabling device
Apr 28 18:05:49 ovs6 kernel: 10ba1df20d: port 3(vif7.0) entered disabled state
After kill the vm and start it again. The log add following lines:
Apr 28 21:20:34 ovs6 kernel: 10ba1df20d: port 3(vif7.0) entered disabled state
Apr 28 21:20:34 ovs6 kernel: device vif7.0 left promiscuous mode
Apr 28 21:20:34 ovs6 kernel: 10ba1df20d: port 3(vif7.0) entered disabled state
Apr 28 21:20:39 ovs6 kernel: device vif8.0 entered promiscuous mode
Apr 28 21:20:41 ovs6 kernel: xen-blkback:ring-ref 9, event-channel 19, protocol 1 (x86_64-abi) persistent grants
Apr 28 21:20:44 ovs6 kernel: 10ba1df20d: port 2(vif8.0) entered forwarding state
Apr 28 21:20:44 ovs6 kernel: 10ba1df20d: port 2(vif8.0) entered forwarding state
Apr 28 21:20:47 ovs6 kernel: ocfs2: Unaligned AIO/DIO on inode 156893450 on device dm-1 by loop0
Actually the vm should use port 2, not port 3.

/proc/cpuinfo | grep vmx -- output changing between OVM Server 2.1 and 2.2

Have not seen this issue before.
I have a Dell 2950 with 2 Intel Xeon Quad-Core CPUs , with Virtualization enabled in the BIOS.
When I install OVM Server 2.1.5, my cpus support virtualization (based on "cat /proc/cpuinfo | grep vmx" returning data)
When I upgrade to OVM Server 2.2, my cpus no longer support virtualization ( based on "cat /proc/cpuinfo | grep vmx" returning NO data)
If I do a clean install of OVM Server 2.2, my cpus do not support virtualization ( based on "cat /proc/cpuinfo | grep vmx" returning NO data)
I have to be missing something simple.

Thanks Herb.
# xm dmesg | grep -i vm
(XEN) VMX: Supported advanced features:
(XEN) HVM: VMX enabled
That is what I was looking for. They need to update Metalink Doc 468463.1.

OracleVM Image in OVM Manager is stuck at 'Initializing' condition.

I have a OracleVM server managed by a OracleVM Manager. OracleVM server version is 2.2.2 , Manager on 2.1.5 . When I started an image after its creation, it got stuck at the 'Initializing' state in the Oracle VM Manager screen. The actual image started up fine in the server as shown by 'xm list' . I restarted the OVM manager system and also the OVM image, no go. Please help.

itsakc wrote:
I have a OracleVM server managed by a OracleVM Manager. OracleVM server version is 2.2.2 , Manager on 2.1.5 .You can't manage 2.2.2 servers with a 2.1.5 manager. You need to upgrade.

Disk add error on OVM

Oracle VM server release 2.1.2
Linux
Hi There,
I'm getting an error when I want to add a disk on OVM. There are all ready 16 disks (a-p), but gets error on 17th (p)
Error: ('cd81da11-4f92-0eeb-b6b2-d2f27521246f', 'VM_metrics')
Here is the config file :
name = "***o2db01"
memory = "8192"
disk = [ 'phy:/dev/mapper/mpath17,xvda,w',
'phy:/dev/mapper/mpath0,xvdb,w',
'phy:/dev/mapper/mpath1,xvdc,w',
'phy:/dev/mapper/mpath10,xvdd,w',
'phy:/dev/mapper/mpath11,xvde,w',
'phy:/dev/mapper/mpath12,xvdf,w',
'phy:/dev/mapper/mpath13,xvdg,w',
'phy:/dev/mapper/mpath14,xvdh,w',
'phy:/dev/mapper/mpath4,xvdi,w',
'phy:/dev/mapper/mpath5,xvdj,w',
'phy:/dev/mapper/mpath6,xvdk,w',
'phy:/dev/mapper/mpath7,xvdl,w',
'phy:/dev/mapper/mpath8,xvdm,w',
'phy:/dev/mapper/mpath9,xvdn,w',
'phy:/dev/mapper/mpath15,xvdo,w',
'phy:/dev/mapper/mpath19,xvdp,w',
'phy:/dev/mapper/mpath21,xvdq,w',
Is there a limit on the amount of disks that can be added?

Hi,
yes in OVM 2.1.2 there was a bug, allowing only 16 xvd* devices.
Workaround is to use /dev/sd* as device.
Better it would be to upgrade to OVM 2.2 where this is solved.
(Or even 3.0, but this is a major task).
Regards
Sebastian

OVM 3.1.1 upgrade to OVM 3.2.2 summary

Similar Messages

Maybe you are looking for