From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BjIUA-00040a-JO for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:05:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BjIU9-000406-Gw for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:05:49 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BjIU9-0003zw-CV for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:05:49 -0400 Received: from [193.252.22.28] (helo=mwinf0303.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BjIRQ-0007fu-7D for qemu-devel@nongnu.org; Sat, 10 Jul 2004 10:03:00 -0400 Received: from bellard.org (ATuileries-112-1-4-169.w81-53.abo.wanadoo.fr [81.53.133.169]) by mwinf0303.wanadoo.fr (SMTP Server) with ESMTP id 63C5A50006CC for ; Sat, 10 Jul 2004 16:02:59 +0200 (CEST) Message-ID: <40EFF718.7020304@bellard.org> Date: Sat, 10 Jul 2004 16:03:04 +0200 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] RFC for new features References: <40EFEADE.40902@bellard.org> In-Reply-To: <40EFEADE.40902@bellard.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.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.