Is there a good reason the "VMware’s Paravirtual SCSI Adapter" not to use?
I would like to use this adapter for every VMs data (not boot partitions) partitions.
Reason: Have the hole environment identitical.
I heard only one disadvantage: VMs with low I/O will have no performance gains over the usually used SCSI adapter.
Thanks for your opinion!
Simon
Is there a good reason the "VMware's Paravirtual SCSI Adapter" not to use?
If you don't need FT, I don't see any reason right now.
see http://blog.scottlowe.org/2009/07/05/another-reason-not-to-use-pvscsi-or-vmxnet3/
I would like to use this adapter for every VMs data (not boot partitions) partitions.
I guess you know that, anyway.
from the http://www.vmware.com/support/vsphere4/doc/vsp_esx40_u1_rel_notes.html
Enhanced VMware Paravirtualized SCSI Support
Support for boot disk devices attached to a Paravirtualized SCSI ( PVSCSI) adapter has been added for Windows 2003 and 2008 guest operating systems...
André
Is there a good reason the "VMware's Paravirtual SCSI Adapter" not to use?
If you don't need FT, I don't see any reason right now.
see http://blog.scottlowe.org/2009/07/05/another-reason-not-to-use-pvscsi-or-vmxnet3/
I would like to use this adapter for every VMs data (not boot partitions) partitions.
I guess you know that, anyway.
from the http://www.vmware.com/support/vsphere4/doc/vsp_esx40_u1_rel_notes.html
Enhanced VMware Paravirtualized SCSI Support
Support for boot disk devices attached to a Paravirtualized SCSI ( PVSCSI) adapter has been added for Windows 2003 and 2008 guest operating systems...
André
Thanks, this was all i needed.
Greetings
Simon
I heard only one disadvantage: VMs with low I/O will have no performance gains over the usually used SCSI adapter.
I read something perhaps a year ago that there was a risk for actually lower performance for virtual machines with "lower" IO need if the PVSCSI driver was used. Do you know if that was true?
Hello.
Yes, but it has been fixed in 4.1 - you can read much much more about it here at Scott Drummonds' site.
Yes, but it has been fixed in 4.1 - you can read much much more about it here at Scott Drummonds' site.
I think that was the article I read before, but I did not find anything about the issue being fixed in 4.1 and not in the What is new in Storage for 4.1 either?
EDIT: Now I saw the last comment on your link saying that is have been fixed. I wonder if there is any other reference available?
VMware kb 1017652 was linked in Scott's blog - it contains a statement about this issue being fixed in vSphere 4.1
Great, thanks a lot.