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

Re: [Xen-devel] blktap3: libxl complaining when a domain gets destroyed

  • To: Roger Pau Monne <roger.pau@xxxxxxxxxx>
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxxx>
  • Date: Wed, 15 May 2013 12:20:35 +0100
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Wed, 15 May 2013 11:21:01 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac5A4ol6ANY6E3PfSayJCizxV+L3eAQezgag
  • Thread-topic: [Xen-devel] blktap3: libxl complaining when a domain gets destroyed

> This is because libxl will wait for the backend to reach state '6'
> (closed). Even if state 6 is not reached libxl will clean up the
> backend path, you should check why blktap3 doesn't set the backend to
> state 6.

At some point during "xl destroy ..." the backend state is set to 5 (assuming 
by libxl?). I get a XenStore watch triggering on this event. So how should I 
handle this event? Setting the backend state to 6 fails with EPERM, which I 
don't understand since I do modify the backend state when going from 
initialised to connected etc.

Xen-devel mailing list



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