<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">What is udev version on F14 ?<br><br>Boris.<br><br>--- On <b>Wed, 9/1/10, W. Michael Petullo <i><mike@flyn.org></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: W. Michael Petullo <mike@flyn.org><br>Subject: [Fedora-xen] Xen Dom0 and Fedora 14<br>To: xen@lists.fedoraproject.org<br>Date: Wednesday, September 1, 2010, 2:42 PM<br><br><div class="plainMail">I have been investigating the use of Xen with a Fedora 14 (devel)-based<br>Dom0. Until now, I have always used Michael Young's Dom0 kernels.<br><br>The first thing I did was try to build the current Fedora 14 kernel with<br>Xen Dom0 support. I began porting Michael's RPM specification to the<br>Fedora 14 specification. What I found was that the Xen pvops work seems<br>to be targeting 2.6.32 and possibly 2.6.36. As a result,
I was unable<br>to find a straightforward way to create a patch for 2.6.35.4. Am I<br>missing something here? Is building a 2.6.35.4-based kernel difficult<br>in this way?<br><br>Next, I tried to use Michael's latest Fedora 12 kernel on Fedora<br>14. Of course, Fedora 14 uses some features that are not available<br>in this kernel. Most notably, I had to provide the kernel with the<br>"init=/sbin/upstart" option to avoid the use of systemd.<br><br>Once I booted the system, I found that xend would not start because it did<br>not find what it expected in /sys/bus/pci/devices/0000\:00\:03.2/config:<br><br>[...]<br> File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 1050, in detect_dev_info<br> pos = self.find_cap_offset(PCI_CAP_ID_EXP)<br> File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 933, in find_cap_offset<br> id = ord(os.read(fd, 1))<br>TypeError: ord() expected a character, but string of
length 0 found<br><br>I "fixed" this by editing pci.py and changing:<br><br>id = ord(os.read(fd, 1))<br><br>to:<br><br>try:<br> id = ord(os.read(fd, 1))<br>except:<br> pos = 0<br> break;<br><br>Of course, this might not be a good fix, but it was quick and it allowed<br>me to continue and experiment. Does anyone know what is going on here?<br><br>At this point, I was able to boot a DomU image, although I need to do a<br>lot more testing. Has anyone else experimented with Fedora 14? What is<br>your experience? I am especially interested in hearing about Fedora 14<br>Dom0 kernels.<br><br>-- <br>Mike<br><br>:wq<br>--<br>xen mailing list<br><a ymailto="mailto:xen@lists.fedoraproject.org" href="/mc/compose?to=xen@lists.fedoraproject.org">xen@lists.fedoraproject.org</a><br><a href="https://admin.fedoraproject.org/mailman/listinfo/xen"
target="_blank">https://admin.fedoraproject.org/mailman/listinfo/xen</a><br></div></blockquote></td></tr></table><br>