VSphere VM - FEX compatibility matrix

Similar Questions

• Compatibility Matrix vs Release Notes - who 'wins '?

  We run vCenter 5.1 U1 with ESXi 5.1 U1 hosts and at one point, I thought would be so deploy vShere replication 5.1.1 for match/being compatible.

  The compatibility matrix has green checkmarks when selecting vSphere replication 5.1.2 with the foregoing.  I know I can't use vSphere replication 5.5.x and that's fine.

  However, the Release Notes for vSphere replication 5.1.2 States the following: "before that vSphere replication upgrade to version 5.1.2 make sure that you have upgraded to vCenter Server 5.1u2.

  So who 'wins '?  Can I go ahead and use my other purely 5.1U1 vCenter and ESXi environment vSphere replication 5.1.2?  The '' correction '' in 5.1.2 to 5.1.1 is minor, so I doubt I give much to just settle for 5.1.1 for my tests/POC, but I wanted to be sure and prefer to use the more recent/more great if I can.  Thank you.

  had it checked. the release notes are NOT correct and will be changed. Go by the matrix of compat. hope that helps.

• SQL server 2005 sp3 - says no on VC 2.5U4 compatibility matrix - VMware will all simply not to test and publish?

  SQL server 2005 sp3 - says no on VC 2.5U4 compatibility matrix - VMware will all simply not to test and publish?

  I play a new installation of VC 2.5U4 and provides the DBA SQL 2005 SP3 standard. VMware will not test compatibility SQL 2005 SP3 or are there unresolved issues? Messages to date appear to be mixed with most saying SP3 of SQL is not question.

  Updates or VMware response to requests for information from SQL Server 2005 SP3? Given that the SPs are listed separately on the compatibility matrix... it seems not to be supported. VMware would accept a call from support with VC on SQL2005 SP3?

  I'm in a similar position, we have installed SQL 2005 with SP3 and it seems to work very well. I just want to know, vmware will support me if I have problems with VCenter?

• compatibility matrix

  Hello
  can we install HR90MSS with tools 8.50?
  Where can I find the compatibility for all matrix?
  Thank you.

  Yes, you can install HCM9.0 with PeopleTools 8.50, if that's what you mean by "HR90MSS". The compatibility matrix is available on My Oracle Support (previously Metalink) in Document ID 822056.1.

  Thank you
  Sameer.

• Compatibility matrix for Cisco Catalyst 3012 Switch Module

  Hello

  I'm checking the compatibility of the VMware vSphere 5.5U1 Guide and an IBM switch module Part Number: 43W4401 product name: Cisco Catalyst Switch Module 3012. The search of the matrix returns Cisco 1GigE I350 LOM who seems to identify the drivers of Cisco.

  Can anyone help clarify and check if this IBM re-branded chassis switch module is supported and to a specific firmware for the switch code? Thank you all.

  L2/L3 switches are off-limit of drivers for vSphere hypervisor, so you don't find on the HCL...

  Here's IBM BladeCenter matrix interop for VMware:

  IBM ServerProven compatibility

  and here is the interoperability of the switch Cisco Catalyst 3012 with IBM BladeCenter chassis:

  IBM BladeCenter Interoperability Test program

  I hope this helps...

• 5.5 vSphere updated for compatibility with Samsung Tera1 Zero customers 1

  Hi all, we anticipate a 5.1 to 5.5 vSpehere upgrade (Update 1).

  I checked the compatibility matrices and can not find a match for our Tera1 Samung SyncMaster NC240 customer zero. My hypothesis is that VMware simply did not worth to test compatibility with the help of these models and it will actually work.

  Everyone upgraded to 5.5 vSphere update 1 with zero customers Tera1 and they can confirm if that succeeded?

  Thanks heaps...

  We are currently using Horizon view 5.3 with vSphere 5.5U1 and about 700 Tera1 zero clients have no problem Display protocol is of course PCoIP, over WAN and LAN connections.

  The Tera1 devices are Wyse P20 and Samsung NC190 (must be the same as yours with screen 19 inch).

