Re: [Fedora-xen] Xen Dom0 and Fedora 14
/usr/lib64/python2.7/site-packages/xen/util/pci.py stays untouched Dmesg log attached [r...@fedora14 ~]# xm info Traceback (most recent call last): File "/usr/sbin/xm", line 5, in from xen.xm import main File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 41, in from xen.util.pci import * File "/usr/lib64/python2.7/site-packages/xen/util/pci.py", line 937 pos = 0 ^ IndentationError: expected an indented block Convert /usr/lib64/python2.7/site-packages/xen/util/pci.py back as it was [r...@fedora14 ~]# vi /usr/lib64/python2.7/site-packages/xen/util/pci.py [r...@fedora14 ~]# service xend start Starting xend daemon: [ OK ] [r...@fedora14 ~]# service xenconsoled start Starting xenconsoled daemon: [ OK ] [r...@fedora14 ~]# xm info host : fedora14 release : 2.6.32.19-xen version : #4 SMP Fri Sep 3 22:10:56 MSD 2010 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2833 hw_caps : bfebfbff:20100800::0940:0408e3fd::0001: virt_caps : hvm total_memory : 8190 free_memory : 1671 node_to_cpu : node0:0-3 node_to_memory : node0:1671 node_to_dma32_mem : node0:841 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0x8000 xen_changeset : unavailable xen_commandline : cc_compiler : gcc version 4.5.1 20100812 (Red Hat 4.5.1-1) (GCC) cc_compile_by : root cc_compile_domain : cc_compile_date : Fri Sep 3 21:16:54 MSD 2010 xend_config_format : 4 Boris. --- On Wed, 9/1/10, W. Michael Petullo wrote: From: W. Michael Petullo Subject: [Fedora-xen] Xen Dom0 and Fedora 14 To: xen@lists.fedoraproject.org Date: Wednesday, September 1, 2010, 2:42 PM 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/\: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? 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. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen dmesgXen401@F14.log.gz Description: GNU Zip compressed data -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Dom0 and Fedora 14
>> 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. > Yes, now that I try it I get the error > failed to mount /sys/fs/cgroup: No such file or directory > It looks like this /sys mount was introduced in 2.6.33. Luckily, I was already familiar with this issue, see also: https://bugzilla.redhat.com/show_bug.cgi?id=628004 -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Dom0 and Fedora 14
On Wed, 1 Sep 2010, W. Michael Petullo wrote: > 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. Yes, that is one reason why I am still tracking Fedora 12, as it is considerably easier than the other options. The other reason is it is (up until now at least) where the main development is. When development shifts to 2.6.36 (which is the current plan) I will probably start building rawhide kernels. > 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. Yes, now that I try it I get the error failed to mount /sys/fs/cgroup: No such file or directory It looks like this /sys mount was introduced in 2.6.33. > 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/\: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 don't see that - though it may depend on your hardware or which xen version you are using. xend works for me, though one of my keyboards doesn't work, it seems due to some apparently IRQ related problem. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Dom0 and Fedora 14
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/\: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 -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Dom0 and Fedora 14
What is udev version on F14 ? Boris. --- On Wed, 9/1/10, W. Michael Petullo wrote: From: W. Michael Petullo Subject: [Fedora-xen] Xen Dom0 and Fedora 14 To: xen@lists.fedoraproject.org Date: Wednesday, September 1, 2010, 2:42 PM 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/\: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? 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. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Xen Dom0 and Fedora 14
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/\: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? 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. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
