If you log in with your developerWorks ID, you can leave comments and feedback for the development team.
WebSphere Virtual Enterprise Version 6.1.1

Supported hardware virtualization environments

Before you deploy WebSphere(R) Virtual Enterprise on virtualized hardware, you must understand the limitations for the hardware virtualization platform that you are using. Note: This page lists the most up to date information on the support of various hardware virtualization platforms.
Hardware virtualization environments

Virtualization platform	Restrictions	Supported processor sharing mode
ESX Version 3.5 VMware vSphere 4

See VMware Infrastructure 3 platforms and WebSphere Virtual Enterprise for a list of limitations.|Shared and dedicated modes are supported for ESX or VMware vSphere4 , but you must configure WebSphere(R) VirtualEnterprise to communicate with the ESX or VMware vSphere 4 hypervisor or the vCenter that is in control of the hypervisors where WebSphere(R) Virtual Enterprise is running.|

AIX(R) 5.3 and AIX(R) 6.1 on POWER5(TM) and POWER6(TM) (Micro-Partitioning(TM))	See Configuring AIX 5.3 and AIX 6.1 on POWER5 and POWER6 Micro-Partitioning for required configuration steps. For uncapped shared processor partitions, equal partition weights are recommended. WebSphere(R) Virtual Enterprise does not have a partition to physical machine mapping and thus does not use the partition weight when making workload distribution and server placement decisions.	All WebSphere(R) VirtualEnterprise features are supported on AIX Micro-partitioning in capped or uncapped mode. Shared capped, shared uncapped, and dedicated modes are supported for both POWER5(TM) and POWER6(TM). Support for dedicated donating and multiple shared pools modes are available on POWER6(TM) only.
Linux(R) on POWER(TM) (Micro-Partitioning(TM))	None for dedicated.	Dedicated.
Linux(R) on z/VM(R)

The guest operating system must be Red Hat Enterprise Linux (RHEL) 5.0, 5.1, 5.2 or SUSE Linux(R) Enterprise Server (SLES) 10.
Mapping a Linux(R) on zSeries(R) operating system image to a physical logical partition (LPAR): WebSphere(R) Virtual Enterprise can balance workload across multiple z/VM(R) virtual machines that are running Linux(R) as the guest operating system. However, it does not have knowledge of the LPAR that is hosting the virtual machines on the z/VM(R) image and is therefore unable to make workload balancing decisions based on the workload at the LPAR level.

Service policy goals: Workload that is not under the control of WebSphere(R) Virtual Enterprise might be running on other Virtual Machines on the same z/VM(R) image. This workload might affect service policy goals.|Dedicated and shared.|

Solaris Operating Environment 10 on Sun (Zones)	None for dedicated.	Dedicated.
HP-UX 11i v3 on HP using Virtual Partitions (vPars) or Integrity VMs	Currently not supported.	None.
Linux(R) Xen

You must be using SLES 11 or later.
You must use the following guidelines for setting up the clock correctly: SUSE Linux Virtual Machines: Section 7.4.3 Virtual Machine Clock Settings.
Use para-virtualized mode over full-virtualized mode. Full-virtualized mode can lead to network bottlenecks that can adversely affect performance of the system. This performance problem is particularly possible for large topologies.||

Microsoft(R) Hyper-V Currently not supported. None.

Supported hardware virtualization environments

Related links

Wiki Disclaimer and License

Copyright IBM Corporation 2007,2008,2009. All Rights Reserved.