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


[Xen-devel] Re: Passing IP Parameters in 3.0

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Passing IP Parameters in 3.0
From: Anand Kumria <wildfire@xxxxxxxxxxx>
Date: Thu, 05 Jan 2006 14:50:55 +1100
Delivery-date: Thu, 05 Jan 2006 03:54:16 +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>
References: <e534a1bc0601031114j59d3b145u908298de05c5ef78@xxxxxxxxxxxxxx> <pan.2006.> <pan.2006.>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Pan/ (As She Crawled Across the Table (Debian GNU/Linux))
On Wed, 04 Jan 2006 14:46:56 +1100, Anand Kumria wrote:

> On Wed, 04 Jan 2006 13:44:09 +1100, Anand Kumria wrote:
>> On Tue, 03 Jan 2006 20:14:34 +0100, sde 9000 wrote:
>>> After having tried XenOS 4.2, Fedora Core 4, Fedora Core 5T1 as hosts and
>>> same sample plus fc3 and suse as guests it appears that passing the IP
>>> parameters from the domU configs idoes not want to work (dom0 and domU dumps
>>> attached). The only parm getting passed is the mac address, which shows up
>>> on the guest nicely.
>> I have the same issue - the issue for me is that I can not directly ssh
>> between dom0 and a domU instance.
> Oh, just a quick follow-up; domU <-> domU connections are working fine.
> The issue is entirely dom0 <-> domU; and all domU's at that too.

And one other datapoint, this works perfectly fine under Xen-2.0


Xen-devel mailing list