On Wed, Sep 01, 2010 at 01:42:01PM -0500, W. Michael Petullo wrote:
I have been investigating the use of Xen with a Fedora 14
(devel)-based
Dom0. Until now, I have always used Michael Young's Dom0 kernels.
The first thing I did was try to build the current Fedora 14 kernel with
Xen Dom0 support. I began porting Michael's RPM specification to the
Fedora 14 specification. What I found was that the Xen pvops work seems
to be targeting 2.6.32 and possibly 2.6.36. As a result, I was unable
to find a straightforward way to create a patch for 2.6.35.4. Am I
missing something here? Is building a 2.6.35.4-based kernel difficult
in this way?
Next, I tried to use Michael's latest Fedora 12 kernel on Fedora
14. Of course, Fedora 14 uses some features that are not available
in this kernel. Most notably, I had to provide the kernel with the
"init=/sbin/upstart" option to avoid the use of systemd.
Once I booted the system, I found that xend would not start because it did
not find what it expected in /sys/bus/pci/devices/0000\:00\:03.2/config:
[...]
File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 1050, in
detect_dev_info
pos = self.find_cap_offset(PCI_CAP_ID_EXP)
File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 933, in
find_cap_offset
id = ord(os.read(fd, 1))
TypeError: ord() expected a character, but string of length 0 found
I "fixed" this by editing pci.py and changing:
id = ord(os.read(fd, 1))
to:
try:
id = ord(os.read(fd, 1))
except:
pos = 0
break;
Of course, this might not be a good fix, but it was quick and it allowed
me to continue and experiment. Does anyone know what is going on here?
Thanks for the info and the fix!
At this point, I was able to boot a DomU image, although I need to do
a
lot more testing. Has anyone else experimented with Fedora 14? What is
your experience? I am especially interested in hearing about Fedora 14
Dom0 kernels.
I haven't tried F14 yet.. but I should soon..
-- Pasi