From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Lu=EDs?= Silva Subject: Tapdisk2 problem Date: Wed, 04 Aug 2010 15:04:39 +0100 Message-ID: <1280930679.3277.11.camel@luis-port> Reply-To: luis.silva@axiomasoft.pt Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1825654741==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-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 --===============1825654741== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-bYBTov3jQDUOIM0tJKSs" --=-bYBTov3jQDUOIM0tJKSs Content-Type: multipart/alternative; boundary="=-d74dLtp2Vmo0X7Fvpla5" --=-d74dLtp2Vmo0X7Fvpla5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=C3=ADs --=-d74dLtp2Vmo0X7Fvpla5 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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/image= s/srv-001-ub1004.img), when I try to terminate it by issuing "echo 1 &= gt; /sys/class/blktap2/blktap0/remove", the last command hangs and tap= disk2 hangs using 100% cpu.

This happens both on manual device destruction and on virtual machine shutd= own. I don't know exactly what triggered this behaviour, but I suspect kern= el changes.

Can anyone confirm this behaviour?

Thanks,
Luís --=-d74dLtp2Vmo0X7Fvpla5-- --=-bYBTov3jQDUOIM0tJKSs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAkxZc3MACgkQXSU0BM8MHj8WvACfUKUC4TNyCF8oGl3nO7qrOWwv F0IAnj3Occy41EqU0i76rLLa+skkO3KO =qlXQ -----END PGP SIGNATURE----- --=-bYBTov3jQDUOIM0tJKSs-- --===============1825654741== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1825654741==--