|
|
![](http://www.xen.org/images/globals/pixel.gif) |
|
|
|
|
|
|
|
xen-devel
[Xen-devel] XEN 3.4 and blktapctrl
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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] XEN 3.4 and blktapctrl,
VM-Sascha <=
|
|
|
|
|