From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingmar Schraub Subject: Re: [ANNOUNCE] qemu-kvm-0.12.1 Date: Mon, 21 Dec 2009 16:39:48 +0100 Message-ID: <4B2F96C4.1060609@eseco.de> References: <4B2E5380.1090406@redhat.com> <4B2F2E55.6050501@eseco.de> <4B2F8AAC.1080904@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Thomas Mueller , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mail.eseco.de ([212.82.249.114]:38820 "EHLO rioja.eseco.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753219AbZLUPjv (ORCPT ); Mon, 21 Dec 2009 10:39:51 -0500 In-Reply-To: <4B2F8AAC.1080904@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > On 12/21/2009 11:43 AM, Thomas Mueller wrote: >> Am Mon, 21 Dec 2009 09:14:13 +0100 schrieb Ingmar Schraub: >> >> >>> Hi, >>> >>> after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot >>> start my Windows 7 (64Bit) VM any more. I get the following error on >>> start-up: >>> >>> rom: requested regions overlap (rom vapic.bin. free=0x0000000000000600, >>> addr=0x0000000000000000) >>> rom loading failed >>> >>> I used to run it with this command line: >>> >>> qemu-system-x86_64 -k de -enable-kvm -usb -drive >>> file=/home/ingmar/kvm/windows7.qcow2,if=ide,boot=on,cache=none -net >>> nic,macaddr=DE:AD:BE:EF:28:26,vlan=1,model=e1000 -net >>> tap,script=/etc/kvm/qemu-ifup,vlan=1 -m 1024 -vnc :3 -boot c >>> >>> Any idea what is wrong here? It worked fine with all previous qemu-kvm >>> versions. >>> >> remove "boot=on" from -drive and set "-boot order=c" instead of "-boot c" >> >> is boot=on in "-drive" no longer supported or is this a bug? >> >> > > boot=on is supported, so this is a bug. Without "-drive boot=on" but with "-boot order=c" I cannot even boot from a virtio disk (-drive if=virtio). The workaround with "-boot order=c" and without "-drive boot=on" works for IDE disks, but not for virtio (another Linux VM I am running beside that Windows 7 VM). Maybe I am missing something. So I am looking forward to the next qemu-kvm-0.12.x and hope for a fix. Regards, Ingmar