From mboxrd@z Thu Jan  1 00:00:00 1970
From: VM-Sascha <sascha@argc.de>
Subject: XEN 3.4 and blktapctrl
Date: Fri, 29 May 2009 03:14:26 -0700 (PDT)
Message-ID: <23771002.post@talk.nabble.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org


Hello all, 

i'm playing with the new XEN 3.4 and if i use the backend "tap:aio" on my
domUs, all have the same
tapctrlwriteX & tapctrlreadX fifos

<SNIP>

tapdisk /var/run/tap/tapctrlwrite312222 /var/run/tap/tapctrlread312222
tapdisk /var/run/tap/tapctrlwrite312222 /var/run/tap/tapctrlread312222
tapdisk /var/run/tap/tapctrlwrite312222 /var/run/tap/tapctrlread312222
tapdisk /var/run/tap/tapctrlwrite312222 /var/run/tap/tapctrlread312222

</SNIP>

On XEN 3.3.1 it was always the domid like this:

<SNIP>

tapdisk /var/run/tap/tapctrlwrite1 /var/run/tap/tapctrlread1
tapdisk /var/run/tap/tapctrlwrite2 /var/run/tap/tapctrlread2
tapdisk /var/run/tap/tapctrlwrite3 /var/run/tap/tapctrlread3
tapdisk /var/run/tap/tapctrlwrite4 /var/run/tap/tapctrlread4

</SNIP>

Has anyone an idea why this happens on the new release?

Thanks,
Sascha



-- 
View this message in context: http://www.nabble.com/XEN-3.4-and-blktapctrl-tp23771002p23771002.html
Sent from the Xen - Dev mailing list archive at Nabble.com.