 Home |
Products |
Support |
Community |
News |
xen-users
[Xen-users] Odd Dom0 network problem
| To: | xen-users@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-users] Odd Dom0 network problem |
| 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 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=Ihx8OdoIKCj+bIN8CYUB2Lj12fuw9q9RMvBFpF+9FYM=; b=k7tsqoKXeHC3kLcPramryDFSQmYVcVQKJvjVdfZqV2g1vW8KrPs9aai9ZQB0Mdy/gb gEEppgHP0bXc1uDZ2UnQqpAdnIUeW4TNV255xE+r2S8X6x3m0FDL1e6V0GZQwIgUV4ki NG33c8zEJ+cFc4YBAexQhXaOrfXyPBstgGojQ= |
| 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= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-users-request@lists.xensource.com?subject=help> |
| List-id: | Xen user discussion <xen-users.lists.xensource.com> |
| List-post: | <mailto:xen-users@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.18 (X11/20081119) |
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. Adam _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-users] failed to boot Domain-U, Muzammel Asghar |
|---|---|
| Next by Date: | [Xen-users] Network and IP problems, Heli |
| Previous by Thread: | [Xen-users] failed to boot Domain-U, Muzammel Asghar |
| Next by Thread: | [Xen-users] Network and IP problems, Heli |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
