I dunno about anywhere else.. But what I did on windows xp sp2, hosting debian and ubuntu was, i just am not using any scsi devices, neither lsi or bus drivers work for me, do not understand enough about scsi or virtualization to know whats causing this. And you can disable the scsi interface. I looked in my vmx file, and even with no scsi devices used, scsi0.present was set to true. So i set it to false. This solves my version of the problem anyhow, if you are needing to work with scsi specifically, i guess it probably doesnt. There was something else called scsi0.redo, set to "", i just removed that line entirely.

I encountered the same problem when I upgraded from VMware server 1.0.3 to 1.0.4.

I'm using a roll-my-own 2.6.24.4 kernel in a once-was-SuSE 6.0 installation.

I think the problem is related to the messages in the attached which result in false detection of additional targets on the SCSI devic.

These targets take quite a long time to be detected as offline when they are probed later in the boot process.

I have only one virtual hard drive configured.