From: William Dauchy <william@gandi.net>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, imain@redhat.com, qemu-devel@nongnu.org,
William Dauchy <william@gandi.net>
Subject: Re: [Qemu-devel] device_del id missing after blockdev-add
Date: Tue, 25 Feb 2014 12:20:12 +0100 [thread overview]
Message-ID: <20140225112012.GA5268@gandi.net> (raw)
In-Reply-To: <20140224153432.GE23185@stefanha-thinkpad.hitronhub.home>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Feb24 16:34, Stefan Hajnoczi wrote:
> Also, it should probably be 'removable':true?
oh true, did not mention this was a boolean
> You forgot to give the device an ID. Could that be the problem here?
yup I spotted that some days after and forgot to write an answer here.
that's solved the issue.
I was indeed confused with drive/id attributes.
Thanks for you answer, I thought it my issue was drowned into the ML.
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2014-02-25 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:36 [Qemu-devel] device_del id missing after blockdev-add William Dauchy
2014-02-24 15:34 ` Stefan Hajnoczi
2014-02-25 11:20 ` William Dauchy [this message]
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=20140225112012.GA5268@gandi.net \
--to=william@gandi.net \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).