Creating an Oracle Linux VM Using virt-install

SUSE Product Topics SLES Virtualization
1

I’ve copied the contents of the Oracle Linux 6.3 installation media to an directory that’s exported via NFS:

[QUOTE]san2:~ # ls -1 /srv/md128/repositories/[COLOR="#FF0000"]oracle[/COLOR]/6.3/os/x86_64/
EFI
EULA
eula.en_US
eula.py
GPL
HighAvailability
images
isolinux
LoadBalancer
media.repo
Packages
README-en
README-en.html
RELEASE-NOTES-en
RELEASE-NOTES-en.html
RELEASE-NOTES-x86_64-en
RELEASE-NOTES-x86_64-en.html
RELEASE-NOTES-x86-en
RELEASE-NOTES-x86-en.html
repodata
ResilientStorage
RPM-GPG-KEY
RPM-GPG-KEY-oracle
ScalableFileSystem
Server
supportinfo
TRANS.TBL
UEK2[/QUOTE]

…and tried to use the directory to install an Oracle Linux VM with virt-install:

xen2:~ # virt-install -p --name dns2 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f310000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --graphics none

…but virt-install complains:

Starting install... ERROR Couldn't find xen kernel for Red Hat Enterprise Linux tree.

This is a tried-and-true methodology: I use this method for installing CentOS & SuSE regularly:

[QUOTE]san2:~ # ls -1 /srv/md128/repositories/[COLOR="#00FF00"]centos[/COLOR]/6.3/os/x86_64/
CentOS_BuildTag
.discinfo
EFI
EULA
GPL
images
isolinux
Packages
RELEASE-NOTES-en-US.html
repodata
RPM-GPG-KEY-CentOS-6
RPM-GPG-KEY-CentOS-Debug-6
RPM-GPG-KEY-CentOS-Security-6
RPM-GPG-KEY-CentOS-Testing-6
.treeinfo[/QUOTE]

xen2:~ # virt-install -p --name dns2 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f310000 --location nfs://192.168.0.2/srv/md128/repositories/centos/6.3/os/x86_64/ --graphics none

What is it that’s different about the Oracle Linux installation media that causes this failure? Is there a workaround?

Eric Pretorious
Truckee, CA

2

epretorious,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

3

Once more, with --debug:

[code]xen2:~ # virt-install -p --name dns2 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f300000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --debug
Thu, 14 Feb 2013 11:48:20 DEBUG Launched with command line:
/usr/bin/virt-install -p --name dns2 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e315f300000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --debug
Thu, 14 Feb 2013 11:48:20 DEBUG Requesting libvirt URI default
Thu, 14 Feb 2013 11:48:22 DEBUG Received libvirt URI xen:///
Thu, 14 Feb 2013 11:48:22 DEBUG Requesting virt method ‘xen’, hv type ‘default’.
Thu, 14 Feb 2013 11:48:22 DEBUG Received virt method ‘xen’
Thu, 14 Feb 2013 11:48:22 DEBUG Hypervisor name is ‘xen’
Thu, 14 Feb 2013 11:48:22 DEBUG DISPLAY is not set: defaulting to nographics.
Thu, 14 Feb 2013 11:48:22 DEBUG --graphics compat generated: none
Thu, 14 Feb 2013 11:48:22 DEBUG DistroInstaller location is a network source.
Thu, 14 Feb 2013 11:48:22 DEBUG Preparing mount at /var/tmp/virtinstmnt.r5psf_
Thu, 14 Feb 2013 11:48:22 DEBUG Attempting to detect distro:
Thu, 14 Feb 2013 11:48:22 DEBUG local hasFile: Couldn’t find /var/tmp/virtinstmnt.r5psf_/.treeinfo
Thu, 14 Feb 2013 11:48:22 DEBUG local hasFile: Couldn’t find /var/tmp/virtinstmnt.r5psf_/Fedora
Thu, 14 Feb 2013 11:48:22 DEBUG Detected a RHEL 5 Server distro
Thu, 14 Feb 2013 11:48:22 DEBUG Cleaning up mount at /var/tmp/virtinstmnt.r5psf_
Thu, 14 Feb 2013 11:48:22 DEBUG Guest.has_install_phase: True