• VSphere APIs and compatibility ESX

  I've implemented the backup of a VMWare VM and application of recovery with vSphere API and VDDK. The development has been done entirely on 5.0 ESX servers. The following discussion provides an overview of how I implemented the restoration.

  http://communities.VMware.com/message/2130483#2130483

  When another person has tested my application, he noted the rollback feature does not work. When I've debugged, I found parameter spec unit to CreateVM_Task behaves differently 5.0 Esx to Esx 4.0. In the case of Esx 5.0, it works perfectly, where as in the case of Esx 4.0, none of the devices that I fill before the CreateVM_Task is created and the restore fails because of this.

  How can I understand the compatibility of the Esx and the vSphereAPI versions? I assumed that the SDK should be retro-compatible with Esx Server? Can someone shed some light how this problem can be solved?

  Thank you

  . / Siva.

  Hi Siva,

  That sounds good, maybe, we'll get you going even faster than I expected:

  As already noted William

  lamw wrote:
  but in general, the more recent editions of vSphere will support previous editions of vSphere. vSphere 5.1 supports vSphere 4.x and 5.0

  the only thing being that if new properties are added to a data in 5.1 object then you can not use in 4.x or 5.0.

  It seems to me that your code is based on 5.0 WSDL generated by gsoap stubs. It is ultimately you generate SOAP requests that are supposed to work with 5.0, 5.1, 6.x one as well now. Yet, when he delivers the SOAP messages to 4.x, it is likely that you include a property that is not defined in the WSDL of 4.x.

  Attached is a diff of the definition WSDL VirtualMachineConfigSpec of 4.0 to 5.0 Quick. Look at line 27 and following

  
  27              
  ====
        !>      
  ====
  28              
  

  Here, you can see that numCoresPerSocket property was not available in 4.0, but was added in 5.0. It is also what we said the documentation centre: for vSphere API 5.0.

  You declare that numCPUs is affected but memoryMB not. Between the two numCoresPerSocket has been inserted to 5.0. It seems that the 4.0 Server reads your VirtualMachineConfigSpec until numCPUs then encounter numCoresPerSocket and abandoned.

  So far my theory.

  What I don't understand is that this seems to happen in silence as you don't declare any exception. Yet, says William

  wlam wrote:
  As you know, there will be new properties in new versions of vSphere such as 5.1, that if you try to assign to an older version of vSphere, it will throw an unknown error...

  As you can learn from the attached diff we serveral more properties that have been added to the 5.0. Might well want to comment on all those in your current code and re-run CreateVM_Task against server 4.0.

  Perhaps this might solve the problem.

• VCA compatibility matrix

  Hello

  We plan to extend our cluster HA/DRS vSphere, currently existing three HP ProLiant DL380 G6, with a server, but it would be DL380 G7. We have CVS in vCenter activated by the following:

  

  But if I followed 1003212 Knowledge Base article, say something different.

  We currently have CPU xE5520, which is Nehalem. We want to add xE5645, which is Westmere.

  Knowledge Base gives me red, which means that it is not taken care of. said vCenter: Westmere is OK.

  Is our configuration support in this case?

  Best regards

  Marco

  Hello

  We use the G6 and G7 with EVC Mode. It works without problems. And if the hardware is on the HCL, there should be no reason why it is not supported. For this purpose, you have the opportunity to use CVS. Because not all companys are in the enviable position to buy equipment for years to come.

  Frank

• vCenter Server 5.5 compatibility with vSphere 4 hypervisor

  I recently installed vCenter Server 5.5.0.5201 (with a Standard license valid vCenter) and I am trying to add the hosts to vCenter data center. I can connect successfully to the host but vSphere displays the following error:

  "The host is licensed with vSphere 4 hypervisor. The license of vCenter Server edition doesn't support vSphere 4 hypervisor. »

  Now I found the slot compatibility matrix and there clearly shows that vCenter 5.5 is compatible with all the way back to version 4 for ESXi. I must be missing something, can someone please clarify the question.

  

  I know that vSphere hypervisor and ESXi Server is essentially the same but vSphere hypervisor is the free version, so is there a difference that I know?

  This happens because you are using a free license on the ESXi 4.1 key.

  "The host is licensed with vSphere 4 hypervisor" means that it is a free ESXi. You will not be able to manage the free ESXi with vCenter.
  

• B-200 M1 with vSphere 5.1

  Hello

  I've seen (both from cisco.com and vmware.com) there is no support for vSphere 5.1 in blades B-200 M1... and I wonder if this info is accurate... that I would find unacceptable from the point of view of customers with B - 200 M 1 set up...

  Thank you very much

  M1 B200 and B230 M1 M1 B440 have since been added to the UCSM 2.0 compatibility matrix (5) & vSphere 5.1.   The PQP process will not be necessary.

  Listen to us and to respond to customer concerns Dani, and we appreciate the feedback!

  Kind regards

  Robert

