From: "Daniel P. Berrange" <berrange@redhat.com>
To: chunhui zhao <zch.open@gmail.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: does qmp supports usb_add?
Date: Mon, 19 Apr 2010 14:00:15 +0100 [thread overview]
Message-ID: <20100419130015.GH19013@redhat.com> (raw)
In-Reply-To: <i2nacf4d72a1004190555r6a1f2331kd19787c28f939f02@mail.gmail.com>
On Mon, Apr 19, 2010 at 08:55:37PM +0800, chunhui zhao wrote:
> Thanks Dan.
> However, as I checked this command "device_add", I did not found QMP
> support it.
> I use the command:
> {"QMP": {"query-command"}}
> In the return list, I did not found the "device_add". The list is as below:
> -------------------------------------------------------------
> {"return": [{"name": "quit"}, {"name": "eject"}, {"name": "change"},
> {"name": "stop"}, {"name": "cont"}, {"name": "system_reset"}, {"name":
> "system_powerdown"}, {"name": "memsave"}, {"name": "pmemsave"},
> {"name": "migrate"}, {"name": "migrate_cancel"}, {"name": "pci_add"},
> {"name": "pci_del"}, {"name": "balloon"}, {"name": "getfd"}, {"name":
> "closefd"}, {"name": "block_passwd"}, {"name": "query-version"},
> {"name": "query-commands"}, {"name": "query-chardev"}, {"name":
> "query-block"}, {"name": "query-blockstats"}, {"name": "query-cpus"},
> {"name": "query-hpet"}, {"name": "query-kvm"}, {"name":
> "query-status"}, {"name": "query-mice"}, {"name": "query-vnc"},
> {"name": "query-name"}, {"name": "query-uuid"}, {"name":
> "query-migrate"}, {"name": "query-balloon"}]}
> -------------------------------------------------------------
>
> And on the page : http://www.linux-kvm.org/page/MonitorProtocol. I
> notice that :
> -------------------------------------------------------------
> TODO
> High Priority
> do_device_add()/do_device_del() conversions (markus)
> do_netdev_add()/do_netdev_del() conversions (markus)
> do_blockdev_add()/do_blockdev_del() conversions (markus)
> Events Grouping (luiz)
> Make qmp-shell work again (luiz)
> Self-description & High-level protocol documentation
> High-level internal documentation
> Better QObjects and QMP debug support
> -------------------------------------------------------------
>
> Cause the do_device_add is in the to_do list, does this mean it is not
> finished yet?
>
> BTW: my qemu version is 0.12.3 which I believe is the latest version.
It is not practical to use QMP with any 0.12.x version of QEMU. The
0.13.x release series will be the first where it is complete enough
to use. Current GIT code is getting reasonably complete - waiting for
netdev_add/del to be merged, and then blockdev_add/del will complete
the functionality for device hotplug use cases.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-04-19 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 13:18 does qmp supports usb_add? chunhui zhao
2010-04-16 13:28 ` Daniel P. Berrange
2010-04-19 12:55 ` chunhui zhao
2010-04-19 13:00 ` Daniel P. Berrange [this message]
2010-04-16 13:31 ` Gerd Hoffmann
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=20100419130015.GH19013@redhat.com \
--to=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=zch.open@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 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.