From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46954) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRdF6-00088k-Vb for qemu-devel@nongnu.org; Tue, 08 May 2012 01:45:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRdF5-0002GE-8K for qemu-devel@nongnu.org; Tue, 08 May 2012 01:45:48 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:55017) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRdF5-0002Fj-1K for qemu-devel@nongnu.org; Tue, 08 May 2012 01:45:47 -0400 Message-ID: <4FA8B2FE.60303@msgid.tls.msk.ru> Date: Tue, 08 May 2012 09:45:34 +0400 From: Michael Tokarev MIME-Version: 1.0 References: <4FA818F9.90104@msgid.tls.msk.ru> <4FA8AD11.6060905@redhat.com> In-Reply-To: <4FA8AD11.6060905@redhat.com> 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel On 08.05.2012 09:20, Gerd Hoffmann wrote: > 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 -drive file=winguest.raw,if=virtio,bootindex=1 -- this does not work: qemu: -drive file=winguest.raw,if=virtio,bootindex=1: Invalid parameter 'bootindex' I understand that I probably can replace this single -drive with 3 parameters -- -device virtio-blk-pci, -drive if=none, and -device ide-drive. But this is already too much for ahci, so now I'm forced to use the same very long syntax for virtio and ide too? Is there a saner way? Also, still, the question in the $subj: how to make the ahci drive non-bootable? > 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