[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Creating a vm with a non-existent /dev/mapper/ tap2 device effectively hangs dom0 system

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Nathan March <nathan@xxxxxx>
  • Date: Thu, 28 Jul 2011 15:13:00 -0700
  • Delivery-date: Thu, 28 Jul 2011 15:14:58 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gt.net; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=Ft4Jeq 6iCz/y22y/HZpDvFAmJKx2XLoMWnjyHDXE8Im3vla0iguDxAaI2RUAJoEcKcop// hbG/lAPQqKL3SV9WpfJs9Hp9q3BBlKspXU+u4hh51g09ZHAMMA0SiK2iucMeJii4 YCEZAJh5MAn9qLQYtzJtiekvwr4r/HGe049dI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 7/28/2011 12:00 PM, Nathan March wrote:
On 7/27/2011 4:29 PM, Nathan March wrote:
Have an interesting one here, originally found on xen 4.1.0 but just upgraded to xen 4.1.1 and it's still here.

Creating a VM with a tap2 device pointed at /dev/mapper/something, when that device doesn't exist, causes the tapdisk2 process to go into D mode and also manages to take out any process that queries it.

This also happens on proper shutdown of a VM, so I must have done something crazy to the setup here since other people haven't been complaining. If I start a VM, strace it's tapdisk2 and then send the VM a shutdown, the strace shows tapdisk2 hanging here:

*sigh*, for anyone who finds this via google, tracked it down to a stupid error. Shouldn't be using tapdisk2 for accessing an iscsi device since it appears as a raw block device, after changing to using phy: things work properly.

- Nathan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.