Red Hat Bugzilla – Bug 437595
Cannot create xen rawhide instance
Last modified: 2008-05-21 12:45:45 EDT
Description of problem:
Cannot create and install install xen rawhide instance. Installing Fedora 8
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. use virt-manager gui
2. setup http install pointing at rawhide tree
3. doesn't work
Name : Fedora development i386 (20080314)
Arch : i386
Id : 1205481897.08
Version : development
Family : Fedora
Time : 2008-03-14 01:04 PDT
Images : i386 (kernel, family, timestamp, variant, boot.iso, initrd,
version, arch), xen (kernel, family, timestamp, variant, initrd, version, arch)
Unable to complete install 'exceptions.ValueError Could not find an installable
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 611, in do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 811, in
File "/usr/lib/python2.4/site-packages/virtinst/ParaVirtGuest.py", line 56, in
self._installer.prepare(guest = self, meter = meter)
File "/usr/lib/python2.4/site-packages/virtinst/DistroManager.py", line 239,
self._prepare_kernel_and_initrd(guest, distro, meter)
File "/usr/lib/python2.4/site-packages/virtinst/DistroManager.py", line 209,
distro = distro)
File "/usr/lib/python2.4/site-packages/virtinst/DistroManager.py", line 122,
progresscb=progresscb, distro=distro, scratchdir=scratchdir)
File "/usr/lib/python2.4/site-packages/virtinst/DistroManager.py", line 101,
raise ValueError, _("Could not find an installable distribution at '%s'" %
ValueError: Could not find an installable distribution at
reassigning to virt-manager for now...
Could it be that the rawhide tree itself is malformed or necessary files are
missing? I believe there have been other problems like this.
More info: I'm running RHEL5.2 beta Dom0 and trying to install a xen rawhide
instance (failure described above). Attempting an F8 (gold) xen install works fine.
Here is a listing of the RHEL5.2 packages for Dom0 (if that is applicable):
$ rpm -qa | egrep 'virt|xen' | sort
Probably virt-manager is looking for a "Fedora" directory, but it was renamed
to "Packages", like on bug #273781.
This is the same as F8 bug 437217
Removing F9 blocker bug, since this is a RHEL 5.2 bug, not a Fedora bug.
Created attachment 298266 [details]
Correctly detect rawhide/f9 distro trees
Fixes distro detection for f9. Verified this doesn't affect installing f7 or f8
guests from a tree.
This is a simple fix to enable installing rawhide and f9 guests, which if we
don't fix now we will definitely see a flood of bzs about later. I'm requesting
this as an exception for inclusion in 5.2.
Set dev ack for Cole.
For further clarification, our package probes an install tree to try and verify
what distro it is, so we know where to look for virt install media. We do this
detection by looking for certain files (for fedora, we would use fedora.css).
Rawhide and eventually f9 no longer carry this fedora.css file, so detection and
installs were failing.
This patch just changes this check to also pass if we find a file .treeinfo,
which is intended to be present in all fedora trees for detections of this type
(so i've been told). The check will fall back to fedora.css if it can't find
treeinfo, so there should be no backwards compatibility issues (I verified this
for f7 and f8).
For these reasons it is low risk, and any remaining risk would be offset by the
amount of time this would save us in future support. Not to mention it would
look bad if this went out the door without being able to create a rawhide guest :)
Restore flags cleared by mistake.
Fix built in python-virtinst-0.300.2-7.el5:
Build Tag Built by
---------------------------------------- -------------------- ----------------
python-virtinst-0.300.2-7.el5 dist-5E-qu-candidate crobinso
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.