From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:50800)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1SRcqW-0005Lo-LA
	for qemu-devel@nongnu.org; Tue, 08 May 2012 01:20:25 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1SRcqU-0001dH-4Y
	for qemu-devel@nongnu.org; Tue, 08 May 2012 01:20:24 -0400
Received: from mx1.redhat.com ([209.132.183.28]:10131)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1SRcqT-0001d4-Rn
	for qemu-devel@nongnu.org; Tue, 08 May 2012 01:20:22 -0400
Message-ID: <4FA8AD11.6060905@redhat.com>
Date: Tue, 08 May 2012 07:20:17 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <4FA818F9.90104@msgid.tls.msk.ru>
In-Reply-To: <4FA818F9.90104@msgid.tls.msk.ru>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] ahci drive: how to make it non-bootable?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>

On 05/07/12 20:48, Michael Tokarev wrote:
> 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?

bootindex=1 for virtio
bootindex=2 for ahci

ordering in the boot menu then should be virtio first, ahci second, then
everything else (cdrom, nic, ..).

cheers,
  Gerd

> 
> Thanks,
> 
> /mjt
>