| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
 Re: [Xen-users] Centos 6.0 guest OS missing xen headers
 Hi Fajar,
 
 
       Its XenServer 6.0, which comes with kernel "2.6.32.12-0.7.1.xs6.0.0.529.170661xen". 
 Regards, Ravi 
On Tue, Nov 29, 2011 at 12:56 PM, Fajar A. Nugraha <list@xxxxxxxxx>  wrote: 
There's no such thing as Xen 6.0.On Tue, Nov 29, 2011 at 1:39 PM, ravi veerad <veerad.ravi@xxxxxxxxx > wrote: 
> Hi, 
> setup environment: 
> Xen version: Xen 6.0
There's Xen 4.x, or XenServer 6.0
 
 I think these aren't caused by missing headers. Rather, your module> DomU: Centos 6.0
 > Solarflare drivers: sfc, sfc_resource, sfc_netback, sfc_netfront,
 > sfc_netutil (these drivers came with xen 5.6.)
 > My task is to port old sfc driver (xen 5.6) to new xen 6.0 and centos (guest
 > OS) environment. I am successfully able to port sfc, sfc_resource,
 > sfc_netback, sfc_netutil on DOM0 side. Now, when I try to compile
 > sfc_netfront and sfc_netutil on the DOMU side (centos 6.0), I am facing the
 > following compilation errors:
 > /sfc_netfront/accel_xenbus.c: In function ‘vnic_setup_domU_shared_state’:
 > /sfc_netfront/accel_xenbus.c:363: error: implicit declaration of function
 > ‘bind_listening_port_to_irqhandler’
 > /sfc_netfront/accel_xenbus.c:370: error: implicit declaration of function
 > ‘irq_to_evtchn_port’
 > make[2]: *** [/root/sfc_phase_4/sfc_netfront/accel_xenbus.o] Error 1
 > make[1]: *** [_module_/root/sfc_phase_4/sfc_netfront] Error 2
 > make[1]: Leaving directory `/usr/src/kernels/2.6.32-71.29.1.el6.i686'
 > make: *** [all] Error 2
 >     I noticed that in centos 6.0 (2.6.32-71.29.1.el6.i686)  doesn't contain
 > the xen headers, And also there are some
 > missing symbol in Module.symvers,  (bind_listening_port_to_irqhandler,
 >   irq_to_evtchn_port)  which we required to compile our module.
 
 
uses old kernel ABI not supported anymore in 2.6.32, or it requires
 xen-specific symbols not present in vanilla/Centos version of 2.6.32
 (which can be used as xen domU kernel, but not dom0)
 
 Your best bet at this point is to either:
 - get newer drivers from solarflare, or
 - use it as normal NIC on dom0, use bridging to share network
 connection with domU, or
 - use whatever kernel version your dom0 use (2.6.32 from JF's tree,
 perhaps?) and compile it manually for domU, replacing Centos' kernel
 RPM.
 
 --
 Fajar
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users 
 |