Winserver 2022 UEFI Template

Product Support Operations
1

Hello, i encounter issues with Windows server 2022 UEFI VM.

No problem on install or lauch , my vm is working fine until i try to restart it from vnc

It remains stucked:

image
image412×164 1.12 KB

I can delete the Vm and instantiate it again but the same problem happens every time i wanna reboot it…

Here is my template:

CONTEXT = [
NETWORK = “YES”,
SSH_PUBLIC_KEY = “root[SSH_PUBLIC_KEY]” ]
CPU = “2”
CPU_MODEL = [
MODEL = “host-passthrough” ]
DISK = [
CACHE = “none”,
DEV_PREFIX = “vd”,
DISCARD = “unmap”,
IMAGE = “SATIS–DSK”,
IMAGE_UNAME = “oneadmin”,
IO = “native” ]
FEATURES = [
ACPI = “yes”,
APIC = “yes”,
GUEST_AGENT = “yes”,
HYPERV = “yes”,
LOCALTIME = “yes”,
PAE = “yes” ]
GRAPHICS = [
KEYMAP = “fr”,
LISTEN = “0.0.0.0”,
PORT = “6930”,
TYPE = “VNC” ]
HOT_RESIZE = [
CPU_HOT_ADD_ENABLED = “NO”,
MEMORY_HOT_ADD_ENABLED = “NO” ]
HYPERVISOR = “kvm”
INPUT = [
BUS = “usb”,
TYPE = “tablet” ]
INPUTS_ORDER = “”
MEMORY = “16384”
MEMORY_RESIZE_MODE = “BALLOONING”
MEMORY_UNIT_COST = “MB”
NIC = [
IP = “172.17.232.7”,
NETWORK = “CR_pedago”,
NETWORK_UNAME = “oneadmin” ]
NIC_DEFAULT = [
MODEL = “virtio” ]
OS = [
ARCH = “x86_64”,
BOOT = “disk0”,
FIRMWARE = “/usr/share/OVMF/OVMF_CODE.secboot.fd”,
FIRMWARE_SECURE = “YES”,
KERNEL_CMD = “console=ttyS0”,
MACHINE = “q35” ]
OTHER = “—”
OWNER = “um-”
USER = “oneadmin”
VCPU = “4”

image is qcow2
and there is no info log in /var/log/one/vmid except:

Fri Dec 19 09:56:07 2025 [Z0][VMM][I]: post: Executed “sudo -n ovs-ofctl del-flows vswitch in_port=13”.
Fri Dec 19 09:56:07 2025 [Z0][VMM][I]: post: Executed “sudo -n ovs-ofctl add-flow vswitch table=0,in_port=13,priority=100,actions=note:00.00.00.2e.00.00,resubmit(,10)”.
Fri Dec 19 09:56:07 2025 [Z0][VMM][I]: post: Executed “sudo -n ovs-ofctl add-flow vswitch table=10,in_port=13,priority=100,actions=resubmit(,20)”.
Fri Dec 19 09:56:07 2025 [Z0][VMM][I]: post: Executed “sudo -n ovs-ofctl add-flow vswitch table=20,in_port=13,priority=100,actions=normal”.
Fri Dec 19 09:56:07 2025 [Z0][VMM][I]: ExitCode: 0
Fri Dec 19 09:56:07 2025 [Z0][VMM][I]: Successfully execute network driver operation: post.
Fri Dec 19 09:56:07 2025 [Z0][VM][I]: New LCM state is RUNNING

OpenNebula version : 6.6.1.1-1

2

Hello,

I understand that windows have the latest virtio drivers installed and the disk was able to boot previously (I mean, the vda disk is OK). Please, install too the guest agent

I’ve found sometimes problems with fast startup and hibernation on windows. Is it disabled on windows image?

3

No problem on install or lauch , my vm is working fine until i try to restart it from vnc

to isolate the problem could you, please, clarify if that VM fails to boot after power off → on cycle triggered from opennebula menu too or it happens only after rebooting the VM from VNC?
By "rebooting from VNC did you mean you are pressing Ctrl+Alt+Del button at the right upper corner of VNC console screen or you are rebooting the VM from inside of Guest OS)?

What OS distro and its version you are using on your hypervisor nodes? What is libvirt version?

OpenNebula 6.6.1.1-1 is too old and we encourage you to upgrade to 7.0.1 at your earliest convenience.