From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Thanos Makatos <thanos.makatos@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: blktap3: libxl complaining when a domain gets destroyed
Date: Wed, 24 Apr 2013 13:54:54 +0200 [thread overview]
Message-ID: <5177C80E.9010906@citrix.com> (raw)
In-Reply-To: <4B45B535F7F6BE4CB1C044ED5115CDDE01541DB7346D@LONPMAILBOX01.citrite.net>
On 24/04/13 13:46, Thanos Makatos wrote:
> I'm testing blktap3 and when I destroy a domain via "xl destroy 21" I get the following behaviour: "xl destroy 21" seems to pause for a couple of seconds and then spits out the following:
> libxl: error: libxl_device.c:882:device_backend_callback: unable to remove device with path /local/domain/0/backend/vbd3/21/51712
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.
> libxl: error: libxl.c:1453:devices_destroy_cb: libxl__devices_destroy failed for 21
> Apart from these messages, the domain seems to be correctly destroyed and there aren't any leftovers in XenStore. I'm able to successfully start and stop the domain multiple times. What is libxl complaining about?
>
> --
> Thanos Makatos
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-04-24 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 11:46 blktap3: libxl complaining when a domain gets destroyed Thanos Makatos
2013-04-24 11:53 ` Ian Campbell
2013-04-24 11:54 ` Roger Pau Monné [this message]
2013-05-15 11:20 ` Thanos Makatos
2013-05-15 14:44 ` Thanos Makatos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5177C80E.9010906@citrix.com \
--to=roger.pau@citrix.com \
--cc=thanos.makatos@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.