Hi,
when I create a vmdk using the standard way "add ne hardware, hard disk, SCSI, blabla", and then set the size of the virtual disk to be above, say, 15 GBytes, it crashes. Not every time, but often.
NEVER any crash when it's below 10 GB.
The host is either 2k3 x64 std. or XP x64. Intel Xeon 5050 2core, 2 CPU, 8 G RAM, on Tyan S5380.
Same error on the BSOD on both OSes, 2k3 and XP, -
0xd1 - storport.sys has crashed. The created file ends where the crash occured- I tried a 25 Gig file, and short before the end it crashed, leaving an 21 Gig file.
I found a way I might avoid it. I can tell the VMWare to split the big files in 2 GB chunks, the option is on the "create file" page during the assisted setup. It shouldn't be a big problem I guess- anybody an idea how much slower it may be ? It would be only for file server purposes- I plan to host the OS on C on a 8 GB file, drive D on another 8 GB file, and the 30 GB file area on a 15*2 file collection ;-).
On the other hand, what can I do to get rid of the dreaded 0xD1 stop ?
Those avoiding- strategies alway leave me with the strange feeling of "it might return EVERY day, and then, it might be in an IMPORTANT situation". These 3 Hosts are production- machines, each holds 8 VMS, of which 3 do real work, and 5 are of the low-CPU-power-demanding type.
It's an LSI SCSI controller, 1030 chip (Model 22320-R), and I run everything on an external raid (Easyraid Q16+, full with 16 250 GB Seagate Sata drives).
I found an MS patch but did not try that yet. It does describe some special situations of enabling and disabling drives so I felt it might not apply (but I will try on monday, just in case it fixes something which causes my problems but does not tell about that 
).
Kind regards,
Carsten