From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan March Subject: Creating a vm with a non-existent /dev/mapper/ tap2 device effectively hangs dom0 system Date: Wed, 27 Jul 2011 16:29:59 -0700 Message-ID: <4E309F77.2040903@gt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 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. For example, I have /dev/mapper/nathanxenuk1 as a valid disk and /dev/mapper/test which doesn't exist. Creating using libvirt: nathanxenuk1