This is a discussion on Re: problem with scsi on current vmware guest - Slackware ; Roel Kluin wrote: > Het is Thu, 10 May 2007 17:32:45 +0200 als kojak typt: > >> vmware server 1.0.3 >> slackware current >> >> in two different server I can't see LSI scsi disk but BusLogig is ok ide ...
Roel Kluin wrote:
> Het is Thu, 10 May 2007 17:32:45 +0200 als kojak typt:
>> vmware server 1.0.3
>> slackware current
>> in two different server I can't see LSI scsi disk but BusLogig is ok ide
>> disk also is ok. this happen only with kernel 126.96.36.199 on guest.
>> kernel's up to 188.8.131.52 are ok.
>> host's are running 2.6.16 up to 184.108.40.206 without problem but scsi are
>> not LSI vmware emulation.
>> this are not a big problem as I can select BusLogic instead of default
>> LSI, but I would like to know is others have see this kind of failure.
> Yes, there is a mail in linux.kernel about problems booting scsi in qemu
> on a 220.127.116.11 kernel. The mail was forwarded to the linux-scsi mailing
> list, but I haven't seen a patch as of yet.
> Fri, 11 May 2007 06:10:11 +0200, Rob Landley wrote in mail to
> linux.kernel with subject "2.6.21 broke arm scsi on qemu -M volatilepb":
>> Booting a 2.6.20 kernel under qemu works fine and gets me to a shell
>> prompt, but booting a 18.104.22.168 kernel cycles endlessly on scsi, going:
>> Loading iSCSI transport class v2.0-724. PCI: enabling device
>> 0000:00:0c.0 (0140 -> 0143) sym0: <895a> rev 0x0 at pci 0000:00:0c.0 irq
>> 0 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym0: SCSI BUS has
>> been reset.
>> scsi0 : sym-2.2.3
>> scsi 0:0:0:0: ABORT operation started. scsi 0:0:0:0: ABORT operation
>> timed-out. scsi 0:0:0:0: DEVICE RESET operation started. scsi 0:0:0:0:
>> DEVICE RESET operation timed-out. scsi 0:0:0:0: BUS RESET operation
>> started. scsi 0:0:0:0: BUS RESET operation timed-out. scsi 0:0:0:0: HOST
>> RESET operation started. sym0: SCSI BUS has been reset.
>> And so on.
>> If you're interested in reproducing this, download the most recent
>> http://landley.net/hg/firmware snapshot (links up top), run "./build.sh
>> armv4l", and when that's done "cd build" and "./run-armv4l.sh".
>> Is this a known issue? A quick google for "arm scsi 2.6.21" didn't turn
>> up anything relevant...
Now LSILogic work with just a small patch from Petr Vandrovec:
but in order to install current I have to put kernel with patched LSI
(or < 2.6.21 kernel) on current iso.
also using buslogic/ide when creating guest disk image converting later
to lsilogic is ok (change in vmx controller and vmdk controller +
geometry in case).