From: Fam Zheng <famz@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] QEMU not honouring bootorder
Date: Mon, 11 Dec 2017 19:41:29 +0800 [thread overview]
Message-ID: <20171211114129.GC3350@lemon> (raw)
In-Reply-To: <b630fe8c-6905-6743-d29d-ded450d5d10b@redhat.com>
On Thu, 12/07 13:10, Michal Privoznik wrote:
> Dear list,
>
> I've encountered the following problem. I have two disks:
>
> /var/lib/libvirt/images/fedora.qcow2 (which contains OS)
> /dev/sde (iSCSI dummy disk just for testing)
>
> Now, when I configure QEMU to start with both of them, QEMU/Seabios
> tries to boot from /dev/sde which fails obviously. Even setting
> bootorder does not help. Here's my command line:
>
> qemu-system-x86_64 \
> -boot menu=on,strict=on \
> -device lsi,id=scsi0,bus=pci.0 \
> -drive file=/var/lib/libvirt/images/fedora.qcow2,format=qcow2,if=none,id=drive-scsi0 \
> -device scsi-hd,bus=scsi0.0,drive=drive-scsi0,bootindex=1 \
> -drive file=/dev/sde,format=raw,if=none,id=drive-scsi1 \
> -device scsi-block,bus=scsi0.0,drive=drive-scsi1,bootindex=2
>
> It was found that if 'drive-scsi1' is scsi-hd instead of scsi-block
> everything works as expected and I can boot my guest successfully.
Does it help if you add SCSI level ordering with "lun={0,1},channel=0,scsi-id=0"
for both devices?
Fam
next prev parent reply other threads:[~2017-12-11 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 12:10 [Qemu-devel] QEMU not honouring bootorder Michal Privoznik
2017-12-11 10:20 ` Michal Privoznik
2017-12-11 11:41 ` Fam Zheng [this message]
2017-12-11 12:14 ` Michal Privoznik
2017-12-13 21:21 ` Paolo Bonzini
2017-12-14 8:48 ` Michal Privoznik
2017-12-14 11:28 ` Paolo Bonzini
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=20171211114129.GC3350@lemon \
--to=famz@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-block@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).