dom0 kernel

[M A Young]

Another dom0 kernel is available at 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2071068 or from the 
repository http://fedorapeople.org/~myoung/dom0/ . This kernel requires 
xen 3.4.3 or xen 4.0.0 and a source rpm for xen-4.0.0-rc7 is at 
http://fedorapeople.org/~myoung/dom0/src/xen-4.0.0-0.5.rc7.fc12.src.rpm

This kernel is the first that boots for me on i686 for a long time. It 
also switches from initrd to initramfs boot partitions which should make 
it easier to use on Fedora 13.

 	Michael Young

[M A Young]

Another dom0 kernel is available at 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2107643 or from the
>  repository http://fedorapeople.org/~myoung/dom0/ . It requires xen
> 3.4.3  
(rc) or 4.0.0 eg. built from the source RPM 
http://fedorapeople.org/~myoung/dom0/src/xen-4.0.0-0.7.fc12.src.rpm

This has STACKPROTECTOR turned back on, the xen includes in 
kernel-devel that some of you requested, and I think PAT code has been 
added to the pvops source since the last kernel I announced.

 	Michael Young

[M A Young]

I have done another update (kernel-2.6.32.12-1.2.103.xendom0.fc12) which 
is available from 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2169712 or the 
repository http://fedorapeople.org/~myoung/dom0/
You need xen-3.4.3 or xen-4.0.0 to use this kernel (it did boot for me 
with the standard F13 3.4.2 package on one machine, but the networking 
didn't work, possibly other things as well as I didn't test it much).

 	Michael Young

dom0 kernel and xen hypervisor

[M A Young]

I have built a new dom0 kernel (kernel-2.6.32.14-1.2.105.xendom0.fc12) 
which is available from 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the 
repository http://fedorapeople.org/~myoung/dom0/

There are now some xen 3.4.3 builds you can test this with available from 
koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If 
there are no problems with them I will start the process to push them out 
to F-12 and F-13 proper in a few days time. Rawhide should get the new 
rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.

 	Michael Young

dom0 kernel and xen hypervisor

[itamar]

