From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LUT8Z-00020g-3Y for qemu-devel@nongnu.org; Tue, 03 Feb 2009 16:48:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LUT8X-0001xf-40 for qemu-devel@nongnu.org; Tue, 03 Feb 2009 16:48:54 -0500 Received: from [199.232.76.173] (port=47592 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LUT8W-0001xL-Ri for qemu-devel@nongnu.org; Tue, 03 Feb 2009 16:48:52 -0500 Received: from hobi.com ([130.94.185.247]:2982) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LUT8W-0002YU-46 for qemu-devel@nongnu.org; Tue, 03 Feb 2009 16:48:52 -0500 Received: from unknown (HELO ricklap.localnet) ([68.23.60.237]) (envelope-sender ) by 130.94.185.247 (qmail-ldap-1.03) with SMTP for ; 3 Feb 2009 21:48:50 -0000 From: Rick Vernam Subject: Re: [Qemu-devel] Cutting a new QEMU release Date: Tue, 3 Feb 2009 15:48:49 -0600 References: <4988AD96.6090308@codemonkey.ws> In-Reply-To: <4988AD96.6090308@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902031548.49500.rickv@hobi.com> 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 On Tuesday 03 February 2009 2:48:22 pm Anthony Liguori wrote: > What do people think? TCG seems to be in a good place. We've got > virtio, KVM, live migration, tons of new devices, bsd-user, etc. > > We could decide to cut one by the end of the month. I'm already doing > some test work in QEMU so I can follow up with some more detailed notes > about what is working and what isn't working. That gives us some time > to decide if there's anything we need to fix before a release. > > Regards, > > Anthony Liguori -vga vmware doesn't work on either of my wxp guests, nor my w2k guest. I continue to get triple faults from any Windows XP guest at a particular point while booting, when invoked with qemu-system-x86_64. When invoked with plain qemu, it seems to work just fine. This is with or without -kqemu or -kernel-kqemu (my athlon 3700+ doesn't do kvm). I've posted about these in the past, and I don't have any additional information to add to those (ancient) discussions. I don't intend to start a discussion about them now, this is just a friendly reminder about some unresolved issues. Thanks -Rick