This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] DOM0 diskless => NAT doesn't work ?!

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] DOM0 diskless => NAT doesn't work ?!
From: Bret Mckee <bret.mckee@xxxxxx>
Date: 09 Apr 2004 11:09:47 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 10 Apr 2004 13:28:15 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1BBdWq-0007Wy-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1BBdWq-0007Wy-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx

Ian and I exchanged more email off list, and he eventually asked the
right question.

For reasons that I don't  understand (but presumably which are related
to how things get added to the routing tables differently if the kernel
initialized the networking instead of the startup scripts) the routing
tables are slightly different if DOM0 is diskless.  On a diskfull
system, the relevant portions look like:

Kernel IP routing table
Destination  Gateway      Genmask         Flags Metric Ref    Use Iface     U     0      0        0 eth0     U     0      0        0 eth0

and on a diskless system the look like:
Kernel IP routing table
Destination  Gateway      Genmask         Flags Metric Ref    Use Iface     U     0      0        0 lo     U     0      0        0 eth0

Notice that the diskless system's first entry is to lo, not to eth0. 
This was the root of the problem.  I fixed it with:

route del -net gw netmask  lo

With that change everything works as expected, and I can boot totally
disless.  I had looked at the routing tables earlier, but missed that

Thanks Ian.


This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>