Thank you for your response, since you emailed oracle directly this must their current stance. the following is for the sake of conversation and will basically be a discussion point with our oracle rep if we ever start running oracle on intel or in a VM.
So by your response, if we had an x445 8way and we created one single CPU'd VM and installed oracle, we would need 8 CPUs worth of licensing??? this seems like robery

. As previously stated we do not currently run Oracle on Intel systems but we are looking into running Oracle on Linux/Intel and maybe in a VM.
My understanding is that the entire encapsulated single CPU VM world is constrained to run on a single processor at a time. I further understand that a world can be moved from a CPU to another CPU as the system load changes but that world (containing the oracle processes)is still only capable of running on 1 physical processor at a time. Does anyone know what ESX processes would perform operations on behalf of the VM that would be running on other CPUs? If we had an external server running similar processes (maybe like patrol monitor or something) that "performed operations on behalf of the ... machine running oracle" like restarting services, running scripts, did health monitoring, would we need to include those CPUs in the license count as well?
I have some limited experience with IBM P650s running AIX in an LPAR configuration. I know this is quite differnt but whenever you restart an LPAR there is NO guarantee that it will get the same physical CPU, so an single CPU assigned LPAR can also be run on any CPU in the system (although it can only change CPU's during a restart of the LPAR). With the upcoming AIX 5.3 and Power5 CPUs, if we had 0.4 processor assigned to an LPAR can we get Oracle license for 0.4 CPU? I bet probably not.
I tend to equate ESX to the Hypervisor function. ESX is software, Hypervisor is firmware. The hypervisor "performs operations on behalf of the" LPAR (primarily during startup) and it has access to all CPUs in the system as well. Can these be somewhat equated? As I previously quoted, Oracle's own white paper describes hard partioning and every piece of their desciption perfectly describes ESX. Their definition of soft partioning perfectly describes work load managemnt products and does NOT describe ESX. Maybe at worst ESX is somewhere in the middle?
I believe this may be just about as clear as mud for me right now.
Thank you for letting me carry on about this.
IF we did a VM with Oracle and they wanted 8 CPUs of license for it, this topic may become a personal peve of mine

.