From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ahci drive: how to make it non-bootable?
Date: Tue, 08 May 2012 07:20:17 +0200 [thread overview]
Message-ID: <4FA8AD11.6060905@redhat.com> (raw)
In-Reply-To: <4FA818F9.90104@msgid.tls.msk.ru>
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
>
next prev parent reply other threads:[~2012-05-08 5:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 18:48 [Qemu-devel] ahci drive: how to make it non-bootable? Michael Tokarev
2012-05-08 5:20 ` Gerd Hoffmann [this message]
2012-05-08 5:45 ` Michael Tokarev
2012-05-08 6:43 ` Gerd Hoffmann
2012-05-08 17:56 ` Michael Tokarev
2012-05-09 8:02 ` Gleb Natapov
2012-05-09 16:10 ` Michael Tokarev
2012-05-10 7:33 ` Paolo Bonzini
2012-05-10 12:27 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA8AD11.6060905@redhat.com \
--to=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.