From: Julien Grall <julien.grall@citrix.com>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, julian.pidancet@citrix.com,
Stefano.Stabellini@eu.citrix.com
Subject: [Qemu-devel] Qemu disaggregation in Xen environment
Date: Tue, 28 Feb 2012 11:46:13 +0000 [thread overview]
Message-ID: <4F4CBE85.5000006@citrix.com> (raw)
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...
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 reply other threads:[~2012-02-28 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 11:46 Julien Grall [this message]
2012-03-05 22:06 ` [Qemu-devel] [Xen-devel] Qemu disaggregation in Xen environment Ian Campbell
2012-03-12 13:42 ` Julien Grall
2012-03-05 22:20 ` [Qemu-devel] " Anthony Liguori
2012-03-05 22:53 ` Stefano Stabellini
2012-03-06 1:45 ` Anthony Liguori
2012-03-06 8:22 ` Markus Armbruster
2012-03-06 15:11 ` Anthony Liguori
2012-03-12 13:17 ` 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=4F4CBE85.5000006@citrix.com \
--to=julien.grall@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=julian.pidancet@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).