Revision history [back]

click to hide/show revision 1
initial version

Havana Windows 2008 vcpu topology workaround?

Hello, I've been working on a Havana cloud, and I realize that the solution for my problem is to upgrade to Juno, but that's several months away and I'm hoping that there is a workaround for my problem.

Like many others, I am trying to create some large Windows VMs with up to 32 vCPUs, but the default topology is allocating one core with one thread to each virtual socket, which is causing a conflict with the version of Windows Server 2008 Enterprise, which only allows 8 sockets.

I have tried manually editing the XML files in the qemu directory in order to add the topology, but the XML file gets overwritten whenever I reboot the instance. Is there a way to make the changes permanent and allow a workaround to enable multiple cores per vCPU? Thanks!

Havana Windows 2008 vcpu topology workaround?

Hello, I've been working on a Havana cloud, and I realize that the solution for my problem is to upgrade to Juno, but that's several months away and I'm hoping that there is a workaround for my problem.

Like many others, I am trying to create some large Windows VMs with up to 32 vCPUs, but the default topology is allocating one core with one thread to each virtual socket, which is causing a conflict with the version of Windows Server 2008 Enterprise, which only allows 8 sockets.

I have tried manually editing the XML files in the qemu directory in order to add the topology, but the XML file gets overwritten whenever I reboot the instance. Is there a way to make the changes permanent and allow a workaround to enable multiple cores per vCPU? Thanks!