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: Mon, 22 Mar 2004 12:03:15 +0000
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Mon, 22 Mar 2004 13:24:30 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 22 Mar 2004 12:45:27 +0100." <1079955927.1554.112.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
> There are no reports of any connection attempts to the NFS server, as
> there are when I test the mount locally.  The portmap service is
> running, I've disabled any iptables, and run xen_nat_enable.

I'd run tcpdump in domain 0 and see if you can see any packets at
all. 

You shouldn't need to run all of xen_nat_enable -- the only bit
you should need is the 'ifconfig eth0:xen 169.254.1.0' alias.

What IP address are you giving the new domain? (I guess
169.254.1.1).  What's the kernel command line look like?

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.

Cheers,
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>