From: Anthony Liguori <anthony@codemonkey.ws>
To: Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
Stefano.Stabellini@eu.citrix.com, julian.pidancet@citrix.com
Subject: Re: [Qemu-devel] Qemu disaggregation in Xen environment
Date: Mon, 05 Mar 2012 16:20:56 -0600 [thread overview]
Message-ID: <4F553C48.8070902@codemonkey.ws> (raw)
In-Reply-To: <4F4CBE85.5000006@citrix.com>
On 02/28/2012 05:46 AM, Julien Grall wrote:
> Hello,
>
> In the current model, only one instance of qemu is running for each running HVM
> domain.
>
> We are looking at disaggregating qemu to have, for example, an instance to
> emulate only
> network controllers, another to emulate block devices, etc...
Why would you want to do this?
Regards,
Anthony Liguori
>
> Multiple instances of qemu would run for a single Xen domain. Each one would handle
> a subset of the hardware.
>
> Has someone already looked at it and potentially already submitted code for qemu ?
> The purpose of this e-mail is to start a discussion and gather opinions on how the
> qemu developers community would like to see it implemented.
>
> A couple of questions comes to mind:
>
> 1) How hard would it be to untangle "machine" specific (PC hardware) emulation
> from "device" specific emulation (PCI devices) ?
>
> 2) How can we achieve disaggregation from a configuration point of view. Currently,
> Xen toolstack starts qemu, and tells qemu which device to emulate using the command
> line. I've heard about a project for creating machine description configuration
> files
> for QEMU which could help greatly in dividing up which hardware to emulate in which
> instance of qemu. What is the status of this project ?
>
> Thank you for your answers,
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
Stefano.Stabellini@eu.citrix.com, julian.pidancet@citrix.com
Subject: Re: Qemu disaggregation in Xen environment
Date: Mon, 05 Mar 2012 16:20:56 -0600 [thread overview]
Message-ID: <4F553C48.8070902@codemonkey.ws> (raw)
In-Reply-To: <4F4CBE85.5000006@citrix.com>
On 02/28/2012 05:46 AM, Julien Grall wrote:
> Hello,
>
> In the current model, only one instance of qemu is running for each running HVM
> domain.
>
> We are looking at disaggregating qemu to have, for example, an instance to
> emulate only
> network controllers, another to emulate block devices, etc...
Why would you want to do this?
Regards,
Anthony Liguori
>
> Multiple instances of qemu would run for a single Xen domain. Each one would handle
> a subset of the hardware.
>
> Has someone already looked at it and potentially already submitted code for qemu ?
> The purpose of this e-mail is to start a discussion and gather opinions on how the
> qemu developers community would like to see it implemented.
>
> A couple of questions comes to mind:
>
> 1) How hard would it be to untangle "machine" specific (PC hardware) emulation
> from "device" specific emulation (PCI devices) ?
>
> 2) How can we achieve disaggregation from a configuration point of view. Currently,
> Xen toolstack starts qemu, and tells qemu which device to emulate using the command
> line. I've heard about a project for creating machine description configuration
> files
> for QEMU which could help greatly in dividing up which hardware to emulate in which
> instance of qemu. What is the status of this project ?
>
> Thank you for your answers,
>
>
next prev parent reply other threads:[~2012-03-05 22:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 11:46 [Qemu-devel] Qemu disaggregation in Xen environment Julien Grall
2012-02-28 11:46 ` Julien Grall
2012-03-05 22:06 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-03-05 22:06 ` Ian Campbell
2012-03-12 13:42 ` [Qemu-devel] " Julien Grall
2012-03-12 13:42 ` Julien Grall
2012-03-05 22:20 ` Anthony Liguori [this message]
2012-03-05 22:20 ` Anthony Liguori
2012-03-05 22:53 ` [Qemu-devel] " Stefano Stabellini
2012-03-05 22:53 ` Stefano Stabellini
2012-03-06 1:45 ` [Qemu-devel] " Anthony Liguori
2012-03-06 1:45 ` Anthony Liguori
2012-03-06 8:22 ` [Qemu-devel] " Markus Armbruster
2012-03-06 8:22 ` Markus Armbruster
2012-03-06 15:11 ` [Qemu-devel] " Anthony Liguori
2012-03-06 15:11 ` Anthony Liguori
2012-03-12 13:17 ` [Qemu-devel] " Stefano Stabellini
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=4F553C48.8070902@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=julian.pidancet@citrix.com \
--cc=julien.grall@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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.