RE: tools/vnet build issues and a patch to fix part

RE: tools/vnet build issues and a patch to fix part

[Ian Pratt]

> Being that driver domains/xend are partially broken for me I 
> thought I'd
> take a run at vnet to accomplish something close to what I desire.  Is
> anyone else out there running vnet?  If so, how stable have you found
> it?

You don't half like living on the bleeding edge ;-)

I'm not aware of anyone outside HP that uses vnets regularly, but
they're a cool thing that we want to maintain.

I suspect that the current breakage is because the code was written for
2.6.7, and there have been updates since. Syncing up probably isn't very
hard. Perhaps a volunteer will step forward....

Ian 
 
> My findings to date are as follows:
> 1) building of gc is broken (at least for me).  I needed the attached
> patch to get things working properly.
> 
> PATCH tools_vnet_Makefile.gc-6.3.patch - Signed off by:  bgb@nt-nv.com
> 
> 2)  The actual vnet-module driver is failing to build with 
> the following
> errors:
> ______________________________________________________________
> __________
> 
> In file included from vnetd.h:22,
>                  from vcache.c:39:
> ../vnet-module/if_varp.h:39: warning: declaration does not declare
> anything
> In file included from vcache.c:39:
> vnetd.h:40: warning: declaration does not declare anything
> vcache.c: In function `varp_send':
> vcache.c:105: error: structure has no member named `id'
> vcache.c:106: error: structure has no member named `opcode'
> vcache.c: In function `vcache_forward_varp':
> vcache.c:506: error: structure has no member named `opcode'
> vcache.c: In function `vcache_handle_message':
> vcache.c:614: error: structure has no member named `opcode'
> make[1]: *** [vcache.o] Error 1
> make[1]: Leaving directory `/usr/src/bk/xen/tools/vnet/vnetd'
> make: *** [vnetd] Error 2
> _________________________________________________________________
> 
> Does anyone have an idea as to what opcode and id should be?
> 
> B.
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

RE: tools/vnet build issues and a patch to fix part

[B.G. Bruce]

On Wed, 2005-02-09 at 12:34, Ian Pratt wrote:

> You don't half like living on the bleeding edge ;-)

Something about frying pans and a fire comes to mind.  :-) 

> I'm not aware of anyone outside HP that uses vnets regularly, but
> they're a cool thing that we want to maintain.
> 
> I suspect that the current breakage is because the code was written for
> 2.6.7, and there have been updates since. Syncing up probably isn't very
> hard. Perhaps a volunteer will step forward....

from what I have seen so far, it probably got more to do with how
VnetMsgHdr is being used in VarpHdr (both in vnet-modules/if_varp.h) and
things that earlier versions of gcc allowed that gcc 3.3.5 doesn't.  At
least that's my initial thoughts. (gentoo-dev-sources-2.6.10-r6) in case
you were wondering .... 

Now if I was REALLY bleeding edge I would be doing the initial setup
with gentoo-hardened (2.6.x) (grsecurity/ssp/pie) on uClibc and
gcc-3.4.x.

> Ian 
>  
> > My findings to date are as follows:
> > 1) building of gc is broken (at least for me).  I needed the attached
> > patch to get things working properly.
> > 
> > PATCH tools_vnet_Makefile.gc-6.3.patch - Signed off by:  bgb@nt-nv.com
> > 
> > 2)  The actual vnet-module driver is failing to build with 
> > the following
> > errors:
> > ______________________________________________________________
> > __________
> > 
> > In file included from vnetd.h:22,
> >                  from vcache.c:39:
> > ../vnet-module/if_varp.h:39: warning: declaration does not declare
> > anything
> > In file included from vcache.c:39:
> > vnetd.h:40: warning: declaration does not declare anything
> > vcache.c: In function `varp_send':
> > vcache.c:105: error: structure has no member named `id'
> > vcache.c:106: error: structure has no member named `opcode'
> > vcache.c: In function `vcache_forward_varp':
> > vcache.c:506: error: structure has no member named `opcode'
> > vcache.c: In function `vcache_handle_message':
> > vcache.c:614: error: structure has no member named `opcode'
> > make[1]: *** [vcache.o] Error 1
> > make[1]: Leaving directory `/usr/src/bk/xen/tools/vnet/vnetd'
> > make: *** [vnetd] Error 2
> > _________________________________________________________________
> > 
> > Does anyone have an idea as to what opcode and id should be?
> > 
> > B.
> > 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

tools/vnet build issues and a patch to fix part

[B.G. Bruce]

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

Being that driver domains/xend are partially broken for me I thought I'd
take a run at vnet to accomplish something close to what I desire.  Is
anyone else out there running vnet?  If so, how stable have you found
it?

