From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:43856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRSz1-0004Pb-Ap for qemu-devel@nongnu.org; Mon, 07 May 2012 14:48:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRSyz-0006rp-8O for qemu-devel@nongnu.org; Mon, 07 May 2012 14:48:30 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:35577) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRSyz-0006p8-11 for qemu-devel@nongnu.org; Mon, 07 May 2012 14:48:29 -0400 Message-ID: <4FA818F9.90104@msgid.tls.msk.ru> Date: Mon, 07 May 2012 22:48:25 +0400 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] ahci drive: how to make it non-bootable? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel I'm trying to experiment with ahci, but can't even get my win guest to install drivers for it. My usualy procedure is, for an existing guest, to add a dummy drive of required type, boot the guest, let it to recognize the new device and to install drivers needed for it, shut it down and change boot drive to the one of required type. This worked fine so far, eg, for virtio or scsi. But now I can't use the same technique for ahci. qemu .. -drive file=winguest.raw,if=virtio \ -device ahci,id=a \ -drive file=dummy.raw,id=d,if=none \ -device ide-disk,bus=a.0,drive=d,bootindex=X Now, no matter what I use for the bootindex parameter, the guest _always_ boots off a dummy ahci drive. Even using bootindex=-1 or some huge value, the guest still boots from ahci. The only workaround I found so far is to boot using -boot menu=on, and manually choose the second entry (which is the virtio image), but obviously this is not good at all. How to let the guest to boot from the virtio drive? Thanks, /mjt