From: "Luís Silva" <luis.silva@axiomasoft.pt>
To: xen-devel@lists.xensource.com
Subject: Tapdisk2 problem
Date: Wed, 04 Aug 2010 15:04:39 +0100 [thread overview]
Message-ID: <1280930679.3277.11.camel@luis-port> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 620 bytes --]
Hello,
I'm using both xen 4.0.1-rc5 and the latest pv_ops dom0 kernel (branch
xen/stable-2.6.32.x), but I'm having some problems with tapdisk2...
Basically, if I create a tap device (tapdisk2 -n
aio:/var/lib/libvirt/images/srv-001-ub1004.img), when I try to terminate
it by issuing "echo 1 > /sys/class/blktap2/blktap0/remove", the last
command hangs and tapdisk2 hangs using 100% cpu.
This happens both on manual device destruction and on virtual machine
shutdown. I don't know exactly what triggered this behaviour, but I
suspect kernel changes.
Can anyone confirm this behaviour?
Thanks,
Luís
[-- Attachment #1.1.2: Type: text/html, Size: 913 bytes --]
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-08-04 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 14:04 Luís Silva [this message]
2010-08-15 16:14 ` Tapdisk2 problem Luís Silva
2010-08-15 16:59 ` Pasi Kärkkäinen
2010-08-15 19:35 ` Daniel Stodden
2010-08-15 20:28 ` Keir Fraser
2010-08-15 20:36 ` Daniel Stodden
2010-08-15 20:48 ` Keir Fraser
2010-08-15 21:54 ` Daniel Stodden
2010-08-15 22:07 ` Michael Brade
2010-08-16 6:56 ` Pasi Kärkkäinen
2010-08-18 17:17 ` Michael Brade
2010-08-18 17:27 ` Keir Fraser
2010-08-19 13:31 ` Ian Jackson
2010-08-16 7:02 ` Pasi Kärkkäinen
2010-08-16 8:41 ` Keir Fraser
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=1280930679.3277.11.camel@luis-port \
--to=luis.silva@axiomasoft.pt \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).