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