[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] vif0.{0..3} and veth0.{0..3} not appearing


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Stefan Berger <stefanb@xxxxxxxxxx>
  • Date: Sat, 23 Jun 2007 13:57:04 -0400
  • Delivery-date: Sat, 23 Jun 2007 10:49:13 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

   I am not sure what make vif0.{0..3} appear, but the attached
configuration file with the networking backend compiled into the kernel
does not show the interfaces. Also veth{0..3} do not appear once the
kernel starts.

   The attached configuration file has been derived from
'linux-2.6.18-xen.hg/buildconfigs/linux-defconfig_xen_x86_32'. When this
file is copied into build-linux-2.6.18-xen-x86_32 the following errors
appear while building that kernel.

  GEN
/opt/daily_builds/2007-06-22-16-00/xen-unstable.hg/build-linux-2.6.18-xen_x86_3
scripts/kconfig/conf -s arch/i386/Kconfig
.config:3278:warning: trying to assign nonexistent symbol
XEN_COMPAT_030002
.config:3279:warning: trying to assign nonexistent symbol
XEN_COMPAT_030004
.config:3282:warning: trying to assign nonexistent symbol XEN_UTIL
.config:3283:warning: trying to assign nonexistent symbol XEN_BALLOON
.config:3284:warning: trying to assign nonexistent symbol XEN_DEVMEM
.config:3285:warning: trying to assign nonexistent symbol XEN_REBOOT


  Stefan


Attachment: config_no_vif
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.