WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Fwd: [Xen-users] Have anyone made vnet working? how?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Fwd: [Xen-users] Have anyone made vnet working? how?
From: "HU wenjin" <wenjin.hu@xxxxxxxxx>
Date: Fri, 16 Mar 2007 03:25:19 -0400
Delivery-date: Fri, 16 Mar 2007 00:24:27 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=PuZUuQHebX/Jb+09LthgQVWtfpSTWTByETXF3STPu3WtPlYZJAeReYPOoOKJKafDJwh8iLqLtZcVpboYB8J6nk90Vtwa2l+b/w8uo62HpwI+fXRhntn4t9tq35sKZCv7TFA8qO4dAsT5JxpmFFg/GQtyuKywiCOaEYjzXNJgnhA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=bttd3CECmiCnIO2JnbV9KYiJ043AyHG/Hb0puqs2Q3OKgz7Z/wUS8oAeOyPYcgf7KjfGObYUFZRj+VSyJWYuKAaBYT1QWtjyfOAltnQMAqt8rwz+I046Fztesgcnnsr6i1BcPby+Ajbbq5rEQke+GtlUKd9ploG7drP2wTVm6nQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <e0e2da9d0703160024s7cbb2d56t5957f157c7e9fad3@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <e0e2da9d0703131908r7f65f758y3ef66db5e47c4d2c@xxxxxxxxxxxxxx> <77abe410703131955u509149d4r75a7179547ff5b4@xxxxxxxxxxxxxx> <e0e2da9d0703160024s7cbb2d56t5957f157c7e9fad3@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxx > 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@xxxxxxxxx>:
> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>