qemu 0.11.50: Guest boot failed when the drive interface is scsi

Bug #485251 reported by Pavan Naregundi
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KVM
New
Undecided
Unassigned
QEMU
Invalid
Undecided
Unassigned

Bug Description

When tried to boot the rhel5.4 guest with the below mentioned options,

/usr/local/bin/qemu-system-x86_64 -drive file=test_rhel5.4.raw,if=scsi -m 512 -enable-kvm

Boot failed with following error,
-------------------------------------
Booting from Hard Disk...
Boot failed: could not read the boot disk

Booting from Floppy...
Boot failed: could not read the boot disk

Booting from CD-Rom...
Boot failed: could not read from CDROM (code 0003)
No bootable device.
--------------------------------------

This guest was installed with following options,
# /usr/local/bin/qemu-system-x86_64 -drive file=test_rhel5.4.raw,if=scsi -net nic,model=rtl8139 -cdrom /var/RHEL5.4-Server-20090819.0-i386-DVD.iso -m 512 -enable-kvm
Warning: vlan 0 is not connected to host network
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: ORDERED queue not implemented

# uname -a
Linux mx3650b.in.ibm.com 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

Machine: x3650

Steps to reproduce:
1. Install a guest with scsi drive interface
2. After the install boot the guest with scsi interface. We can see the above mentioned boot failure.

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 485251] Re: qemu 0.11.50: Guest boot failed when the drive interface is scsi

Can you reproduce this with qemu 0.12?

Revision history for this message
Francesco Salbaroli (thewathrog) wrote :

Yes, I had the problem also using qemu 0.12.3.

Could finish installing the OS using virt-install with distribution
specific parameters for RHEL5.4+

Francesco

On Tue, Apr 13, 2010 at 4:42 PM, Dustin Kirkland
<email address hidden> wrote:
> Can you reproduce this with qemu 0.12?
>
> --
> qemu 0.11.50: Guest boot failed when the drive interface is scsi
> https://bugs.launchpad.net/bugs/485251
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Anthony Liguori (anthony-codemonkey) wrote :

QEMU does not support booting from SCSI. 0.13.0 will add support for booting from virtio in addition to IDE.

Changed in qemu:
status: New → Invalid
Revision history for this message
Gerd Hoffmann (kraxel-redhat) wrote :

Oh, scsi boot actually works.
You need 0.12.4+ or unstable.
Also http://www.lsi.com/DistributionSystem/AssetDocument/files/support/ssp/sdms/Bios/lsi_bios.zip
Unpack the downloaded zip to get the option rom.
Then boot qemu with -option-rom 8xx_64.rom

Revision history for this message
Anthony Liguori (anthony-codemonkey) wrote :

Wow, I'm amazed that works. That said, it doesn't look like that blob is redistributable.

Revision history for this message
Maraschin (carlo-maraschin) wrote :

Hello,

Is there any plans to fix this issue?

lsi_scsi: error: ORDERED queue not implemented
lsi_scsi: error: Unimplemented message 0x0d
kvm: /build/buildd/qemu-kvm-0.12.5+noroms/hw/lsi53c895a.c:596: lsi_reselect: Assertion `s->current == ((void *)0)' failed.

I've tried with qemu-kvm: 012.4 and
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008 Fabrice Bellard

uname -a
Linux overkill 2.6.35-22-server #33-Ubuntu SMP Sun Sep 19 20:48:58 UTC 2010 x86_64 GNU/Linux

I get this error all the time!
If I start to have intensive I/O (like copy really large files), it just crashes!

/Carlo

Revision history for this message
Michael Tokarev (mjt+launchpad-tls) wrote :

The crashes were most likely fixed by commit e8637c9013609271772cc0c3436cb1240cd6b034 , which is a part of 0.13 and while it applies to 0.12 just fine, it didn't went into 0.12-stable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.