![]() When live migration is used in an Oracle VM server pool, hard partition licensing is not applicable. Consequently, for Oracle VM Release 3, any servers running CPU pinned guests must not be included in DRS (Distributed Resource Scheduler) and DPM (Distributed Power Management) policies. Live migration of CPU pinned virtual machines to another Oracle VM Server is not permitted under the terms of the hard partitioning license. To conform to the Oracle hard partition licensing requirement, you must follow the instructions described in this white paper to bind vCPUs to physical CPU threads or cores. Here are the requirements to satisfy the hard partition I mentioned above (taken from a document that is linked in InfoDoc 1529408.1): ![]() 5 license multiplier (such as x86), you are entitled to run that software on 4 cores. This means that if you own 2 processor licenses for Oracle Database EE for example, and are running on a platform that has a. With OVM, Oracle does accept a specific configuration that satisfies their definition of a “hard partition” where processor licensing is concerned. With anything other than Oracle VM Server for x86, you basically have to license every core in the cluster (VMware, Hyper-V, etc). As most of you likely know, Oracle has stringent licensing rules when it comes to running their software in a virtual environment.
0 Comments
Leave a Reply. |