No, this update does not fix the behaviour I'm seeing with tapdisk2 (i.e.,
64-bit HVM, Multi-VCPU-domains causing the tapdisk2 process to block
indefinitely/fail), and I've also got the problem that tapdev*-devices don't
disappear after restarting a DomU.
So, I guess this is no "fix" yet. I'm still waiting for the patch spoken of
on xen-devel, which queues the requests for tapdisk2 to a single thread,
which might possibly be a fix for this (as I'm not seeing the problem on
Uni-VCPU domains).
--- Heiko.
-----Ursprüngliche Nachricht-----
Von: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag von Fajar A.
Nugraha
Gesendet: Montag, 17. Mai 2010 16:57
An: Heiko Wundram
Cc: Xen User-List
Betreff: Re: [Xen-users] Xen 4.0.0 - tapdisk2 "hangs"
On Mon, May 17, 2010 at 5:51 PM, Heiko Wundram <modelnine@xxxxxxxxxxxxx>
wrote:
> I'm in the process of testing this version (i.e., the kernel is being
> compiled as I write this); I should be able to comment on whether this
fixes
> things some time in the afternoon.
Thanks.
Could you also start-and-destroy some domUs repeatedly (two or three
times should be enough), and see if the devices on /dev/xen/blktap-2/*
keeps on increasing instead of reusing ununsed device nodes? Just want
to make sure whether the other problem I had is specific to my
environment (distro version, config, etc.) or if it's in the kernel.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home