From: "Sébastien Riccio" <sr@swisscenter.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: xm/xl block-detach issue
Date: Sat, 09 Jul 2011 16:34:42 +0200 [thread overview]
Message-ID: <4E186702.6050601@swisscenter.com> (raw)
Hi dear list,
I'm using xen 4.1.1 (built from tar.gz) with 2.6.39.2 kernel + blkback
module and I'm getting into an issue trying to detach a block device
from a domain.
What I did:
root@mybox:~# vhd-util create -s 50000 -n /cloud/data2/machines/vm1.vhd
root@mybox:~# xl block-attach 0 tap:vhd:/cloud/local/vm1.vhd xvda rw 0
everything fine, xvda shows up in the dom0 and I can access it.
Now i want to detach it to reattach it to another domain:
root@mybox:~# xl block-list 0
Vdev BE handle state evt-ch ring-ref BE-path
51728 0 0 4 99 8 /local/domain/0/backend/vbd/0/51728
root@mybox:~# xl block-detach 0 51728
Error: Device 51728 not connected
Usage: xm block-detach <Domain> <DevId> [-f|--force]
Destroy a domain's virtual block device.
game over :(
Any idea what could be wrong ? Bug ?
Thanks in advance for your advices.
--
Sébastien
next reply other threads:[~2011-07-09 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 14:34 Sébastien Riccio [this message]
2011-07-09 17:28 ` xm/xl block-detach issue Sébastien Riccio
2011-07-10 9:05 ` Daniel Stodden
2011-07-10 12:07 ` Sébastien Riccio
2011-07-10 18:19 ` Daniel Stodden
2011-07-11 17:09 ` Sébastien Riccio
2011-07-11 18:22 ` Daniel Stodden
2011-07-11 21:37 ` Sébastien Riccio
2011-07-11 21:48 ` Daniel Stodden
2011-07-12 5:21 ` Sébastien Riccio
2011-07-12 5:47 ` Sébastien Riccio
2011-07-12 5:30 ` Sébastien Riccio
2011-07-12 5:44 ` Sébastien Riccio
2011-07-13 8:32 ` Sébastien Riccio
2011-07-13 8:44 ` Sébastien Riccio
2011-07-29 14:25 ` Konrad Rzeszutek Wilk
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=4E186702.6050601@swisscenter.com \
--to=sr@swisscenter.com \
--cc=xen-devel@lists.xensource.com \
/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.