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] Booting up the most recent 2.6.29-rc3 (pv_ops Dom0 suppo

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Booting up the most recent 2.6.29-rc3 (pv_ops Dom0 support) under Xen Unstable on Intel SATA (AHCI) box
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Fri, 6 Feb 2009 04:01:02 -0800 (PST)
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 06 Feb 2009 04:01:42 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1233921662; bh=i2PiXkC+WC35IaiWKGJNt/DDmQ1oN5spgtuYgVKVGa8=; h=Message-ID:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=t05JF0OWpoKGVi8WLo5iSAZo0mY0GqorXz+TJR15nBXijoNAjxmQgwM+2r/6nkreHkXp0qBaT4YtECZoNpea8DjeQw0aEJDOwMkS7TTE4jFsbXQGdB2CmeEC2MtaJxb3VpKtKhu3BdMPIFOJgxuWgRWoEaUmWHTgWJHGmTjMLZk=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=V3ppz2hi40nbVUEzUIBquwOCW9xJxi/jGQcLZLMAuAjcjmoUUDm/C981ugchA46GtWPNH0kesXMeH3MlXWyAno5bEReWpdf/b0dLsOe5XJ/twvIyeFEUMzSAaPCnplnJEO6n7oVJkTUcu3w171NCYi7a2F2xKXdBREuRAuYczq4=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <498BDE93.6020505@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bderzhavets@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
My board is  ASUS P5K Premium/WIFI.
Second Ethernet Adapter Realtek 8110SC (eth1) is attached to ADSL Modem (emulating local DHCP server for intranet ) and is working as xen bridge.

# ifconfig
# brctl show

looks fine,  just like under Xen 3.3.1 with xen-ified kernel

 Interface "eth1"  fails to work with LAN, but obtains IP address for Dom0 via DHCP request to ADSL Modem. I am able do DHCPRELEASE and DHCPREQUEST via "eth1"  whenever  i want.
But,  i cannot ping IP of ADSL modem from Dom0 , which clearly shows up in  DHCPOFFER & DHCPACK responses.
 F10 DomU obtained IP via this bridge also with no problems and communicates via ssh with Dom0.

>Does it fail to probe, or does it probe but
>not work?

Sorry,what exactly means "probe" eth1 ? 


--- On Fri, 2/6/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Booting up the most recent 2.6.29-rc3 (pv_ops Dom0 support) under Xen Unstable on Intel SATA (AHCI) box
To: bderzhavets@xxxxxxxxx
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Friday, February 6, 2009, 1:54 AM

Boris Derzhavets wrote:
> Build 2.6.29-rc3 with the most recent change set and load under Xen
Unstable
> Logged into Dom0.
> Was able to load F10 PV DomU via prepared image.
> DomU obtained IP (192.168.1.38) via DHCP .
> Opened ssh connection to Dom0 192.168.1.34 (Ubuntu 8.10 Server)
>
> LAN is still unavailable for both DomU & Dom0.
>

So you're saying that you got internal host<->guest networking going,
but external networking fails.
*****
YES
*****
What's your ethernet hardware? Does it fail to probe, or does it probe but
not work?

J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>