Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] [PATCH] remove dummy 1.2.3.4 IP

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] remove dummy 1.2.3.4 IP
From: "Charles Coffing" <ccoffing@xxxxxxxxxx>
Date: Thu, 30 Mar 2006 18:39:25 -0500
Delivery-date: Thu, 30 Mar 2006 23:41:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Is there any good reason that a dummy NFS IP address of "1.2.3.4" is
added to the domU kernel's boot line (in
tools/python/xen/xm/create.py)?

In the past, I've seen cases where my domU would hang while the kernel
was initializing its networking.  Once I removed this dummy IP (as per
the attached patch), things came up fine.

Signed-off-by: Charles Coffing <ccoffing@xxxxxxxxxx>

Attachment: xen-no-dummy-nfs-ip.diff
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>