[ovs-dev] ovs-vsctl for sFlow config
Neil McKee
neil.mckee at inmon.com
Wed May 12 23:35:43 UTC 2010
OK. I'm going to assume that I started with the wrong VM.
Neil
On May 7, 2010, at 3:17 PM, Ben Pfaff wrote:
> On Fri, May 07, 2010 at 11:42:54AM -0700, Neil McKee wrote:
>>
>> On May 7, 2010, at 9:30 AM, Ben Pfaff wrote:
>>
>>> On Thu, May 06, 2010 at 04:57:40PM -0700, Neil McKee wrote:
>>>> I followed these steps to compile the openvswitch rpm on xenserver 5.5 update2 DDK, and run it on xenserver 5.5 update2:
>>>>
>>>> http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=INSTALL.XenServer;hb=HEAD
>>>>
>>>> It mostly worked as advertised, except that missing from these
>>>> instructions is a step where you have to install the kernel-src rpm
>>>> from the DDK sources download, copy in the xen .config file that comes
>>>> with it, compile the kernel with "make" and ensure that
>>>> /lib/modules/<kernel>/build points to that source directory.
>>>
>>> That's very odd. We compile the RPM from the Xen DDK, using the steps
>>> listed there all the time (often several times a day in our internal
>>> autobuilder), and we do not make any changes to the DDK. We certainly
>>> do not rebuild the kernel-src RPM (I would have to go off searching to
>>> find it). And we have probably a dozen different variants on the Xen
>>> DDK VM that we use this way.
>>>
>>> So I think that something probably went wrong with your Xen DDK VM. It
>>> shouldn't be that hard.
>>>
>>
>> So in your DDK VM the /lib/modules/`uname -r`/build link is present
>> and points to some kernel sources?
>
> Yes. For example, in the one I have here,
> /lib/modules/2.6.27.42-0.1.1.xs5.6.0.41.111155xen/build is a symlink to
> /usr/src/kernels/2.6.27.42-0.1.1.xs5.6.0.41.111155xen-i686, which
> contains enough headers and other files that I can use
> --with-l26=/lib/modules/2.6.27.42-0.1.1.xs5.6.0.41.111155xen/build to
> configure a kernel to build against the corresponding Xen kernel.
>
>> The openvswitch configure script seems to nose around there to check
>> some things. Or maybe you copy the tarball across *after* you have
>> run the configure script?
>
> No, the configure script runs inside the DDK. We run "make dist"
> outside the DDK, copy the OVS .tar.gz into the DDK, run configure
> and make inside the DDK (we actually let the RPM spec file do that, of
> course), and copy out the generated RPM.
>
>> I was just taking what I got from "make dist". We're using xenserver
>> update 2 instead of update 1, so perhaps there is a difference there
>> too. The kernel version is 2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.
>
> I doubt there would be a difference--I have 20 DDKs from 5.0.0 up to
> alphas and RCs for 5.6 here and they all work the same way for me.
>
>> I did get some warnings during the openvswitch compilation:
>>
>> Building modules, stage 2.
>> MODPOST
>> [...]
>
> I just checked the build logs for warnings like those, and I don't have
> any. I think that we must be doing different things here. (If we
> figure out what, then I'll document it in INSTALL.XenServer.)
More information about the dev
mailing list