Starting install…
Thu, 14 Feb 2013 11:48:22 DEBUG scratchdir=/var/lib/xen
Thu, 14 Feb 2013 11:48:22 DEBUG Preparing mount at /var/lib/xen/virtinstmnt.X0dm9e
Thu, 14 Feb 2013 11:48:22 DEBUG Attempting to detect distro:
Thu, 14 Feb 2013 11:48:22 DEBUG local hasFile: Couldn’t find /var/lib/xen/virtinstmnt.X0dm9e/.treeinfo
Thu, 14 Feb 2013 11:48:22 DEBUG local hasFile: Couldn’t find /var/lib/xen/virtinstmnt.X0dm9e/Fedora
Thu, 14 Feb 2013 11:48:22 DEBUG Detected a RHEL 5 Server distro
Thu, 14 Feb 2013 11:48:22 DEBUG local hasFile: Couldn’t find /var/lib/xen/virtinstmnt.X0dm9e/images/xen/vmlinuz
Thu, 14 Feb 2013 11:48:22 DEBUG Cleaning up mount at /var/lib/xen/virtinstmnt.X0dm9e
Thu, 14 Feb 2013 11:48:22 ERROR Couldn’t find xen kernel for Red Hat Enterprise Linux tree.
Thu, 14 Feb 2013 11:48:22 DEBUG Traceback (most recent call last):
File “/usr/bin/virt-install”, line 633, in start_install
noboot=options.noreboot)
File “/usr/lib64/python2.6/site-packages/virtinst/Guest.py”, line 1207, in start_install
self._prepare_install(meter, dry)
File “/usr/lib64/python2.6/site-packages/virtinst/Guest.py”, line 964, in _prepare_install
meter=meter)
File “/usr/lib64/python2.6/site-packages/virtinst/DistroInstaller.py”, line 429, in prepare
dev = self._prepare_kernel_and_initrd(guest, meter)
File “/usr/lib64/python2.6/site-packages/virtinst/DistroInstaller.py”, line 368, in _prepare_kernel_and_initrd
self.os_type)
File “/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py”, line 158, in acquireKernel
scratchdir, type)
File “/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py”, line 152, in _acquireMedia
None, media_cb)
File “/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py”, line 133, in _locationCheckWrapper
return callback(store, fetcher)
File “/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py”, line 145, in media_cb
media = store.acquireKernel(guest, fetcher, progresscb)
File “/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py”, line 276, in acquireKernel
{ “distro”: self.name, “type” : self.type })
RuntimeError: Couldn’t find xen kernel for Red Hat Enterprise Linux tree.[/code]

It appears that the last line provides the vital clue. i.e., The Oracle Linux 6.3 .iso is lacking a .treeinfo file. CentOS, however, includes a .treeinfo file for each of it’s installation .iso’s:

san2:/srv/md128/repositories/centos # find . -name .treeinfo ./5.7/os/i386/.treeinfo ./5.7/os/x86_64/.treeinfo ./5.8/os/i386/.treeinfo ./5.8/os/x86_64/.treeinfo ./5.9/os/i386/.treeinfo ./5.9/os/x86_64/.treeinfo ./6.0/os/x86_64/.treeinfo ./6.2/os/i386/.treeinfo ./6.2/os/x86_64/.treeinfo ./6.3/os/i386/.treeinfo ./6.3/os/x86_64/.treeinfo

The contents of .treeinfo seem fairly straight-forward:

[CODE]san2:/srv/md128/repositories # cat ./centos/6.3/os/x86_64/.treeinfo
[general]
family = CentOS
timestamp = 1341569485.3
variant =
totaldiscs = 1
version = 6.3
discnum = 1
packagedir =
arch = x86_64

[images-x86_64]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img
boot.iso = …/…/isos/x86_64/CentOS-6.3-x86_64-netinstall.iso
[images-xen]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img

[stage2]
mainimage = images/install.img[/CODE]

…so I started with the .treeinfo file for CentOS 6.3 and verified that it reflected the contents of the Oracle Linux 6.3 directory as well:

