|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [HOWTO] Setting up Xen4 + pvops 2.6.32.21.x on CentOS 5.
Pradeep, Yours "Howto" worked for me in some unexpected way. There is well known issue with failure OSOL 134 ( Indiana in meantime) DHCPREQUEST success on system with pvops kernel mostly have all xen backend drivers hard linked to the kernel. At the same time same OSOL 134 behaves fine on OpenSuse 11.3 , loading xen-backend drivers via xend at every boot up. I just decided try to load as module xen-netback on systems with pvops kernel ( on top of F13,Ubuntu 10.04.1 Server) and got positive results. The final conclusion is :- for OSOL 134 (OI 147) xen-netback driver should be loaded as module, otherwise in 90% off attempts DHCP request for Solaris DomU will fail right away.
Boris.
--- On Mon, 10/4/10, Pradeep Padala <ppadala@xxxxxxxxxxxxxxxxxx>
wrote:
From: Pradeep Padala <ppadala@xxxxxxxxxxxxxxxxxx> Subject: RE: [Xen-devel] [HOWTO] Setting up Xen4 + pvops 2.6.32.21.x on CentOS 5.5 To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, "Pasi Kärkkäinen" <pasik@xxxxxx> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx Date: Monday, October 4, 2010, 12:59 PM
Hi Boris, Thanks for the comments. I will update the HOWTO with the right config. You can either compile it as a module or in the kernel. Pradeep From: Boris Derzhavets [mailto:bderzhavets@xxxxxxxxx] Sent: Monday, October 04, 2010 5:01 AM To: Pradeep Padala; Pasi Kärkkäinen Cc: xen-devel@xxxxxxxxxxxxxxxxxxx Subject: Re: [Xen-devel] [HOWTO] Setting up Xen4 + pvops 2.6.32.21.x on CentOS
5.5 If i will follow :-
http://ppadala.net/blog/2010/09/how-to-setup-xen4-and-pvops-2-6-32-x-on-centos-5-5-using-gitco-repository/
Recommended .config (fragment)
CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y
I believe in this case modules :- xen-evtchn xen-netback xen-blkback xenfs won't be created because they are hard linked to kernel.
To get them as modules i need
:-
CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_XEN_NETDEV_BACKEND=m CONFIG_XENFS=m
At least on my system (F14) with .config Fragment from .config # CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=m CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y # [root@fedora14 2.6.32.23]# pwd /lib/modules/2.6.32.23 [root@fedora14 2.6.32.23]# find . -name "xen-*back.ko" -print ./kernel/drivers/xen/netback/xen-netback.ko [root@fedora14 2.6.32.23]# find . -name "xen-evtchn.ko" -print
Module xen-netback.ko has been created only due to :- CONFIG_XEN_NETDEV_BACKEND=m
May be i am missing something here ?
Boris. P.S. I just need xen-netback to be loaded as module for OpenIndiana 147 PV Guest stable networking with PVOPS kernel ( OSOL 134 aswell). In
other words i need to configure PVOPS kernel like XenLinux kernel in regards of loading xen backend drivers.
--- On Sun, 10/3/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote: From: Pasi Kärkkäinen <pasik@xxxxxx> Subject: Re: [Xen-devel] [HOWTO] Setting up Xen4 + pvops 2.6.32.21.x on CentOS 5.5 To: "Pradeep Padala" <ppadala@xxxxxxxxxxxxxxxxxx> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx Date: Sunday, October 3, 2010, 3:34 PM
|
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|