On 03/09/2011 07:55 AM, Avi Kivity wrote:
On 03/09/2011 03:51 PM, Anthony Liguori wrote:
{ execute: 'write-keystore' arguments: { 'key': 'foo', 'value':
'bar' } }
This is coming from the guest?
Yes.
So what about:
{ 'KeyStore': { '*foo': 'str', '*otherkey': 'str' } }
[ 'guest-write-keys
On 03/09/2011 03:51 PM, Anthony Liguori wrote:
{ execute: 'write-keystore' arguments: { 'key': 'foo', 'value':
'bar' } }
This is coming from the guest?
Yes.
So what about:
{ 'KeyStore': { '*foo': 'str', '*otherkey': 'str' } }
[ 'guest-write-keystore', { 'keystore': 'KeyStore' }, 'none' ]
On 03/09/2011 07:14 AM, Avi Kivity wrote:
On 03/09/2011 03:12 PM, Anthony Liguori wrote:
On 03/09/2011 02:51 AM, Avi Kivity wrote:
On 03/08/2011 09:19 PM, Anthony Liguori wrote:
Both the guest and the management agent (and both can listen for
events). I don't see why guest->qemu RPC is problem
On 03/09/2011 07:14 AM, Avi Kivity wrote:
On 03/09/2011 03:12 PM, Anthony Liguori wrote:
On 03/09/2011 02:51 AM, Avi Kivity wrote:
On 03/08/2011 09:19 PM, Anthony Liguori wrote:
Both the guest and the management agent (and both can listen for
events). I don't see why guest->qemu RPC is proble
On 03/09/2011 03:12 PM, Anthony Liguori wrote:
On 03/09/2011 02:51 AM, Avi Kivity wrote:
On 03/08/2011 09:19 PM, Anthony Liguori wrote:
Both the guest and the management agent (and both can listen for
events). I don't see why guest->qemu RPC is problematic for
migration - at least when qemu t
On 03/09/2011 02:51 AM, Avi Kivity wrote:
On 03/08/2011 09:19 PM, Anthony Liguori wrote:
Both the guest and the management agent (and both can listen for
events). I don't see why guest->qemu RPC is problematic for
migration - at least when qemu terminates it.
If it's terminated in QEMU, it'
On 03/08/2011 09:19 PM, Anthony Liguori wrote:
Both the guest and the management agent (and both can listen for
events). I don't see why guest->qemu RPC is problematic for
migration - at least when qemu terminates it.
If it's terminated in QEMU, it's fine, but then it's not QMP anymore.
Le
On 03/08/2011 11:44 AM, Avi Kivity wrote:
I'm not sure I see this as all that critical though. I sort of like
the idea of it being transparent to the client whether a guest agent
implements a command or QEMU does.
A qemu command is guaranteed to be executed faithfully, modulo bugs
and runt
On 03/08/2011 05:03 PM, Anthony Liguori wrote:
We may want to use a different way of separating the namespaces -
enacapsulation:
{
'command': 'guest-command',
arguments: {
'command': 'read-file',
'arguments': {
'path': '/var/log/messages'
}
}
}
This serves to dec
On 03/08/2011 08:52 AM, Avi Kivity wrote:
On 03/08/2011 04:38 PM, Anthony Liguori wrote:
http://wiki.qemu.org/Features/QAPI/GuestAgent
Nice. A couple of remarks.
We may want to use a different way of separating the namespaces -
enacapsulation:
{
'command': 'guest-command',
argument
On 03/08/2011 04:38 PM, Anthony Liguori wrote:
http://wiki.qemu.org/Features/QAPI/GuestAgent
Nice. A couple of remarks.
We may want to use a different way of separating the namespaces -
enacapsulation:
{
'command': 'guest-command',
arguments: {
'command': 'read-file',
'arg
On 03/08/2011 08:17 AM, Avi Kivity wrote:
No, I'm in the process of writing up my latest proposal.
The idea is pretty simple. QAPI generates code for libqmp that takes
native arguments for a command and generates a QObject. It also
generates code for QEMU that takes a QObject and generates n
On 03/08/2011 08:17 AM, Avi Kivity wrote:
On 03/08/2011 04:10 PM, Anthony Liguori wrote:
On 03/08/2011 08:00 AM, Avi Kivity wrote:
On 03/08/2011 03:54 PM, Anthony Liguori wrote:
(and gah, do we really need a vfs/rpc in qemu?)
Fun, eh :-) Unfortunately, our friends at VMware provide a
Vix
On 03/08/2011 04:10 PM, Anthony Liguori wrote:
On 03/08/2011 08:00 AM, Avi Kivity wrote:
On 03/08/2011 03:54 PM, Anthony Liguori wrote:
(and gah, do we really need a vfs/rpc in qemu?)
Fun, eh :-) Unfortunately, our friends at VMware provide a
VixVM_CopyFileFromGuestToHost API so there's a
On 03/08/2011 08:00 AM, Avi Kivity wrote:
On 03/08/2011 03:54 PM, Anthony Liguori wrote:
(and gah, do we really need a vfs/rpc in qemu?)
Fun, eh :-) Unfortunately, our friends at VMware provide a
VixVM_CopyFileFromGuestToHost API so there's an expectation that we
provide a similar interfa
On 03/08/2011 03:54 PM, Anthony Liguori wrote:
(and gah, do we really need a vfs/rpc in qemu?)
Fun, eh :-) Unfortunately, our friends at VMware provide a
VixVM_CopyFileFromGuestToHost API so there's an expectation that we
provide a similar interface.
Yes, but do we have to terminate it
On 03/08/2011 07:45 AM, Avi Kivity wrote:
On 03/08/2011 03:35 PM, Anthony Liguori wrote:
On 03/08/2011 05:12 AM, Avi Kivity wrote:
On 03/07/2011 05:59 PM, Anthony Liguori wrote:
How do async commands work? You mentioned them when talking about
QAPI but it's not obvious to me that there is a
On 03/08/2011 03:35 PM, Anthony Liguori wrote:
On 03/08/2011 05:12 AM, Avi Kivity wrote:
On 03/07/2011 05:59 PM, Anthony Liguori wrote:
How do async commands work? You mentioned them when talking about
QAPI but it's not obvious to me that there is any "native" support for
async commands?
A
On 03/08/2011 05:12 AM, Avi Kivity wrote:
On 03/07/2011 05:59 PM, Anthony Liguori wrote:
How do async commands work? You mentioned them when talking about
QAPI but it's not obvious to me that there is any "native" support for
async commands?
Async commands are interesting..
Would there be
On 03/07/2011 05:59 PM, Anthony Liguori wrote:
How do async commands work? You mentioned them when talking about
QAPI but it's not obvious to me that there is any "native" support for
async commands?
Async commands are interesting..
Would there be anything in them other than starting each
On Mon, Mar 7, 2011 at 8:59 PM, Anthony Liguori wrote:
> On 03/07/2011 09:08 AM, Stefan Hajnoczi wrote:
>>
>> The signals and slots magic makes sense when looking at the patches,
>> but I wasn't confident about their semantics just by reading the
>> documentation. I had a vague idea about why the
On 03/07/2011 09:08 AM, Stefan Hajnoczi wrote:
The signals and slots magic makes sense when looking at the patches,
but I wasn't confident about their semantics just by reading the
documentation. I had a vague idea about why the Event struct is
needed but didn't fully understand. Perhaps it's j
On 03/07/2011 09:08 AM, Stefan Hajnoczi wrote:
On Mon, Mar 7, 2011 at 1:22 AM, Anthony Liguori wrote:
More information about QAPI can be found on the wiki:
http://wiki.qemu.org/Features/QAPI
Thanks for the good documentation. A few thoughts:
A "Naming Conventions" section would be a helpful
On Mon, Mar 7, 2011 at 1:22 AM, Anthony Liguori wrote:
> More information about QAPI can be found on the wiki:
>
> http://wiki.qemu.org/Features/QAPI
Thanks for the good documentation. A few thoughts:
A "Naming Conventions" section would be a helpful summary of the
different entities that .json
This is the first round of QAPI. This lays all the basic ground work for QAPI
including a client library, new server, and new signal/slot mechanism.
The QAPI development branch contains conversions of every 0.14 QMP command and
also converts all possible HMP commands to use the QMP versions of th
25 matches
Mail list logo