On Tue, Jun 1, 2010 at 6:26 PM, M A Young <m.a.young(a)durham.ac.uk&gt; wrote:
>  I have built a new dom0 kernel
> (kernel-2.6.32.14-1.2.105.xendom0.fc12)
>  which is available from
>  http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the
>  repository http://fedorapeople.org/~myoung/dom0/
>
>  There are now some xen 3.4.3 builds you can test this with available from
>  koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If
>  there are no problems with them I will start the process to push them out
>  to F-12 and F-13 proper in a few days time. Rawhide should get the new
>  rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.
>
>         Michael Young
>  --
>  xen mailing list
>  xen(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/xen
>  
do you have commit access to xen rpm ?

I think redhat is more interested in KVM than xen




-- 
------------

Itamar Reis Peixoto

dom0 kernel and xen hypervisor

[Brian Lavender]

On Tue, Jun 01, 2010 at 07:07:35PM -0300, Itamar Reis Peixoto wrote:
>  On Tue, Jun 1, 2010 at 6:26 PM, M A Young
> <m.a.young(a)durham.ac.uk&gt; wrote:
>  > I have built a new dom0 kernel (kernel-2.6.32.14-1.2.105.xendom0.fc12)
>  > which is available from
>  > http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the
>  > repository http://fedorapeople.org/~myoung/dom0/
>  >
>  > There are now some xen 3.4.3 builds you can test this with available from
>  > koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If
>  > there are no problems with them I will start the process to push them out
>  > to F-12 and F-13 proper in a few days time. Rawhide should get the new
>  > rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.
>  >
>  >        Michael Young
>  > --
>  > xen mailing list
>  > xen(a)lists.fedoraproject.org
>  > https://admin.fedoraproject.org/mailman/listinfo/xen
>  >
>  
>  do you have commit access to xen rpm ?
>  
>  I think redhat is more interested in KVM than xen 
Screw Redhat. I am interested in Xen! Keep the Xen packaging coming!

-- 
Brian Lavender
http://www.brie.com/brian/

"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the other
way is to make it so complicated that there are no obvious deficiencies."

Professor C. A. R. Hoare
The 1980 Turing award lecture

dom0 kernel and xen hypervisor

[Virgil]

On Wed, 2 Jun 2010 07:26:26 am M A Young wrote:
>  I have built a new dom0 kernel
> (kernel-2.6.32.14-1.2.105.xendom0.fc12)
>  which is available from
>  http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the
>  repository http://fedorapeople.org/~myoung/dom0/
>  
>  There are now some xen 3.4.3 builds you can test this with available from
>  koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If
>  there are no problems with them I will start the process to push them out
>  to F-12 and F-13 proper in a few days time. Rawhide should get the new
>  rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.
>  
>   	Michael Young
>  --
>  xen mailing list
>  xen(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/xen 
Hi Michael,

Just yum updated the kernel (probably should have installed as it turns out). It fails to
do the initrd thing.
I've tried a force install to capture the error messages.

There was one other error message relating to plymouth not having a default.
I used `plymouth-set-default-theme text` to fix that.

My running test system probably won't reboot now I'm guessing, so I hope the power
doesn't go out :-)

[root@seanl64 tmp]# rpm -ivh --force kernel-2.6.32.14-1.2.105.xendom0.fc12.x86_64.rpm 
Preparing...                ########################################### [100%]
   1:kernel                 ########################################### [100%]
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libbz2.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libglib-2.0.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libply.so.2' -> `': No such file or directory
ln: creating symbolic link `libplybootsplash.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpng12.so.0' -> `': No such file or directory
ln: creating symbolic link `libm.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libz.so.1' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libply.so.2' -> `': No such file or directory
ln: creating symbolic link `libm.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libplybootsplash.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpng12.so.0' -> `': No such file or directory
ln: creating symbolic link `libply.so.2' -> `': No such file or directory
ln: creating symbolic link `libm.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libz.so.1' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libplybootsplash.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpng12.so.0' -> `': No such file or directory
ln: creating symbolic link `libply.so.2' -> `': No such file or directory
ln: creating symbolic link `libm.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libz.so.1' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
grep: /usr/share/plymouth/themes/.plymouth/.plymouth.plymouth: No such file or directory
The default plymouth plugin () doesn't exist
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpopt.so.0' -> `': No such file or directory
ln: creating symbolic link `libcryptsetup.so.1' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libuuid.so.1' -> `': No such file or directory
ln: creating symbolic link `libgcrypt.so.11' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libgpg-error.so.0' -> `': No such file or
directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libreadline.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `libreadline.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `libreadline.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `libgcc_s.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libreadline.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libreadline.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `libblkid.so.1' -> `': No such file or directory
ln: creating symbolic link `libuuid.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libblkid.so.1' -> `': No such file or directory
ln: creating symbolic link `libuuid.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpcre.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpopt.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `libreadline.so.6' -> `': No such file or directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libusb-0.1.so.4' -> `': No such file or directory
ln: creating symbolic link `libudev.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libblkid.so.1' -> `': No such file or directory
ln: creating symbolic link `libuuid.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `librt.so.1' -> `': No such file or directory
ln: creating symbolic link `libcap.so.2' -> `': No such file or directory
ln: creating symbolic link `libacl.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libpthread.so.0' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libattr.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libacl.so.1' -> `': No such file or directory
ln: creating symbolic link `libattr.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libacl.so.1' -> `': No such file or directory
ln: creating symbolic link `libattr.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `libpcre.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ldconfig: Cannot mmap file /lib64/libdmraid-events-isw.so.

ldconfig: Cannot mmap file /lib64/libnss_files.so.2.

/sbin/dracut: line 307: : No such file or directory
E: dracut: creation of  failed
mkinitrd failed
warning: %post(kernel-2.6.32.14-1.2.105.xendom0.fc12.x86_64) scriptlet failed, exit status
1


Cheers
Virgil.

dom0 kernel and xen hypervisor

[M A Young]

On Wed, 2 Jun 2010, Virgil wrote:

>  Just yum updated the kernel (probably should have installed as it
> turns out). It fails to do the initrd thing.
>  I've tried a force install to capture the error messages. 
yum should leave a few kernels (3 typically including the one you are 
running on) so you should be okay.

>  There was one other error message relating to plymouth not having a
> default.
>  I used `plymouth-set-default-theme text` to fix that.
>
>  My running test system probably won't reboot now I'm guessing, so I hope the
> power doesn't go out :-)
>
>  [root@seanl64 tmp]# rpm -ivh --force kernel-2.6.32.14-1.2.105.xendom0.fc12.x86_64.rpm
rpm -ivh should be safe as the existing kernels will still be there (rpm 
-q kernel will list them), you just need to make sure you pick one of the 
other options at the boot menu.

>  Preparing...               
> ########################################### [100%]
>    1:kernel                 ########################################### [100%]
>  ln: creating symbolic link `libc.so.6' -> `': No such file or directory
>  ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
> directory 
I am not sure about that - it looks like the initramfs build is failing. 
Are you short of free disk space (on /boot or more generally)?
It would also be useful to know what errors rpm gives if you don't use the 
--force option and what Fedora version you are using.

 	Michael Young

dom0 kernel and xen hypervisor

[Pasi Kärkkäinen]

On Tue, Jun 01, 2010 at 07:07:35PM -0300, Itamar Reis Peixoto wrote:
>  On Tue, Jun 1, 2010 at 6:26 PM, M A Young
> <m.a.young(a)durham.ac.uk&gt; wrote:
>  > I have built a new dom0 kernel (kernel-2.6.32.14-1.2.105.xendom0.fc12)
>  > which is available from
>  > http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the
>  > repository http://fedorapeople.org/~myoung/dom0/
>  >
>  > There are now some xen 3.4.3 builds you can test this with available from
>  > koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If
>  > there are no problems with them I will start the process to push them out
>  > to F-12 and F-13 proper in a few days time. Rawhide should get the new
>  > rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.
>  >
>  >        Michael Young
>  > --
>  > xen mailing list
>  > xen(a)lists.fedoraproject.org
>  > https://admin.fedoraproject.org/mailman/listinfo/xen
>  >
>  
>  do you have commit access to xen rpm ?
>   
Yep, Michael has, afaik.

-- Pasi

>  
>  
>  
>  -- 
>  ------------
>  
>  Itamar Reis Peixoto
>  --
>  xen mailing list
>  xen(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/xen

dom0 kernel and xen hypervisor

[Pasi Kärkkäinen]

On Tue, Jun 01, 2010 at 07:07:35PM -0300, Itamar Reis Peixoto wrote:
>  On Tue, Jun 1, 2010 at 6:26 PM, M A Young
> <m.a.young(a)durham.ac.uk&gt; wrote:
>  > I have built a new dom0 kernel (kernel-2.6.32.14-1.2.105.xendom0.fc12)
>  > which is available from
>  > http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the
>  > repository http://fedorapeople.org/~myoung/dom0/
>  >
>  > There are now some xen 3.4.3 builds you can test this with available from
>  > koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If
>  > there are no problems with them I will start the process to push them out
>  > to F-12 and F-13 proper in a few days time. Rawhide should get the new
>  > rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.
>  >
>  >        Michael Young
>  > --
>  > xen mailing list
>  > xen(a)lists.fedoraproject.org
>  > https://admin.fedoraproject.org/mailman/listinfo/xen
>  >
>  
>  do you have commit access to xen rpm ?
>   
> From Fedora rawhide changelog: 
xen-3.4.3-1.fc14
----------------
* Tue Jun 01 2010 Michael Young <m.a.young(a)durham.ac.uk&gt; - 3.4.3-1
- update to 3.4.3 release including
    support for latest pv_ops kernels (possibly incomplete)
    should fix build problems (#565063) and crashes (#545307)
- replace Prereq: with Requires: in spec file
- drop static libraries (#556101)


-- Pasi

dom0 kernel and xen hypervisor

[Pasi Kärkkäinen]

On Tue, Jun 01, 2010 at 10:26:26PM +0100, M A Young wrote:
>  I have built a new dom0 kernel
> (kernel-2.6.32.14-1.2.105.xendom0.fc12) 
>  which is available from 
>  http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the 
>  repository http://fedorapeople.org/~myoung/dom0/
>   
kernel-2.6.32.14-1.2.105.xendom0.fc12 works OK for me, with Xen 4.0.0, on Fedora 13.

-- Pasi

>  There are now some xen 3.4.3 builds you can test this with available
> from 
>  koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If 
>  there are no problems with them I will start the process to push them out 
>  to F-12 and F-13 proper in a few days time. Rawhide should get the new 
>  rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon.
>  
>   	Michael Young
>  --
>  xen mailing list
>  xen(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/xen

dom0 kernel and xen hypervisor

[M A Young]

On Thu, 3 Jun 2010, Pasi K?rkk?inen wrote:

>  On Tue, Jun 01, 2010 at 07:07:35PM -0300, Itamar Reis Peixoto wrote:
> > do you have commit access to xen rpm ?
> >
>
>  From Fedora rawhide changelog:
>
>  xen-3.4.3-1.fc14
>  ----------------
>  * Tue Jun 01 2010 Michael Young <m.a.young(a)durham.ac.uk&gt; - 3.4.3-1
>  - update to 3.4.3 release including
>     support for latest pv_ops kernels (possibly incomplete)
>     should fix build problems (#565063) and crashes (#545307)
>  - replace Prereq: with Requires: in spec file
>  - drop static libraries (#556101) 
The definitive answer is here 
https://admin.fedoraproject.org/pkgdb/acls/name/xen

 	Michael Young

dom0 kernel and xen hypervisor

[M A Young]

Here is another new kernel (kernel-2.6.32.14-1.2.107.xendom0.fc12) at 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2254110 or the 
repository http://fedorapeople.org/~myoung/dom0/

This needs xen with a patch to remove some old device creation code that 
doesn't work with the latest stable.2.6.32.x pvops kernels like this one. 
Possible options include xen-4.0.0-2 from rawhide, xen-3.4.3-2 from F-13 
or F-12 updates-testing (also available via 
http://koji.fedoraproject.org/koji/packageinfo?packageID=7 ) or a test 
build of xen 4.0.1 rc3 available from 
http://koji.fedoraproject.org/koji/taskinfo?taskID=2264056
Any build of xen 4.0.1 rc2 or later will also work.

 	Michael Young