Hi ,
there`s probably another bug in VMWare LSI emulated scsi controller, recent
solaris builds crash the vmware process on boot (iirc, it was a regression
introduced in snv_63).
from what i`ve read so far it happens during scsi device initialization from
withing mpt driver, but unfortunately the mpt driver in solaris seems to be
closed source.
since there i found no more information within vmware community or within
opensolaris community about details of this bug - maybe anybody here knows
what`s causing this crash and if it can perhaps be reproduced from within linux
?
i`m even unsure if some hacker could exploit this to break out of a virtual
machine !? i`m running VMs in dmz setup.....
regards
roland
>[PATCH 1/2] fusion : shost max_id not set in VMWare guest os
>
>In vmware guest os with emulated LSI 53c1030, the port facts config page is
>not having MaxDevices initialized to 16 devices. Instead its set to zero.
>Thereforewhen driver loads, no devices are scanned for from scsi_scan_host.
>Prior to the3.04.04 driver, shost max_id was set to hard coded value \
>MPT_MAX_SCSI_DEVICES. After that release, support for greater than 255 targets
>was \
>added, and the driver was taking the target count from the port facts instead.
> With \
>this patch we will restore the hard coded values for SPI, but at the same time
>use \
>the settingsneeded for SAS and Fibre Channel.
>
>Signed-off-by: Eric Moore <[EMAIL PROTECTED]>
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
Mehr Infos unter http://produkte.web.de/club/?mc=021131
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
