All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>, Ryan O'Connor <rjo@cs.ubc.ca>
Subject: Re: regression with c/s 21223
Date: Fri, 07 May 2010 07:37:18 -0600	[thread overview]
Message-ID: <4BE4178E.2030406@novell.com> (raw)
In-Reply-To: <C8098E2C.139E6%keir.fraser@eu.citrix.com>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

Keir Fraser wrote:
> On 07/05/2010 04:36, "Jim Fehlig" <jfehlig@novell.com> 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?
>   

That is certainly an approach we are considering for our Xen 4.0-based
packages - see attached patch.  As mentioned previously, we are not yet
supporting blktap2 so such a change seems appropriate in our case.

I'm hoping some of the folks that integrated blktap2 in xend can provide
suggestions.

Regards,
Jim


[-- Attachment #2: suse-disable-tap2-default.patch --]
[-- Type: text/x-patch, Size: 1171 bytes --]

Index: xen-4.0.0-testing/tools/python/xen/xm/main.py
===================================================================
--- xen-4.0.0-testing.orig/tools/python/xen/xm/main.py
+++ xen-4.0.0-testing/tools/python/xen/xm/main.py
@@ -2629,8 +2629,10 @@ def xm_usb_list_assignable_devices(args)
 def parse_block_configuration(args):
     dom = args[0]
 
-    if args[1].startswith('tap:'):
+    if args[1].startswith('tap2:'):
         cls = 'tap2'
+    elif args[1].startswith('tap:'):
+        cls = 'tap'
     else:
         cls = 'vbd'
 
Index: xen-4.0.0-testing/tools/python/xen/xm/create.py
===================================================================
--- xen-4.0.0-testing.orig/tools/python/xen/xm/create.py
+++ xen-4.0.0-testing/tools/python/xen/xm/create.py
@@ -791,8 +791,10 @@ def configure_disks(config_devs, vals):
     """Create the config for disks (virtual block devices).
     """
     for (uname, dev, mode, backend, protocol) in vals.disk:
-        if uname.startswith('tap:'):
+        if uname.startswith('tap2:'):
             cls = 'tap2'
+        elif uname.startswith('tap:'):
+            cls = 'tap'
         else:
             cls = 'vbd'
 

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-05-07 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  3:36 regression with c/s 21223 Jim Fehlig
2010-05-07  8:30 ` Keir Fraser
2010-05-07 13:37   ` Jim Fehlig [this message]
2010-05-07 18:12     ` Keir Fraser
2010-05-07 19:31       ` Jim Fehlig
2010-05-07 19:41         ` Keir Fraser
2010-05-16 10:54           ` Does Xen 3.4.3 support pvops kernel 2.6.32.12 ? Boris Derzhavets
2010-05-16 11:09             ` Keir Fraser
2010-05-16 12:11               ` Joanna Rutkowska

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BE4178E.2030406@novell.com \
    --to=jfehlig@novell.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=rjo@cs.ubc.ca \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.