qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [RFC][PATCH 00/10] virtagent: host/guest RPC communicat


From: Andrew Beekhof
Subject: [Qemu-devel] Re: [RFC][PATCH 00/10] virtagent: host/guest RPC communication agent
Date: Mon, 25 Oct 2010 11:46:07 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Thunderbird/3.1.4

On 10/23/2010 04:41 PM, Michael Roth wrote:
On 10/23/2010 06:31 AM, Andrew Beekhof wrote:
On 10/22/2010 08:45 PM, Michael Roth wrote:

the ability to deploy to guests which may not support virtio-serial,
which currently rules Matahari out.

Possibly there has been some miscommunication, Matahari does not require
virtio-serial.

It will be possible to configure Matahari to use virtio-serial if it
exists, but like Virtproxy it can also be used over a regular IP network
(yes, its transparent to clients too).


Sorry, I'm aware of this but wasn't very clear here. I was speaking in
the context of our cloud, or other environments where there isn't any
network access between the host and the guest. This essentially leaves
virtio-serial and isa-serial, and a large number of our guests don't
support the former.

Well again, Matahari has no concept of what transport is being used. That's completely hidden from us by Qpid behind a layer of abstraction.

So what we're really talking about is the difficulty in adding a new transport to Qpid... and if the interface is anything like virtio-serial or a standard serial port, we're talking about a few hundred lines and "a couple of days".

Not exactly a major barrier considering the pay-off would be a single set of agents.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]