|
From: | Anthony Liguori |
Subject: | [Qemu-devel] Re: [RFC][PATCH v1 08/12] qemu-char: add qmp_proxy chardev |
Date: | Mon, 28 Mar 2011 12:45:46 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8 |
On 03/25/2011 05:11 PM, Michael Roth wrote:
Why are these options required?The qmp_proxy_new() constructor expects a path to a socket it can connect() to. Not sure about telnet, but the other options are required for this. Well...server=on at least, wait=off needs to be set as well because that's the only way to have the socket chardev set the listening socket to non-block, since qmp_proxy_new() calls connect() on it before we return to the main I/O loop.Although, we probably shouldn't just silently switch out explicitly set options; an error would probably be more appropriate here.
You ought to make qmp_proxy_new() return a CharDriverState such that you can do:
qemu -device virtio-serial,chardev=foo -chardev guest-agent,id=foo Regards, Anthony Liguori
Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |