Hi, all When I tried to build vnet module in FC6 xen, I got stuck in it. I downloaded xen sourcecode 3.0.4 and went to xen tree tools/vnet sub directory and try to compile it. First it said missing the files config.hand autoconf.h, so I copied them from linux xen kernel source code to the vnet-module/linux directory linux-2.6.16.33-xen]# cp include/linux/autoconf.h ../tools/vnet/vnet-module /linux/ And I have no problem in ''make'' now but I continued to get stuck in ''make install''. the error information was as below: make -C vnetd install make[1]: Entering directory `/root/Desktop/xen-3.0.4_1-src/tools/vnet/vnetd'' mkdir -p /usr/sbin vnetd /usr/sbin make[1]: vnetd: Command not found make[1]: *** [install] Error 127 make[1]: Leaving directory `/root/Desktop/xen-3.0.4_1-src/tools/vnet/vnetd'' make: *** [vnetd-install] Error 2 I wonder what "vnetd /usr/sbin" wants to do. And I''ve searched on the forum but I didn''t see anyone ever get this problem. And also few information is released on vnet. My machine is IBM ThinkCenter Pentiumn 4 HT. I use FC6. Do anyone have any idea of what''s wrong with it? Thanks in advance. ~wenjin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stick w/ your distro unless you must go to upstream.... (Open source Rule #2542 I think. :-) http://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/SRPMS/xen-3.0.3-6.fc6.src.rpm On 3/13/07, HU wenjin <wenjin.hu@gmail.com> wrote:> Hi, all > > When I tried to build vnet module in FC6 xen, I got stuck in it. I > downloaded xen sourcecode 3.0.4 and went to xen tree tools/vnet sub > directory and try to compile it. First it said missing the files config.h > and autoconf.h, so I copied them from linux xen kernel source code to the > vnet-module/linux directory > linux-2.6.16.33-xen]# cp include/linux/autoconf.h ../tools/vnet/vnet-module > /linux/ > And I have no problem in ''make'' now but I continued to get stuck in ''make > install''. the error information was as below: > make -C vnetd install > make[1]: Entering directory `/root/Desktop/xen-3.0.4_1-src/tools/vnet/vnetd'' > mkdir -p /usr/sbin > vnetd /usr/sbin > make[1]: vnetd: Command not found > make[1]: *** [install] Error 127 > make[1]: Leaving directory `/root/Desktop/xen-3.0.4_1-src/tools/vnet/vnetd'' > make: *** [vnetd-install] Error 2 > > I wonder what "vnetd /usr/sbin" wants to do. And I''ve searched on the forum > but I didn''t see anyone ever get this problem. And also few information is > released on vnet. > > My machine is IBM ThinkCenter Pentiumn 4 HT. I use FC6. > > Do anyone have any idea of what''s wrong with it? Thanks in advance. > > > ~wenjin > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- "Oh joy! Rapture! I''ve got a brain" -Scarecrow _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I''m afraid vnet is too untested to successfully build or use. I think most people are unaware of it, too. Maybe someone could pick this up, fix the install/Makefile error you hit and actually _document_ vnet. Then it should be possible to talk the distros into including it. Messing around with bridges while Xen has a better utility is SO tedious, especially if one is looking at consolidating whole networks into Xen, let aside the security advantages. 2007/3/14, HU wenjin <wenjin.hu@gmail.com>:> Hi, all > > When I tried to build vnet module in FC6 xen, I got stuck in it. I > downloaded xen sourcecode 3.0.4 and went to xen tree tools/vnet sub > directory and try to compile it. First it said missing the files config.h > and autoconf.h, so I copied them from linux xen kernel source code to the > vnet-module/linux directory > linux-2.6.16.33-xen]# cp include/linux/autoconf.h ../tools/vnet/vnet-module > /linux/ > And I have no problem in ''make'' now but I continued to get stuck in ''make > install''. the error information was as below: > make -C vnetd install > make[1]: Entering directory `/root/Desktop/xen-3.0.4_1-src/tools/vnet/vnetd'' > mkdir -p /usr/sbin > vnetd /usr/sbin > make[1]: vnetd: Command not found > make[1]: *** [install] Error 127 > make[1]: Leaving directory `/root/Desktop/xen-3.0.4_1-src/tools/vnet/vnetd'' > make: *** [vnetd-install] Error 2 > > I wonder what "vnetd /usr/sbin" wants to do. And I''ve searched on the forum > but I didn''t see anyone ever get this problem. And also few information is > released on vnet. > > My machine is IBM ThinkCenter Pentiumn 4 HT. I use FC6. > > Do anyone have any idea of what''s wrong with it? Thanks in advance.It would appear to be a really small bug, have you tried simply copying vnetd to /usr/sbin? maybe it works :) florian -- ''Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 3/13/07, Florian Heigl <florian.heigl@gmail.com> wrote:> Hi, > > I''m afraid vnet is too untested to successfully build or use. > I think most people are unaware of it, too.Heh, count me in there...> Maybe someone could pick this up, fix the install/Makefile error you > hit and actually _document_ vnet. Then it should be possible to talk > the distros into including it. > > Messing around with bridges while Xen has a better utility is SO > tedious, especially if one is looking at consolidating whole networks > into Xen, let aside the security advantages.Intriguing!> It would appear to be a really small bug, have you tried simply > copying vnetd to /usr/sbin? > maybe it works :)Seems reasonable. Looks like the build is trying to run it, rather than copy to the install target... jerry -- "Oh joy! Rapture! I''ve got a brain" -Scarecrow _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, 2007/3/14, Jerry Amundson <jamundso@gmail.com>:> On 3/13/07, Florian Heigl <florian.heigl@gmail.com> wrote: > > Hi, > > > > I''m afraid vnet is too untested to successfully build or use. > > I think most people are unaware of it, too. > > Heh, count me in there... > > > Maybe someone could pick this up, fix the install/Makefile error you > > hit and actually _document_ vnet. Then it should be possible to talk > > the distros into including it. > > > > Messing around with bridges while Xen has a better utility is SO > > tedious, especially if one is looking at consolidating whole networks > > into Xen, let aside the security advantages. > > Intriguing!There''s two ''public references'' to it, - one post on this or the xen-devel list, by it''s developer, somewhere in middle of last year, and I stumbled over some source code commit log, once - in the xen summit pdf''s at the xensource site; there''s also something called solarflare I think by a company of embedded gurus (iirc), which is a highspeed virtual networking implementation including 802.1q; this is the funniest thing - it was announced, written about, and is available _nowhere_. Regards, Florian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Florian Thansk for your reply. Actually, I really like to document how to make vnet work. And I also think that in the makefile, that line is missing the command cp. I added in the makefile. "make install" then it appears the following errors. Anyway, I copied the module vnet_module.ko to the directory /lib/modules/2.6.16.33-xen/kernel/xen/vnet_module.ko as 00INSTALL said . (The "xen" subdirectory is not there and I had to create it.) In the xend-config.sxp file, I use (network-script network-vnet). And boot up Xen, but Dom0''s interface is the bridging''s interface. And type "xm vnet-list" it said Error: method "xend_vnets" is not supproted. Can you give me more hints on what''s else I need to fix? Thank you. ~wenjin ---------------------------------------------------------------------------------------------------------- mkdir -p /usr/sbin cp vnetd /usr/sbin make[1]: Leaving directory `/root/xen-3.0.4_1-src/tools/vnet/vnetd '' make -C vnet-module install make[1]: Entering directory `/root/xen-3.0.4_1-src/tools/vnet/vnet-module'' Makefile.ver:45: KERNEL_SRC /root/xen- 3.0.4_1-src/linux-2.6.16.33-xen Makefile.ver:46: LINUX_VERSION 2.6.16.33 Makefile.ver:47: KERNEL_VERSION 2.6.16.33-xen Makefile.ver:48: KERNEL_RELEASE 2.6.16.33-xen Makefile.ver :49: KERNEL_ MODULE_DIR /lib/modules/$(KERNEL_RELEASE)/kernel make -C /root/xen-3.0.4_1-src/linux-2.6.16.33-xen M=`pwd` modules make[2]: Entering directory `/root/xen-3.0.4_1-src/linux-2.6.16.33-xen'' Building modules, stage 2. MODPOST make[2]: Leaving directory `/root/xen-3.0.4_1-src/linux-2.6.16.33-xen'' install -m 0755 -d /lib/modules/$(KERNEL_RELEASE)/kernel /bin/sh: KERNEL_RELEASE: command not found install -m 0554 vnet_module.ko /lib/modules/$(KERNEL_RELEASE)/kernel /bin/sh: KERNEL_RELEASE: command not found make[1]: Leaving directory `/root/xen-3.0.4_1-src/tools/vnet/vnet-module '' On 3/13/07, Florian Heigl <florian.heigl@gmail.com > wrote:> > Hi, > > I''m afraid vnet is too untested to successfully build or use. > I think most people are unaware of it, too. > > Maybe someone could pick this up, fix the install/Makefile error you > hit and actually _document_ vnet. Then it should be possible to talk > the distros into including it. > > Messing around with bridges while Xen has a better utility is SO > tedious, especially if one is looking at consolidating whole networks > into Xen, let aside the security advantages. > > > > 2007/3/14, HU wenjin < wenjin.hu@gmail.com>: > > Hi, all > > > > When I tried to build vnet module in FC6 xen, I got stuck in it. I > > downloaded xen sourcecode 3.0.4 and went to xen tree tools/vnet sub > > directory and try to compile it. First it said missing the files > config.h > > and autoconf.h, so I copied them from linux xen kernel source code to > the > > vnet-module/linux directory > > linux-2.6.16.33-xen]# cp include/linux/autoconf.h > ../tools/vnet/vnet-module > > /linux/ > > And I have no problem in ''make'' now but I continued to get stuck in > ''make > > install''. the error information was as below: > > make -C vnetd install > > make[1]: Entering directory `/root/Desktop/xen- > 3.0.4_1-src/tools/vnet/vnetd'' > > mkdir -p /usr/sbin > > vnetd /usr/sbin > > make[1]: vnetd: Command not found > > make[1]: *** [install] Error 127 > > make[1]: Leaving directory `/root/Desktop/xen- > 3.0.4_1-src/tools/vnet/vnetd'' > > make: *** [vnetd-install] Error 2 > > > > I wonder what "vnetd /usr/sbin" wants to do. And I''ve searched on the > forum > > but I didn''t see anyone ever get this problem. And also few information > is > > released on vnet. > > > > My machine is IBM ThinkCenter Pentiumn 4 HT. I use FC6. > > > > Do anyone have any idea of what''s wrong with it? Thanks in advance. > > It would appear to be a really small bug, have you tried simply > copying vnetd to /usr/sbin? > maybe it works :) > > florian > > -- > ''Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen'' >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users