I've been seeing people using Paravirtual adapters in there desktops, and I'm working how many people have used it without issue
I have run desktops with the Paravirtual adapter and haven't noticed any issues. With that said, VMware seems to recommend the LSI SAS adapter for Horizon desktops, so I switched away from the Paravirtual again. It used to be published that the Paravirtual adapter was optimized for high-transaction drives like DB and log drives and that it should not be used on system drives. However, with the 6.0 release (I think), it became acceptable to use the Paravirtual adapter with system drives.
Someone I talked to mentioned a instant clone issue, so I'm leaning toward just doing the lsi sas, I just know I have some high powered users where I think the paravirtual driver ma help. I 've been lucky enough to be able to one parent image for everything, so I probably will just pick the lsi sas, and play with the paravirtual one in my lab some more.
This is a great topic. I've gotten into several debates about this subject. It's always been my understanding that when building a master image we should be using the LSI SAS controller. Should I start looking at the Paravirtual controller or do you think it's a good idea to stick with the LSI SAS controller?
I'll probably stay with LSI SAS, until I can test it thoroughly.