* [Qemu-devel] QEMU not honouring bootorder
@ 2017-12-07 12:10 Michal Privoznik
2017-12-11 10:20 ` Michal Privoznik
2017-12-11 11:41 ` Fam Zheng
0 siblings, 2 replies; 7+ messages in thread
From: Michal Privoznik @ 2017-12-07 12:10 UTC (permalink / raw)
To: QEMU Developers; +Cc: qemu-block
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.
Michal
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] QEMU not honouring bootorder
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
1 sibling, 0 replies; 7+ messages in thread
From: Michal Privoznik @ 2017-12-11 10:20 UTC (permalink / raw)
To: QEMU Developers; +Cc: qemu-block
On 12/07/2017 01:10 PM, Michal Privoznik wrote:
> Dear list,
>
Ping. Is there anything I can help you with to have this sorted out?
Michal
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] QEMU not honouring bootorder
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
2017-12-11 12:14 ` Michal Privoznik
1 sibling, 1 reply; 7+ messages in thread
From: Fam Zheng @ 2017-12-11 11:41 UTC (permalink / raw)
To: Michal Privoznik; +Cc: QEMU Developers, qemu-block
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
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Qemu-devel] QEMU not honouring bootorder
2017-12-11 11:41 ` Fam Zheng
@ 2017-12-11 12:14 ` Michal Privoznik
2017-12-13 21:21 ` Paolo Bonzini
0 siblings, 1 reply; 7+ messages in thread
From: Michal Privoznik @ 2017-12-11 12:14 UTC (permalink / raw)
To: Fam Zheng; +Cc: QEMU Developers, qemu-block
On 12/11/2017 12:41 PM, Fam Zheng wrote:
> 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?
Setting lun helps. On the other hand, I had to change from LSI
controller to virtio-scsi as LSI doesn't support more than 1 LUNs.
Michal
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Qemu-devel] QEMU not honouring bootorder
2017-12-11 12:14 ` Michal Privoznik
@ 2017-12-13 21:21 ` Paolo Bonzini
2017-12-14 8:48 ` Michal Privoznik
0 siblings, 1 reply; 7+ messages in thread
From: Paolo Bonzini @ 2017-12-13 21:21 UTC (permalink / raw)
To: Michal Privoznik, Fam Zheng; +Cc: QEMU Developers, qemu-block
On 11/12/2017 13:14, Michal Privoznik wrote:
>>> 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?
> Setting lun helps. On the other hand, I had to change from LSI
> controller to virtio-scsi as LSI doesn't support more than 1 LUNs.
Does it help to use virtio-scsi and keep the default assignment?
Thanks,
Paolo
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Qemu-devel] QEMU not honouring bootorder
2017-12-13 21:21 ` Paolo Bonzini
@ 2017-12-14 8:48 ` Michal Privoznik
2017-12-14 11:28 ` Paolo Bonzini
0 siblings, 1 reply; 7+ messages in thread
From: Michal Privoznik @ 2017-12-14 8:48 UTC (permalink / raw)
To: Paolo Bonzini, Fam Zheng; +Cc: QEMU Developers, qemu-block
On 12/13/2017 10:21 PM, Paolo Bonzini wrote:
> On 11/12/2017 13:14, Michal Privoznik wrote:
>>>> 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?
>> Setting lun helps. On the other hand, I had to change from LSI
>> controller to virtio-scsi as LSI doesn't support more than 1 LUNs.
>
> Does it help to use virtio-scsi and keep the default assignment?
Yes. If I s/lsi/virtio-scsi-pci/ on the cmd line it does help too.
Michal
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Qemu-devel] QEMU not honouring bootorder
2017-12-14 8:48 ` Michal Privoznik
@ 2017-12-14 11:28 ` Paolo Bonzini
0 siblings, 0 replies; 7+ messages in thread
From: Paolo Bonzini @ 2017-12-14 11:28 UTC (permalink / raw)
To: Michal Privoznik, Fam Zheng; +Cc: QEMU Developers, qemu-block
On 14/12/2017 09:48, Michal Privoznik wrote:
> On 12/13/2017 10:21 PM, Paolo Bonzini wrote:
>> On 11/12/2017 13:14, Michal Privoznik wrote:
>>>>> 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?
>>> Setting lun helps. On the other hand, I had to change from LSI
>>> controller to virtio-scsi as LSI doesn't support more than 1 LUNs.
>>
>> Does it help to use virtio-scsi and keep the default assignment?
>
> Yes. If I s/lsi/virtio-scsi-pci/ on the cmd line it does help too.
Cool, then it's an lsi bug. :)
Paolo
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-12-14 11:28 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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).