From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Lalancette <clalance@redhat.com>
Subject: Re: [PATCH]: Fix xm block-detach
Date: Tue, 02 Dec 2008 15:20:48 +0100
Message-ID: <49354440.3080003@redhat.com>
References: <49352971.6020605@redhat.com>
	<96C95486AAA6EEkanno.masaki@jp.fujitsu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <96C95486AAA6EEkanno.masaki@jp.fujitsu.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Masaki Kanno wrote:
> Hi Chris,
> 
> I could not reproduce the problem by using the latest xen-unstable.
> 
> I also found a problem of block tap devices included by c/s 18562, 
> then I have fixed the problem by c/s 18843.  But the problem occurred 
> by using xm shutdown or xm destroy or etc, not xm block-detach.
> 
> Could you try xm block-detach by using the latest xen-unstable?
> 
> Best regards,
>  Kan

OK, interesting.  I'll give it a shot, but it's going to take a little while
since I have to build from scratch.  I'll report when I'm done.

Thanks,

-- 
Chris Lalancette