Hi Ron,
I don't think it's paravirtual SCSI problem. More likely the deployment is not successful. Can you try a fresh deployment, have disks think eager zeroed, and do not power on after deployment? Once it's done, please verify the VMDKs. Here's what I have on my vSphere host:
# cd to VM installation directory first.
$> ls -l *-flat.vmdk
-rw------- 1 root root 17179869184 Apr 8 16:50 <VM_NAME>-flat.vmdk
-rw------- 1 root root 104857600 Apr 8 16:50 <VM_NAME>_1-flat.vmdk
$> md5sum *-flat.vmdk
a4c310c3bd78d40a326b38c9b46abd5d <VM_NAME>-flat.vmdk
f67870ca1e0eed6c79b293ec3c54960f <VM_NAME>_1-flat.vmdk
You might also want to use vmkfstools to check if there is error (vmkfstools --fix check <VM_NAME>-flat.vmdk).
If any of the above doesn't match, you should check /var/log/vmkernel.log and the vmware.log file locates with your VMDK's and see if there is error during deployment (vmware.log will be generated only after first boot).
Thanks,
Chien-Chia