My findings to date are as follows:
1) building of gc is broken (at least for me).  I needed the attached
patch to get things working properly.

PATCH tools_vnet_Makefile.gc-6.3.patch - Signed off by:  bgb@nt-nv.com

2)  The actual vnet-module driver is failing to build with the following
errors:
________________________________________________________________________

In file included from vnetd.h:22,
                 from vcache.c:39:
../vnet-module/if_varp.h:39: warning: declaration does not declare
anything
In file included from vcache.c:39:
vnetd.h:40: warning: declaration does not declare anything
vcache.c: In function `varp_send':
vcache.c:105: error: structure has no member named `id'
vcache.c:106: error: structure has no member named `opcode'
vcache.c: In function `vcache_forward_varp':
vcache.c:506: error: structure has no member named `opcode'
vcache.c: In function `vcache_handle_message':
vcache.c:614: error: structure has no member named `opcode'
make[1]: *** [vcache.o] Error 1
make[1]: Leaving directory `/usr/src/bk/xen/tools/vnet/vnetd'
make: *** [vnetd] Error 2
_________________________________________________________________

Does anyone have an idea as to what opcode and id should be?

B.

[-- Attachment #2: tools_vnet_Makfiel.gc-6.3.patch --]
[-- Type: text/x-patch, Size: 522 bytes --]

diff -ruN xen-2.0-testing.bk/tools/vnet/Makefile xen/tools/vnet/Makefile
--- xen-2.0-testing.bk/tools/vnet/Makefile      2005-01-31 20:38:33.000000000 -0400
+++ xen/tools/vnet/Makefile     2005-02-09 11:28:48.132468424 -0400
@@ -20,10 +20,8 @@
        tar xfz gc.tar.gz
        ln -sf gc?.? gc
  
-gc/Makefile:
-       (cd gc && ./configure --prefix=`pwd`/install)
-
 gc-install: gc gc/Makefile
+       (cd gc && make test && ./configure --prefix=`pwd`/install)
        make -C gc
        make -C gc install

Re: tools/vnet build issues and a patch to fix part

[Mike Wray]

B.G. Bruce wrote:
> Being that driver domains/xend are partially broken for me I thought I'd
> take a run at vnet to accomplish something close to what I desire.  Is
> anyone else out there running vnet?  If so, how stable have you found
> it?
> 
> My findings to date are as follows:
> 1) building of gc is broken (at least for me).  I needed the attached
> patch to get things working properly.

Thanks to Bruce for funding this. It looks like my code has either
bit-rotted or (looking at the patch) thatsome earlier fixes
missed a couple of uses of inline structures.

> 
> PATCH tools_vnet_Makefile.gc-6.3.patch - Signed off by:  bgb@nt-nv.com
> 
> 2)  The actual vnet-module driver is failing to build with the following
> errors:
> ________________________________________________________________________
> 
> In file included from vnetd.h:22,
>                  from vcache.c:39:
> ../vnet-module/if_varp.h:39: warning: declaration does not declare
> anything
> In file included from vcache.c:39:
> vnetd.h:40: warning: declaration does not declare anything
> vcache.c: In function `varp_send':
> vcache.c:105: error: structure has no member named `id'
> vcache.c:106: error: structure has no member named `opcode'
> vcache.c: In function `vcache_forward_varp':
> vcache.c:506: error: structure has no member named `opcode'
> vcache.c: In function `vcache_handle_message':
> vcache.c:614: error: structure has no member named `opcode'
> make[1]: *** [vcache.o] Error 1
> make[1]: Leaving directory `/usr/src/bk/xen/tools/vnet/vnetd'
> make: *** [vnetd] Error 2
> _________________________________________________________________
> 
> Does anyone have an idea as to what opcode and id should be?
> 
> B.
> 
> 
> ------------------------------------------------------------------------
> 
> diff -ruN xen-2.0-testing.bk/tools/vnet/Makefile xen/tools/vnet/Makefile
> --- xen-2.0-testing.bk/tools/vnet/Makefile      2005-01-31 20:38:33.000000000 -0400
> +++ xen/tools/vnet/Makefile     2005-02-09 11:28:48.132468424 -0400
> @@ -20,10 +20,8 @@
>         tar xfz gc.tar.gz
>         ln -sf gc?.? gc
>   
> -gc/Makefile:
> -       (cd gc && ./configure --prefix=`pwd`/install)
> -
>  gc-install: gc gc/Makefile
> +       (cd gc && make test && ./configure --prefix=`pwd`/install)
>         make -C gc
>         make -C gc install

Mike




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click