Hello!
I followed the document Setup for Microsoft Cluster Service to configure a MS Cluster 2008 between to VMs in two vSphere hosts.
The procedure is easy and I've done that some times using Windows 2003 and ESX 3.5. But it is not working with the newer versions. I received the message "Device 'SCSI controller 1' is a SCSI controller engaged in bus-sharing" when I tried to set SCSI Bus Sharing on the VM to Physical.
Anyone could help me?
Regards,
Luciano
You have to follow the new document:
http://www.vmware.com/pdf/vsphere4/r40/vsp_40_mscs.pdf
Note that for Windows 2008 you must use a specific controller.
Andre
Thank you for your help but I received the same error message again.
Some doubts about the document:
. "Clustered virtual machines as part of VMware clusters (DRS or HA)" - As I use DRS and HA may I configure an anti-afinity rule solve this problem?
. "You must use hardware version 7 with ESX/ESXi 4.0" - This is new for me. How do I know the hardware version?
I hope you can help me more.
Regards,
Luciano
As I use DRS and HA may I configure an anti-afinity rule solve this problem?
Yes. Or put on ESX not in a VMware cluster.
This is new for me. How do I know the hardware version?
New VM created with vSphere have v7.
Old VM (ESX 3.x) have v4.
You can see the version in VM properties (at the top).
You can set a different version using a manual VM creation.
Andre
Ok. So DRS and HA is not the problem at this moment.
The VM is new so the HW is v7. I checked!
What else could cause this problem?
Windows 2008 has different SCSI requirements.
You must use a different SCSI controller (LSI Logic SAS).
Are you using this kind of controller?
Andre
Yes. I changed the SCSI controller type as described in the pdf document.
Your error message is strange, cause normal appear when your use VMotion on a MSCS node:
Are you trying to set the SCSI controller to physical (remembet to use a different SCSI controller from the OS one) or the shared disks?
Andre
The message is strange for me too but I started using ESX 4.0 last week.
I already have two VMs running MS Cluster but they were created and configured on ESX 3.5 and they run Windows 2003.
The problem happens when I set the LSI Logic SAS controller to physical.
I've no other idea. I can't recreate your problem.
My configuration is very simple and works: one vmdk (C:) with id 0,1 and no sharing, more disks with id 1,X attached to a controller with physical sharing.
All disks are thick with support for clustering.
Andre
After remove all snapshots the problem was solved.
Tks!
Good for you
Andre
hi guys,
Is there any way to take snapshot of these kind of clustered systems (especially Microsoft Server 2003 Cluster)?