So, you want to run Windows workloads on OpenStack?
summary
Production cloud shifts to 70% Windows VMs after COVID and runs Windows on KVM/QEMU with nested Hyper‑V working inside a Windows Server 2016 guest. Image build uses cloudbase‑init, automated sysprep, driver injection and compression; set image metadata os_type=windows and prefer vendor‑built WHQL drivers (Red Hat or Canonical builds) for Microsoft support. On KVM enable host CPU passthrough and cpu_mode=custom to allow nested virtualization and live migration across different CPUs. Recommend boot volumes 20–25GB, 4GB RAM, 2 vCPU, create volumes with delete_on_terminate=no, and enforce QoS IOPS (example read 3000/write 1000) plus per‑instance monitoring.
AI-written summary · about
chapters (17)
- 0:00Introduction and setup
- 2:50Hypervisor choices
- 7:32Windows image creation
- 9:39Drivers and configurations
- 10:34Driver certification check
- 10:55Canonical build drivers
- 11:24KVM metrics configuration
- 13:22Instance launch practices
- 15:10Performance limits
- 17:46Monitoring instance data
- 17:56Windows sandbox feature
- 18:10Performance results
- 18:20Simplifying user experience
- 18:30Environment tuning
- 18:43Conclusion
- 19:07Session recap
- 20:02End of session
related talks
19mFlattening The Cloud Learning Curve Using Rails
40mDeploying any Rails application to any cloud in minutes
28mMoving a Monolith from AWS EC2 to K8
31mWalking in the Clouds
26mLessons learned from running Rails apps on-premise
38mA Small Business that was Able to Leverage the Platform While...
37mBalancing Power and Pain: Moving a Startup From a PaaS to Kubernetes
53mDelivering Autonomous Rails Apps behind Corporate Firewalls