New Question

Revision history [back]

click to hide/show revision 1
initial version

Hello,

please make sure you have the virtio drivers installed, in case you are using KVM. This can be achieved by setting the correct platform when you generate the image: https://github.com/cloudbase/cloudbase-init-offline-install/blob/nano-server-support/NewNanoServerImage.ps1#L27

Moreover, if you are using KVM, the processor flags must be compatible. You may need to set a comptible cpu-model or the following conf value in the nova compute node, in nova.conf: [libvirt] cpumode=host-passthrough The reason behind this behavior is that the kvm cpu models(kvm64/qemu64) do not offer to the Windows 10 / Nano VM the required CPU capabilities: cx16, lahflm and PrefetchW(3dnow -- already emulated). More info here: https://www.microsoft.com/en-us/windows/windows-10-specifications .

Thanks,

Adrian.

Hello,

please make sure you have the virtio drivers installed, in case you are using KVM. This can be achieved by setting the correct platform when you generate the image: https://github.com/cloudbase/cloudbase-init-offline-install/blob/nano-server-support/NewNanoServerImage.ps1#L27

Moreover, if you are using KVM, the processor flags must be compatible. You may need to set a comptible cpu-model or the following conf value in the nova compute node, in nova.conf: nova.conf:

    [libvirt]
        cpumode=host-passthrough
     cpu_mode=host-passthrough

The reason behind this behavior is that the kvm cpu models(kvm64/qemu64) do not offer to the Windows 10 / Nano VM the required CPU capabilities: cx16, lahflm lahf_lm and PrefetchW(3dnow -- already emulated). More info here: https://www.microsoft.com/en-us/windows/windows-10-specifications .

Thanks,

Adrian.