From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NIPpz-00085w-Cu for qemu-devel@nongnu.org; Wed, 09 Dec 2009 11:56:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NIPpu-00082P-KJ for qemu-devel@nongnu.org; Wed, 09 Dec 2009 11:56:26 -0500 Received: from [199.232.76.173] (port=51096 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NIPpu-00082H-DR for qemu-devel@nongnu.org; Wed, 09 Dec 2009 11:56:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51285) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NIPpt-00013Z-U1 for qemu-devel@nongnu.org; Wed, 09 Dec 2009 11:56:22 -0500 Date: Wed, 9 Dec 2009 16:56:05 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU Message-ID: <20091209165605.GT21885@redhat.com> References: <4B1C3377.1020509@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B1C3377.1020509@linux.vnet.ibm.com> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: "qemu-devel@nongnu.org" On Sun, Dec 06, 2009 at 04:43:03PM -0600, Anthony Liguori wrote: > The QEMU team is pleased to announce the availability of the 0.12.0-rc1 > release. This is the first release candidate for the 0.12.0 release. > This release is not intended for production use. > > Testing release candidates is a great way to contribute to QEMU and > improve the quality of the 0.12.0 release. > > The current plan is to release a 0.12.0-rc2 on Friday, Dec. 11th > followed by the final 0.12.0 release on Wednesday, Dec 15th. > > For this release candidate, we would appreciate as much testing and > feedback as possible, particularly the following features which have > seen a lot of activity since the 0.11.0 release: > > - live migration; especially with non-x86 and complex machine > configurations > - block device migration > - exotic x86 guests that may interact with the BIOS in special ways > - PXE booting > - SCSI disk support > - any tools that depend on parsing monitor output There's a small bug in SCSI drive hotplug where QEMU is not assigning unique block device names when you leave the name unspecified $ /home/berrange/usr/qemu-0.12/bin/qemu -vnc :1 -monitor stdio -device lsi QEMU 0.11.91 monitor - type 'help' for more information (qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi OK bus 0, unit 0 (qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi OK bus 0, unit 1 (qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi OK bus 0, unit 2 (qemu) drive_add 0:0:4 file=/home/berrange/mcdboot.img,if=scsi OK bus 0, unit 3 (qemu) info block ide1-cd0: type=cdrom removable=1 locked=0 [not inserted] floppy0: type=floppy removable=1 locked=0 [not inserted] sd0: type=floppy removable=1 locked=0 [not inserted] scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1 drv=raw encrypted=0 scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1 drv=raw encrypted=0 scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1 drv=raw encrypted=0 scsi0-hd0: type=hd removable=0 file=/home/berrange/mcdboot.img ro=1 drv=raw encrypted=0 (qemu) Notice they are all 'scsi0-hd0', instead of scsi0-hd1, scsi0-hd2, etc (Ignore the fact that i attached the same underlying file many times :-) Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|