7 messages in com.xensource.lists.xen-develRe: [Xen-devel] Starting DOM1
FromSent OnAttachments
Sean Atkinson22 Mar 2004 02:22 
Keir Fraser22 Mar 2004 02:29 
Sean Atkinson22 Mar 2004 03:45 
Ian Pratt22 Mar 2004 04:02 
Sean Atkinson22 Mar 2004 23:18 
Ian Pratt23 Mar 2004 02:52 
Sean Atkinson25 Mar 2004 01:02 
Subject:Re: [Xen-devel] Starting DOM1
From:Sean Atkinson (se@netproject.com)
Date:03/25/2004 01:02:06 AM
List:com.xensource.lists.xen-devel

Hi,

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@1.82?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.

Only just got around to testing this, but I'm afraid I see exactly the same RPC errors as without the patch. I note that this is different behaviour than if no NFS server runs, when things just stick looking up RPC ports.

Also if I boot from my new root disk partition with the default subnet details, DOM0 receives no ping replies from 169.254.1.1 and DOM1 complains about a broadcast address trying to ping 169.254.1.0, and still receives nothing if I use "-b" to force broadcast ping.

Seems it's to do with DOM0's 169.254.1.0 address, but then how does that work for others?

Cheers,

Sean.

-- Sean Atkinson <se@netproject.com> Netproject

_______________________________________________ Xen-devel mailing list Xen-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel