On Wed, 2012-06-20 at 19:17 -0700, Peter Cao wrote: > Hi Ben, > > The disk became read-only when the error happens so the log was not saved. > But I have a screenshot for the error msg: > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=debian-605-32bit-buslogic-6Gmem-IO_error.png;att=2;bug=678236 > > We have not see any error with PVSCSI adapter so far. > And there is no error with debian 64bit release but only the 32bit release with large memory+buslogic. [...] So far as I can see, BusLogic has not been changed in any significant way between Linux 2.6.32 and current mainline (3.5-rc3). So unless you know better, this problem also affects mainline Linux and should be fixed there first. But what is the point of using this driver at all under VMware, when we could use vmw_pvscsi? Do you make the same SCSI devices available to the guest through both an emulated BusLogic adapter and paravirtual SCSI adapter at the same time? In that case, could the BusLogic driver detect that an adapter is actually an emulation (based on PCI subsystem vendor ID?) and ignore it because the vmw_pvscsi driver will work better? If not, isn't it a bug in VMware that it enables the BusLogic device and not the PV-SCSI device for Debian guests? Ben. -- Ben Hutchings Every program is either trivial or else contains at least one bug
Attachment:
signature.asc
Description: This is a digitally signed message part