From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43804) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxypG-0006DZ-3v for qemu-devel@nongnu.org; Mon, 29 Aug 2011 06:12:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QxypF-0003JX-A7 for qemu-devel@nongnu.org; Mon, 29 Aug 2011 06:12:18 -0400 Received: from ssl.dlh.net ([91.198.192.8]:60881) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxypF-0003Ij-0m for qemu-devel@nongnu.org; Mon, 29 Aug 2011 06:12:17 -0400 Message-ID: <4E5B65FE.7020101@dlh.net> Date: Mon, 29 Aug 2011 12:12:14 +0200 From: Peter Lieven MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu-kvm 0.15.0 boot order not working List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, kvm@vger.kernel.org Hi, when I specify something like qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes or qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes with qemu-kvm 0.15.0 it will always directly boot from the hardrive and not from cdrom or network. is this on purpose? the behaviour was different in earlier versions. If i omit the boot=yes in the drive specification the "-boot order" parameter is working as expected. Peter