WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Starting DOM1

To: Sean Atkinson <sean@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Starting DOM1
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 23 Mar 2004 10:52:44 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 23 Mar 2004 10:53:34 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 23 Mar 2004 08:18:48 +0100." <1080026328.1536.26.camel@xxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > You might want to try configuring dom 0 and the new domain with
> > some over subnet e.g. 10.10.10.1/2 just to check that its not
> > something screwy with 169.254.x.x, which is treated slightly
> > differently to ensure packets can not escape the VMM.
> 
> I was indeed using 169.254.1.0/1, and moving to your suggested subnet
> fixed the networking so DOM1 boots fine off an NFS root.
> 
> Unfortunately that root had a broken distribution, so I've repartitioned
> after all to add a clean installation to a new partition, and perhaps
> I'll try the VBD/VD stuff for better performance too.

Please can you try backing out the following change and see if
that fixes it for the 169.254.x.x case:

http://xen.bkbits.net:8080/xeno-unstable.bk/diffs/xen/net/dev.c@xxxx?nav=index.html|src/.|src/xen|src/xen/net|hist/xen/net/dev.c

I suspect we're somehow killing 169.254.x.x packets even if
they're within the VMM rather than destined for the wire.

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
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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