From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan March Subject: Re: Creating a vm with a non-existent /dev/mapper/ tap2 device effectively hangs dom0 system Date: Thu, 28 Jul 2011 15:13:00 -0700 Message-ID: <4E31DEEC.7000408@gt.net> References: <4E309F77.2040903@gt.net> <4E31B1E5.5080500@gt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E31B1E5.5080500@gt.net> 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 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