Increasing XenServer_s VM density
summary
XenServer 6.2 removes multiple hard limits so a host can run 500 supported VMs (650 PV) by increasing event‑channel capacity, doubling blktap2 device counts, raising AIO limits to ~1,000,000 and mitigating xenstored/select fd limits; dom0 lowmem (~1MB per VM) remains a constraint until 64‑bit dom0. Dom0 CPU pressure drops by replacing xenstored polling with xenstored polling → watches and by cutting qemu callbacks (notably USB emulation throttled/optional). Measured results: 90 Windows VMs boot ~60% faster, 200 VMs boot in ~13 minutes, Login VSI stays acceptable for ~300+ VMs.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:09Users expect VM density to scale with hardware
- 1:50XenServer's VM density scalability
- 3:08domo event channels
- 6:04blktap2 device minor numbers
- 7:21number of aio requests
- 8:47domo grant references
- 10:26connections to xenstored
- 12:16connections to consoled
- 12:51domo low memory
- 13:45Summary of hard limits
- 16:35500 Windows VMs on a host
- 17:04Outline
- 17:59High domo CPU utilisation by xenstored
- 21:41qemu burning domo CPU
- 27:14Booting 90 Win7 VMs
- 28:39Booting 120 Win7 VMs
- 29:12Booting 200 Win7 VMs
- 34:25Questions