• VSphere 6.0 backward compatible with vCenter 5.5 replication is?

  At one point, the vSphere replication 6.0 compatibility matrix said that it is compatible with vCenter 5.5.  I think it was around mid-March.  Now, he seems to have changed and says vSphere 6.0 replication is only compatible with vCenter 6.0.  Is this true?  Are there plans to make vSphere replication 6.0 backward compatible with vCenter 5.5?

  Bill,

  A decision was made not to support backward compatibility between replication 6.0 vSphere and vCenter Server 5.5 going forward.  This is the result extended and careful considerations affecting the provision of quality and consistent user experience for our customers using vSphere 6.0 replication.

  Thus, vSphere 6.0 replication is officially supported with vCenter Server 6.0 only (SSO 6.0, 6.0 PC, Web Client 6.0).  This resulted therefore in the interoperability of public VMware product matrix.

• The horizon 6 compatibility?

  You want to create an environment of 6.1. I know that sounds ridiculous, but is it supported in vSphere 6?  The compatibility matrix shows no any view version of vSphere 6 and 6.1 compatibility view doesn't show no compatibility with any version of vSphere either.  So although the release refers to vSphere vSphere and 6 6 is available for download under view, the matrix is not saying.  I can say that the power that we can indeed go with 6.1 and vSphere 6 looking just for clarification.  TIA.

  Yes it is

  Look at the release notes.

  They just do not update yet.

  This is the reason why they put this release - to vsphere supports 6

• vSphere replication device 5.5.1.2 Build 1999430 to 5.5.8 upgrade?

  I have vCenter Server 5.5 U2 both protected and DR Sites, vSphere replication device 5.5.1.2 build 1999430

  I'm not able to move the unit to 5.5.8 version or by using update manager, nor page VAMI (Update Section)

  Any ideas, please.

  Kind regards.

  Ndiaye.

  Unfortunately, upgrade is possible between minor versions... 5.5.x to 5.5.x etc.

  The replication of vSphere upgrade

  The downloadable ISO image is the only way to upgrade to vSphere replication 5.1.x 5.5.x or 5.6 to 5.8 Replication vSphere. You cannot pass vSphere replication version 5.5.x or 5.6 5.1.x version 5.8 using vSphere Update Manager or the official repository of update of VMware since the unit of replication vSphere VAMI. See the compatibility matrix for more information on versions supported.
  See Upgrading vSphere replication upgrade to vSphere 5.8 replication.

  See:

  

• Customer error supported download the files for the client vSphere 5.0

  Hi all

  
  

  I am new to VMware and learning ESXi 5.0. I built my 5.0 ESXi host and then downloaded the 5.5 vSphere client. Given that I have only one host; client vSphere 5.5 can handle that. I installed the client and enter the IP address of the host with root/configured password management. He gave the certificate WARNING said to download the files from customer support. He has always exceeded with error as you can see it.

  
  

  I'm under client on a LAN connection high speed, I even changed the connections to see if access to the internet the problem. It is more simple home, 1 host installation, a windows 7 computer (with vSphere client installed), both connected to my DSL modem/router. The client support files won't download anything. Help please!

  
  

  

  Sorry my bad vSphere Client 5.5 support ESXi 5.0 but Client vSphere 5.0 ESXi host does not support the 5.5U1 (Build 1618071)

  Check the compatibility matrix for more information vSphere Client

  

  VMware product interoperability matrices

• Windows 2003 & 2008 vCPU compatibility

  Hi guys,.
  I use the vSphere Enterprise license
  I received some comments std VMs Windows 2003 and windows 2008 std, I turn vCPUs to 8 for these guest virtual machines
  I wonder is Windows 2003 & 2008 supports 8 vCPUs or no, I've read somewhere Windows 2003 supports maximum of 4 processors of material, but I couldn't find the vCPU compatibility matrix
  your help will be much appreciated
  Thank you
  Kind regards
  Chan

  For this and for licensing reasons, VMware has introduced virtual vCPUs multi-core with vSphere 4.1. You can assign the number of vCPUs you need, and then set the way they are presented to the guest OS.

  With vSphere 4.1, you must configure it as explained http://kb.vmware.com/kb/1010184, vSphere 5 provides this setting in the GUI.

  To find out how many "physical" processors are supported by see for example http://support.microsoft.com/kb/888732/en-us or http://msdn.microsoft.com/en-us/library/ms143760.aspx Windows

  André