Score:0

Is it (still) possible to overcommit cpu with Xen?

cn flag

Common hypervisors (Proxmox, Vmware, KVM..) do not prevent the sum of allocated virtual resources (such as vCPU) to exceed the number of physical ones, even if some of them (OpenStack) do limit the overcommittment ratio (virtual_resources/physical_resources) to a configurable value.

I'm confused about this paragraph from this article

XenServer previously allowed overcommitting vCPUs. However, this behavior is blocked as it can lead to undesirable effects when running a VM a vCPU that cannot be matched to a pCPU

I can both read it as "overcommittment is blocked in Xen" or "one VM cannot exceed the number of physical cores but sum of all VM vCPUs can"

Is it (still) possible to overcommit cpu/memory with Xen?

Score:0
mf flag

The number of vCPUs any given domain (Xen VM) can have may be limited to the number of actual cores. It is definitely still possible for the total number of allocated vCPUs on a given host to exceed the number of physical cores.

(presently looking at a host with 8 cores, but 35 vCPUs among 8 domains)

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.