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

[Xen-users] Odd Dom0 network problem

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Adam Huffman <adam.huffman@xxxxxxxxx>
  • Date: Wed, 17 Dec 2008 14:36:44 +0000
  • Delivery-date: Wed, 17 Dec 2008 06:37:24 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=qBK/5ggbojEdGM9SkojhYJnx54yZKhQseSJInpaoGA064kMiKmUzfzulN6R/0wkPfb A6auFaJGxPwtirCTawr8r7KjzFu2XUE4GfH4v3Gone2LgcQJxYMxfNzWTsoO09xzt5KX rf8YCUondS3DXndkw+e38tdbu9GKWiv8jLTzM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I have a Centos 5.2 server hosting 3 DomUs. What I've noticed recently is that for some reason at boot the Dom0 interface eth0 is not picking up an IP address. This happens even when I disable libvirtd/dnsmasq or if I set the IP statically in /etc/sysconfig.

The odd thing is that if I connect via a virtual console and restart networking, it does pick up the correct IP address and is accessible normally. At the moment I'm forcing that in /etc/rc.local, but that's an ugly hack and I'd much rather fix it properly.

Not quite sure where to look in the morass of Xen logs.


Xen-users mailing list



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