VMware Cloud Community
KNardi
Contributor
Contributor

LSI or BUS Logic

We will be converting existing VM's from our current ESX 3.0.xx, VC 2.0 to ESX 3.5, with VC 2.5. My question is do I change from LSI Logic to BUSLogic for the scsi controller?

If yes, can you please point me to the white paper that suggests this.

thanks in advance

0 Kudos
7 Replies
Jasemccarty
Immortal
Immortal

What type of guests do you have?

I can't speak for Linux, but Windows 2000 works best with the BusLogic, and Windows 2003 works best with LSILogic.

But you shouldn't have any changes when you move from ESX 3.0 to ESX 3.5, other than upgrading the VMware Tools and the virtual hardware version.

Jase McCarty

http://www.jasemccarty.com

Co-Author of VMware ESX Essentials in the Virtual Data Center

(ISBN:1420070274) from Auerbach

Please consider awarding points if this post was helpful or correct

Jase McCarty - @jasemccarty
0 Kudos
marceljanssen
Contributor
Contributor

for Linux see http://www.vmware.com/files/pdf/linux_install_config.pdf

quote from above pdf

"In most cases, VMware recommends that you use the LSI Logic virtual SCSI adapter with all Red Hat guest operating systems.
However, ESX Server 2.5.2, 2.5.3, 2.5.4, and 2.5.5 support only the BusLogic SCSI adapter. VMware provides a
separate BusLogic driver for Red Hat Enterprise Linux 4 Upgrades 1, 2, 3, 4, and 5"

-Marcel-

0 Kudos
AntonVZhbankov
Immortal
Immortal

There is good old rule. If it works - don't touch it.

So you shouldn't signficantly change VMs (replace disk controllers, for ex), unless you experience real problems with old config.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
TomHowarth
Leadership
Leadership

I have got to agree with Anton, if it works don't touch it. some people have reported better performance with the LSI driver with XP guest, personally I have not seen it. Just move the guests and leave then as they are

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "VMware Virtual Infrastructure Security: Securing ESX and the Virtual Environment”.

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
0 Kudos
KNardi
Contributor
Contributor

We are currently at 3.0.x and moving to 3.5 update 3 (already built, ready for conversion).

All of our VM's are Windows servers.

0 Kudos
AntonVZhbankov
Immortal
Immortal

Just leave BUSLogic controllers for existing VM's and use LSI for new.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
ksc
VMware Employee
VMware Employee

The backend for Buslogic / LSILogic is almost identical, with very minor differences due to the hardware specs being different. The differences only apply during device driver loading, and should not affect I/O speed.

The real reason for two controllers is driver support. Older OSes have default driver support for Buslogic (e.g. Windows 2000 install CD), newer OSes do not have Buslogic drivers but do have LSILogic drivers (e.g. Windows 2003, 2008 install CDs). Pick the controller for which it is easier to obtain a driver for the guest.

0 Kudos