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

[Xen-users] switching runlevel 5 to 3 kills networking


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Phill Jolliffe <phill.jolliffe@xxxxxxxxx>
  • Date: Tue, 28 Dec 2010 21:27:09 +0000
  • Delivery-date: Tue, 28 Dec 2010 13:29:06 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=UPrfY+y0nAC77owUB5Eitg2+gnnJkU3kspPU+LQi8R6I4puTiYT1heiMSREc2FLoB5 MZXfaf+67fL7GU9aj7lINRTZu2ylJjVHWe/nYdywMRMfWO9SR/cU24b1GH9ujasKC0kO Hz3PToQzfccwxwxVmigxdMcM5sdu6YNlkUrsY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I had my first xen (3.1.2-192) install progressing nicely, Centos 5.5 for dom0. Got my first domU installed (Win7) as well.

Both dom0 and domU had network access. I had network-bridge setup.

I switched the runlevel from 3 to 5 networking is down.

Both xend and xendomains are services in runlevel 3 and 5.

If i try and ping the default gateway I now get "destination unreachable" from my own src address.

netstat -rn shows the directly connected subnet

ifconfig shows me my eth0, peth0, vif0.0 and xenbr0 but no tap interface which I recall seeing in runlevel 5

Any ideas? 

Cheers

Phill 

--
Phill Jolliffe

_______________________________________________
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®.