[code]san2:/srv/md128/repositories/centos # ll ./6.3/os/x86_64/
total 472
-rw-r–r–. 1 59999 59999 14 Jul 6 2012 CentOS_BuildTag
-rw-rw-r–. 1 59999 59999 33 Jul 6 2012 .discinfo
drwxrwxr-x. 3 59999 59999 17 Jul 6 2012 EFI
-rw-rw-r–. 1 59999 59999 212 Jun 23 2012 EULA
-rw-rw-r–. 1 59999 59999 18009 Jun 23 2012 GPL
drwxr-xr-x. 3 59999 59999 74 Jul 6 2012 images
drwxr-xr-x. 2 59999 59999 4096 Jul 6 2012 isolinux
drwxrwxr-x. 2 59999 59999 339968 Jul 5 2012 Packages
-rw-rw-r–. 1 59999 59999 1354 Jun 23 2012 RELEASE-NOTES-en-US.html
drwxr-xr-x. 2 59999 59999 4096 Jul 6 2012 repodata
-rw-rw-r–. 1 59999 59999 1706 Jun 23 2012 RPM-GPG-KEY-CentOS-6
-rw-rw-r–. 1 59999 59999 1730 Jun 23 2012 RPM-GPG-KEY-CentOS-Debug-6
-rw-rw-r–. 1 59999 59999 1730 Jun 23 2012 RPM-GPG-KEY-CentOS-Security-6
-rw-rw-r–. 1 59999 59999 1734 Jun 23 2012 RPM-GPG-KEY-CentOS-Testing-6
-rw-rw-r–. 1 59999 59999 398 Jul 6 2012 .treeinfo

san2:/srv/md128/repositories/centos # ll ./6.3/os/x86_64/images/
total 168904
-rw-r–r–. 1 59999 59999 372736 Jul 6 2012 efiboot.img
-rw-r–r–. 1 59999 59999 35997696 Jul 6 2012 efidisk.img
-rw-r–r–. 1 59999 59999 136585216 Jul 6 2012 install.img
drwxr-xr-x. 2 59999 59999 37 Jul 6 2012 pxeboot

san2:/srv/md128/repositories/centos # ll ./6.3/os/x86_64/images/pxeboot/
total 34756
-rw-r–r–. 1 59999 59999 31596586 Jul 6 2012 initrd.img
-rwxr-xr-x. 1 59999 59999 3986608 Jul 6 2012 vmlinuz[/code]

[code]san2:/srv/md128/repositories/centos # ll …/oracle/6.3/os/x86_64/
total 504
drwxr-xr-x 3 root root 33 Feb 8 18:09 EFI
-rw-r–r-- 1 root root 7041 Feb 8 18:09 EULA
-rw-r–r-- 1 root root 7041 Feb 8 18:09 eula.en_US
-rw-r–r-- 1 root root 3334 Feb 8 18:09 eula.py
-rw-r–r-- 1 root root 18390 Feb 8 18:09 GPL
drwxr-xr-x 3 root root 66 Feb 8 18:09 HighAvailability
drwxr-xr-x 3 root root 103 Feb 8 18:09 images
drwxr-xr-x 2 root root 4096 Feb 8 18:09 isolinux
drwxr-xr-x 3 root root 66 Feb 8 18:09 LoadBalancer
-rw-r–r-- 1 root root 196 Feb 8 18:09 media.repo
drwxr-xr-x 2 root root 188416 Feb 8 18:10 Packages
-rw-r–r-- 1 root root 2619 Feb 8 18:10 README-en
-rw-r–r-- 1 root root 7054 Feb 8 18:10 README-en.html
-rw-r–r-- 1 root root 29531 Feb 8 18:10 RELEASE-NOTES-en
-rw-r–r-- 1 root root 32428 Feb 8 18:10 RELEASE-NOTES-en.html
-rw-r–r-- 1 root root 29531 Feb 8 18:10 RELEASE-NOTES-x86_64-en
-rw-r–r-- 1 root root 32428 Feb 8 18:10 RELEASE-NOTES-x86_64-en.html
-rw-r–r-- 1 root root 29531 Feb 8 18:10 RELEASE-NOTES-x86-en
-rw-r–r-- 1 root root 32428 Feb 8 18:10 RELEASE-NOTES-x86-en.html
lrwxrwxrwx 1 root root 15 Feb 8 18:10 repodata → Server/repodata
drwxr-xr-x 3 root root 66 Feb 8 18:10 ResilientStorage
-rw-r–r-- 1 root root 1011 Feb 8 18:10 RPM-GPG-KEY
-rw-r–r-- 1 root root 1011 Feb 8 18:10 RPM-GPG-KEY-oracle
drwxr-xr-x 3 root root 66 Feb 8 18:10 ScalableFileSystem
drwxr-xr-x 4 root root 87 Feb 8 18:10 Server
-rw-r–r-- 1 root root 108 Feb 8 18:10 supportinfo
-r–r–r-- 1 root root 6517 Feb 8 18:10 TRANS.TBL
drwxr-xr-x 3 root root 66 Feb 8 18:10 UEK2

