From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wray Subject: Re: Problem with xen vnet on x86_64 Date: Wed, 09 Aug 2006 17:27:48 +0100 Message-ID: <44DA0D04.3040408@hp.com> References: <68DBE68F3589A84BB5C776EE69E82A72D81F7D@orsmsx413.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <68DBE68F3589A84BB5C776EE69E82A72D81F7D@orsmsx413.amr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Sanjeepan, Vivekananthan" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Sanjeepan, Vivekananthan wrote: > I am trying to compile xen vnet on x86_64. I am getting a following err= or (see below). I saw a mailing list discussion about this issue in march= , 2006. There was a patch propsed to work around it. If there is a final = version of the patch please point me to it. The error is as follows: >=20 > /home/sanjee/workspace/xen/xen-unstable.hg/tools/vnet/vnet-module/varp_= socket.c: In function =91socketcall=92: > /home/sanjee/workspace/xen/xen-unstable.hg/tools/vnet/vnet-module/varp_= socket.c:86: error: =91__NR_socketcall=92 undeclared (first use in this f= unction) > /home/sanjee/workspace/xen/xen-unstable.hg/tools/vnet/vnet-module/varp_= socket.c:86: error: (Each undeclared identifier is reported only once > /home/sanjee/workspace/xen/xen-unstable.hg/tools/vnet/vnet-module/varp_= socket.c:86: error: for each function it appears in.) > make[3]: *** [/home/sanjee/workspace/xen/xen-unstable.hg/tools/vnet/vne= t-module/varp_socket.o] Error 1 > make[2]: *** [_module_/home/sanjee/workspace/xen/xen-unstable.hg/tools/= vnet/vnet-module] Error 2 > make[2]: Leaving directory `/home/sanjee/workspace/xen/xen-unstable.hg/= linux-2.6.16.13-xen' > make[1]: *** [module] Error 2 > make[1]: Leaving directory `/home/sanjee/workspace/xen/xen-unstable.hg/= tools/vnet/vnet-module'make: *** [vnet-module-all] Error 2 >=20 > Thanks, > Sanjee >=20 The problem is that the x86_64 kernel doesn't have the socketcall multipl= exor that the vnet implementation uses for its socket api. The proposed patch had some probl= ems, so it probably didn't get applied. As I'm responsible for the code that doesn't work I'll take a look at wha= t can be done. Regards, Mike Wray