{"id":1060,"date":"2010-11-24T14:41:46","date_gmt":"2010-11-24T13:41:46","guid":{"rendered":"http:\/\/vmdamentals.com\/?p=1060"},"modified":"2011-12-29T11:35:29","modified_gmt":"2011-12-29T10:35:29","slug":"windows-xp-virtualized-which-disk-controller","status":"publish","type":"post","link":"https:\/\/www.vmdamentals.com\/?p=1060","title":{"rendered":"Windows XP virtualized – Which disk controller?"},"content":{"rendered":"


<\/p>\n

Amongst many of the optimizations for virtual desktops, it is always stated that the LSI Logic virtual disk controller is faster\/more efficient than the BusLogic controller. So is this really true in vSphere 4.1 environments?<\/p><\/blockquote>\n


\n


\nIntro<\/strong><\/p>\n

In the ESX 3.5 days it was often stated: An LSI Logic virtual disk controller performs better than the (default) BusLogic virtual disk controller. I wondered if this is still true in vSphere. So I performed a little test to show what’s best.
\n


\nTo the Lab!<\/strong><\/p>\n

In the lab I took a Sun x4170 (dual quadcore Nehalem server) with vSphere 4.1 running on top. For storage, a fiberchannel connected EMC CX500 LUN. On that same LUN, I performed three fresh installs of Windows XP (with SP3 integrated). One using the IDE controller, one on BusLogic and one on LSI Logic.<\/p>\n

After some “EfSixing” \ud83d\ude09 I managed to get the SCSI drivers into the XP installs. Right after the XP installs were done, I downloaded IOmeter<\/a> on all of them. Within IOmeter, I created a workload on their C-drives:<\/p>\n