san2:/srv/md128/repositories/centos # ll …/oracle/6.3/os/x86_64/images/
total 167692
-rw-r–r-- 1 root root 376832 Feb 8 18:09 efiboot.img
-rw-r–r-- 1 root root 34924544 Feb 8 18:09 efidisk.img
-rw-r–r-- 1 root root 136404992 Feb 8 18:09 install.img
drwxr-xr-x 2 root root 53 Feb 8 18:09 pxeboot
-rw-r–r-- 1 root root 541 Feb 8 18:09 README
-r–r–r-- 1 root root 1106 Feb 8 18:09 TRANS.TBL

san2:/srv/md128/repositories/centos # ll …/oracle/6.3/os/x86_64/images/pxeboot/
total 33668
-rw-r–r-- 1 root root 30481341 Feb 8 18:09 initrd.img
-r–r–r-- 1 root root 441 Feb 8 18:09 TRANS.TBL
-rwxr-xr-x 1 root root 3986992 Feb 8 18:09 vmlinuz[/code]

…and then I used the CentOS 6.3 .treeinfo file verbatim to guide virt-install through the process of creating an Oracle 6.3 PV: :slight_smile:

san2:/srv/md128/repositories # cp ./centos/6.3/os/x86_64/.treeinfo ./oracle/6.3/os/x86_64/

Problem solved! :smiley:

Eric Pretorious
Truckee, CA

4

Someone else has pointed out that the OL 6.3 ISO does contain a .treeinfo file. (They are correct. Somehow, the .itreeinfo file was deleted from the repository that I was using.)

[CODE]san2:/srv/md128/repositories # cat /mnt/.treeinfo
[general]
family = Oracle Linux Server
timestamp = 1340764248.23
variant = Server
totaldiscs = 1
version = 6.3
discnum = 1
packagedir = Packages
variants = Server
arch = x86_64

[images-x86_64]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img

[images-xen]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img

[stage2]
mainimage = images/install.img

[variant-Server]
addons = ResilientStorage,HighAvailability,ScalableFileSystem,LoadBalancer
repository = Server/repodata
identity = Server/Server.cert

[addon-ResilientStorage]
repository = ResilientStorage
name = Resilient Storage
identity = ResilientStorage/ResilientStorage.cert

[addon-HighAvailability]
repository = HighAvailability
name = High Availability
identity = HighAvailability/HighAvailability.cert

[addon-ScalableFileSystem]
repository = ScalableFileSystem
name = Scalable Filesystem Support
identity = ScalableFileSystem/ScalableFileSystem.cert

[addon-LoadBalancer]
repository = LoadBalancer
name = Load Balancer
identity = LoadBalancer/LoadBalancer.cert

[checksums]
images/install.img = sha256:c6f84bc868e82c07120c336cede9b01aa4a864ec6ccab782fc24a84683129703
images/pxeboot/vmlinuz = sha256:d2e268237355e41b3a681ace31ece1b68803b820bb199f1480f23b11010639f3
images/pxeboot/initrd.img = sha256:ac7a33c8c9b4b7024a198bd46be9be2e36b140c75d55f981000ba462c9b7f4e1
images/efiboot.img = sha256:7f6ae7f0b8fed11c5f26c9f836f51e532afa2b8af8986d9c98c9be2c981f0672
images/efidisk.img = sha256:a887c209392c6a453002a52e91b07b63a2c27c3d2be4fa46f1f3d92b425db993[/CODE]

However, when I use the .treeinfo file included in the ISO by Oracle (above), virt-install complains…

