From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC for new features
Date: Sat, 10 Jul 2004 16:03:04 +0200 [thread overview]
Message-ID: <40EFF718.7020304@bellard.org> (raw)
In-Reply-To: <40EFEADE.40902@bellard.org>
About the new features: none of them will be for the upcoming 0.6.0
release. Maybe for 0.6.1.
Some comments:
- The old console will still be available with a command line option.
- The disk images will support both free sector compression (as cow
images) and "read-only" zlib based block compression, so that the
FreeOSZoo disk images do not need to be decompressed. QEMU itself will
never store compressed blocks as it is more complicated and less useful.
- The disk images will support AES based encryption.
- There will be no plugin system in the near future. Such systems are
mainly useful for closed source project, which QEMU is not. Moreover, as
in ffmpeg, I don't want to bother about binary compatibility and API
stability at this stage of the project.
- The first version of config file will just contain the same as the
command line options. Then someday there will be more options to add new
hardware dynamically and to change some of its properties... but it will
never use XML !
Fabrice.
next prev parent reply other threads:[~2004-07-10 14:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 1:59 [Qemu-devel] (Before) RFC for new features Natalia Portillo
2004-07-10 15:37 ` Hetz Ben Hamo
2004-07-09 17:23 ` Natalia Portillo
2004-07-09 17:32 ` Antony T Curtis
2004-07-09 17:57 ` Natalia Portillo
2004-07-09 20:42 ` Jim C. Brown
2004-07-10 2:41 ` Natalia Portillo
2004-07-10 13:10 ` Fabrice Bellard
2004-07-10 14:03 ` Fabrice Bellard [this message]
2004-07-10 14:47 ` [Qemu-devel] " Antony T Curtis
2004-07-10 14:57 ` Fabrice Bellard
2004-07-10 20:53 ` [Qemu-devel] (Before) " Hetz Ben Hamo
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 20:50 [Qemu-devel] " Natalia Portillo
2004-07-08 22:48 ` Natalia Portillo
2004-07-09 19:04 ` Jocelyn Mayer
2004-07-09 19:28 ` Natalia Portillo
2004-07-08 19:19 Thomas Munn
2004-07-09 10:02 ` Johannes Schindelin
2004-07-09 10:34 ` Julian Seward
2004-07-08 18:14 Fabrice Bellard
2004-07-08 18:54 ` Antony T Curtis
2004-07-08 19:36 ` Jim C. Brown
2004-07-08 20:31 ` Jernej Simončič
2004-07-08 21:04 ` Jim C. Brown
2004-07-08 22:37 ` Jernej Simončič
2004-07-08 22:57 ` Jim C. Brown
2004-07-08 19:45 ` Jocelyn Mayer
2004-07-08 19:00 ` Karel Gardas
2004-07-08 21:44 ` vaise
2004-07-08 19:30 ` Jean-Michel POURE
2004-07-08 19:48 ` Brad Watson
2004-07-08 21:37 ` Jan Dittmer
2004-07-08 22:24 ` malc
2004-07-08 19:35 ` Jim C. Brown
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=40EFF718.7020304@bellard.org \
--to=fabrice@bellard.org \
--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).