From: Jan Marten Simons <marten@xtal.rwth-aachen.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interest in hardware plugin functionality
Date: Tue, 10 Jan 2006 19:01:24 +0100 [thread overview]
Message-ID: <43C3F674.4030202@xtal.rwth-aachen.de> (raw)
In-Reply-To: <20060110120109.GA17360@xi.wantstofly.org>
Lennert Buytenhek wrote:
>I think the biggest problem would be that a lot of operating systems
>don't support hotplug PCI.
>
>
>
I think Michael's idea was rather to select the hardware to use during
qemu startup rather then to change it while the system is up and
runnning. Therefore hotplugging would not be an issue.
To give some feedback as well, I like the idea of dynamic hardware as
qemu can become even more versatile than it is right now.
With regards,
Jan
next prev parent reply other threads:[~2006-01-10 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 1:38 [Qemu-devel] Interest in hardware plugin functionality Andre Pech
2006-01-10 6:21 ` Michael Renzmann
2006-01-10 12:01 ` Lennert Buytenhek
2006-01-10 17:41 ` Andre Pech
2006-01-10 18:01 ` Jan Marten Simons [this message]
2006-01-10 18:36 ` Anthony Liguori
2006-01-11 0:14 ` Andre Pech
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=43C3F674.4030202@xtal.rwth-aachen.de \
--to=marten@xtal.rwth-aachen.de \
--cc=qemu-devel@nongnu.org \
/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).