xen2:~ # virt-install -p --name oracle3 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e325f310000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --debug Thu, 14 Feb 2013 17:00:10 DEBUG Launched with command line: /usr/bin/virt-install -p --name oracle3 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e325f310000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --debug Thu, 14 Feb 2013 17:00:10 DEBUG Requesting libvirt URI default Thu, 14 Feb 2013 17:00:13 DEBUG Received libvirt URI xen:/// Thu, 14 Feb 2013 17:00:13 DEBUG Requesting virt method 'xen', hv type 'default'. Thu, 14 Feb 2013 17:00:13 DEBUG Received virt method 'xen' Thu, 14 Feb 2013 17:00:13 DEBUG Hypervisor name is 'xen' Thu, 14 Feb 2013 17:00:13 DEBUG DISPLAY is not set: defaulting to nographics. Thu, 14 Feb 2013 17:00:13 DEBUG --graphics compat generated: none Thu, 14 Feb 2013 17:00:13 DEBUG DistroInstaller location is a network source. Thu, 14 Feb 2013 17:00:13 DEBUG Preparing mount at /var/tmp/virtinstmnt._8jiS6 Thu, 14 Feb 2013 17:00:13 DEBUG Attempting to detect distro: Thu, 14 Feb 2013 17:00:13 DEBUG Fetching URI: /var/tmp/virtinstmnt._8jiS6/.treeinfo Thu, 14 Feb 2013 17:00:13 DEBUG Saved file to /var/tmp/virtinst-.treeinfo._jiClZ Thu, 14 Feb 2013 17:00:13 DEBUG Cleaning up mount at /var/tmp/virtinstmnt._8jiS6 Thu, 14 Feb 2013 17:00:13 ERROR No option 'boot.iso' in section: 'images-x86_64' Thu, 14 Feb 2013 17:00:13 DEBUG Traceback (most recent call last): File "/usr/bin/virt-install", line 1008, in <module> sys.exit(main()) File "/usr/bin/virt-install", line 993, in main guest = build_guest_instance(conn, options) File "/usr/bin/virt-install", line 530, in build_guest_instance get_install_media(guest, options.location, options.cdrom, need_install) File "/usr/bin/virt-install", line 304, in get_install_media validate_install_media(guest, location, cdpath, cdinstall) File "/usr/bin/virt-install", line 341, in validate_install_media guest.installer.check_location() File "/usr/lib64/python2.6/site-packages/virtinst/DistroInstaller.py", line 440, in check_location OSDistro.detectMediaDistro(location=self.location, arch=self.arch) File "/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py", line 185, in detectMediaDistro _type, arch, media_cb) File "/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py", line 131, in _locationCheckWrapper arch=arch) File "/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py", line 68, in _storeForDistro arch, typ, scratchdir) File "/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py", line 224, in distroFromTreeinfo ob.isValidStore(fetcher, progresscb) File "/usr/lib64/python2.6/site-packages/virtinst/OSDistro.py", line 426, in isValidStore self._valid_iso_path = self.treeinfo.get(isoSection, "boot.iso") File "/usr/lib64/python2.6/ConfigParser.py", line 540, in get raise NoOptionError(option, section) NoOptionError: No option 'boot.iso' in section: 'images-x86_64'

I’m not sure what to make of this error, though.

Thoughts? Suggestions? :confused:

5

[QUOTE=epretorious;11886]Someone else has pointed out that the OL 6.3 ISO does contain a .treeinfo file. (They are correct. Somehow, the .itreeinfo file was deleted from the repository that I was using.)… However, when I use the .treeinfo file included in the ISO by Oracle (above), virt-install complains…

xen2:~ # virt-install -p --name oracle3 --ram 786 --disk /dev/disk/by-id/scsi-14945540000000000705f69534353492d73616e325f310000 --location nfs://192.168.0.2/srv/md128/repositories/oracle/6.3/os/x86_64/ --debug ... NoOptionError: No option 'boot.iso' in section: 'images-x86_64'[/QUOTE]

Comparing the two .treeinfo files, I can see the difference: The CentOS 6.3 .treeinfo file contains a line that references “boot.iso”:

[CODE]san2:/srv/md128/repositories # cat centos/6.3/os/x86_64/.treeinfo
[general]
family = CentOS
timestamp = 1341569485.3
variant =
totaldiscs = 1
version = 6.3
discnum = 1
packagedir =
arch = x86_64

