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] regression with c/s 21223

To: Jim Fehlig <jfehlig@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] regression with c/s 21223
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 7 May 2010 09:30:20 +0100
Cc: Ryan O'Connor <rjo@xxxxxxxxx>
Delivery-date: Fri, 07 May 2010 01:30:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BE38AD9.3010701@xxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acrtlqo/meT5NSVHSKKxUzDEweyHrwAKN0u8
Thread-topic: [Xen-devel] regression with c/s 21223
User-agent: Microsoft-Entourage/12.24.0.100205
On 07/05/2010 04:36, "Jim Fehlig" <jfehlig@xxxxxxxxxx> wrote:

> Frankly, I'm not sure how best to handle this case.  The current
> philosophy seems to be treat all 'tap:foo' devices as blktap2 (see c/s
> 19874 - author cc'd), but fall back to blktap1 if blktap2 is not found
> when domU is started.  I'm certainly having problems differentiating
> between the two in to_sxp().
> 
> Any suggestions on how to prevent the bug reported in [1] without this
> new regression?

Way outside my comfort zone with xend I'm afraid. Do you think we need
explicit differentiation between tap and tap2?

 -- Keir



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