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

[Xen-users] xen kernel does not boot if eth0:1 is added


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Ivan <gonzalezzzivan@xxxxxxxxx>
  • Date: Fri, 23 Apr 2010 08:32:50 +0300
  • Delivery-date: Thu, 22 Apr 2010 22:34:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=b1uuJPjpXSM1x7ESkCqtBWCYU/GkJC/fvItG7qi7eMNjyUFVGmpleqKZGbI7uWWYfe drdwbJ82lWTfgzgo5XGayyT3knchHrBy18RdUZwevMdoTwEoA5v7LCZSZH5iUgPG6dX2 Ris4vn2kYqKKkma6xVoK+oVq5d6x/OTavhmU0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I have CentOS 5.4 with Xen Kernel and it works OK in general.
But I need to add a new eth0:1 interface with ip address from my ip subnet dedicated for VM-s. If I create the eth0:1 interface, the system boots normally, but I can't ping server and it seems like network interfaces are unavailable.
I guess it's correlated with routing/bridging system...
Could you please help me with this issue?

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

 


Rackspace

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