[images-x86_64]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img
boot.iso = …/…/isos/x86_64/CentOS-6.3-x86_64-netinstall.iso
[images-xen]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img

[stage2]
mainimage = images/install.img[/CODE]

If I add that exact same line to the Oracle Linux 6.3 .treeinfo file, the installation completes successfully (just as when I used the unmodified CentOS 6.3 .treeinfo).

Thoughts, anyone? :confused:

6

Hi epretorious,

Thoughts, anyone? :confused:

Yes - if it works: great! And thank your for reporting back :slight_smile:

7

[QUOTE=jmozdzen;11968]Hi epretorious,

Thoughts, anyone? :confused:

Yes - if it works: great! And thank your for reporting back :)[/QUOTE]

Thanks, J:

I meant analytical thinking – Something that might explain why this is happening. :rolleyes:

Eric Pretorious
Truckee, CA

8

Hi Eric,

it sounds as if you didn’t catch my humor, I’m sorry for that and didn’t want to offend you. Your analysis already seemed to sum up to “there’s a line missing in the Oracle version of the file”, my reaction to it was “hey great: he found out what was wrong and fixed it!”. And I especially wanted to thank you for sharing the result, as others facing the same problem now will have a chance of profiting from it.

Something that might explain why this is happening. :rolleyes:

As you most likely have seen in the output posted by you, there’s an error message

ERROR    No option 'boot.iso' in section: 'images-x86_64'

Sounds to me like the loader doesn’t take kernel &initrd from that section, but rather requires a bootable ISO. (And don’t ask me why - I simply don’t know. I’ve been digging through that python code several times chasing other bugs, but not that specific area.)

Regards,
Jens

9

No offense taken, Jens. I was just being grumpy. :stuck_out_tongue:

[QUOTE=jmozdzen;12143]As you most likely have seen in the output posted by you, there’s an error message

ERROR    No option 'boot.iso' in section: 'images-x86_64'

Sounds to me like the loader doesn’t take kernel &initrd from that section, but rather requires a bootable ISO. (And don’t ask me why - I simply don’t know. I’ve been digging through that python code several times chasing other bugs, but not that specific area.)[/QUOTE]
Yeah, I wasn’t very clear about my intent there:

What I was trying to convey was that:

[LIST]
[][COLOR=“#FF0000”]the boot.iso option is required but the actual contents of the boot.iso option are completely discarded[/COLOR], and
[]this might qualify as a bug but I wanted confirmation of that and maybe some guidance on how/whether to address the potential bug.[/LIST]
What do you recommend, Jens. Should I submit a bug report? If so, how do I go about submitting a bug report?

Eric Pretorious
Truckee, CA

10

Hi Eric,

[QUOTE=epretorious;12147]No offense taken, Jens. I was just being grumpy. :stuck_out_tongue:

Yeah, I wasn’t very clear about my intent there:

What I was trying to convey was that:

[LIST]
[][COLOR=#FF0000]the boot.iso option is required but the actual contents of the boot.iso option are completely discarded[/COLOR], and
[]this might qualify as a bug but I wanted confirmation of that and maybe some guidance on how/whether to address the potential bug.
[/LIST]
What do you recommend, Jens. Should I submit a bug report? If so, how do I go about submitting a bug report?

Eric Pretorious
Truckee, CA[/QUOTE]

I found the following comment in /usr/lib64/python/site-packages/virtinst/DistroInstaller.py:

# Xen needs a boot.iso if its a http://, ftp://, or nfs: url

So I doubt this is a bug, but rather by design/implementation. And are you sure it is not actually used? I’d assume that it is used, to create a run-time environment for the installer. But others with more in-depth knowledge would have to comment on this. AFAICT, this code is actually very distro-specific (concerning the distro to be installed) and most probably the included version has not yet created the code to support Oracle’s “distro” yet.

virt-install is part of the virt-manager stuff from http://virt-manager.org, maybe their mailing list can help to check for the current upstream support status. If newer upstream code supports Oracle VMs, it might be helpful to file a bug to let SuSE know about this issue and probably include an update in a later SP or fix.

Regards,
Jens