Sebastián Greco wrote:
LOL!!! I just saw your "EDIT" So funny we both mark "bold" the same phrase!
Do you have any document that supports your statment of "regardless of whether or not they're sibling vCPUs"?
Thanks again Andy!
elgreco81
PS: I'm very slow when writting in english
I just noticed this too. I'm apparently slow when writing in english too, and it's my native language. 
There are quite a few documents to support that, but most of them are huge and not easy to quote here. Probably the easiest way to explain this is to note the following line from the VMware CPU scheduler doc you linked in the original post:
A vCPU and a world are interchangeably used to refer to a schedulable CPU context that corresponds to a process in conventional operating systems.
Now I hate to send you to Wikipedia for a source on this, but it's the most concise explanation I could find.
A process moves into the running state when it is chosen for execution. The process's instructions are executed by one of the CPUs (or cores) of the system. There is at most one running process per CPU or core.
You might also take a look at this: http://www.cs.uic.edu/~jbell/CourseNotes/OperatingSystems/5_CPU_Scheduling.html
It's more of an overview of CPU scheduling in general, but reading through that will probably clarify things a bit.