Using sysprep to initialize a Windows virtual machine has no effect

[yule-sun]

Affected version

In the ovirt4.4.8.6 environment, I installed a Windows virtual machine and used sysprep /oobe /shutdown to shut it down. Then I used this virtual machine to create a template, and then used the template to create a virtual machine.After using the sysprep function to start the virtual machine, the configuration of the virtual machine did not change.

• oVirt Engine: ovirt-engine-4.4.8.6-1.el8.noarch
• Host OS Variant: ovirt-host-4.4.9-2.el8.x86_64
• VDSM version: vdsm-4.40.100.2-1.el8.x86_64

Describe the bug

A clear and concise description of what the bug is

To reproduce

Steps to reproduce the behavior

1. use the windows vm create a template
2. Follow the steps on the official website to initialize and start the virtual machine.
   7.10.2. Using Sysprep to Initialize a Virtual Machine
   Use Sysprep to automate the initial configuration of a Windows virtual machine. You can use the Sysprep fields to configure a virtual machine’s host name, time zone, root password, authorized keys, network interfaces, and DNS service.

Using Sysprep to Initialize a Virtual Machine
This procedure starts a virtual machine with a set of Sysprep settings. If the relevant settings are included in the template the virtual machine is based on, review the settings and make changes where required.

Create a new Windows virtual machine based on a template of the required Windows virtual machine. See Creating a Virtual Machine Based on a Template.

Click Compute Virtual Machines and select the virtual machine.

Click the Run drop-down button and select Run Once.

Expand the Boot Options section, select the Attach Floppy check box, and select the [sysprep] option.

Select the Attach CD check box and select the required Windows ISO from the drop-down list.

Move the CD-ROM to the top of the Boot Sequence field.

Configure any further Run Once options as required. See Virtual Machine Run Once settings explained for more details.

Click OK.

Then there is no change in the virtual machine configuration, the administrator password, IP address, etc. are not modified.

Expected behavior

A clear and concise description of what you expected to happen

Screenshots

If applicable, add screenshots to help explain your problem

Additional context

The following is the sysprep script

true true true Ethernet 10.199.196.50 255.255.254.0 10.199.196.1

Add any other context about the problem here

[dupondje]

Can you try to reproduce the issue on the latest ovirt version on el9/el10?
If you can reproduce it, please re-open the issue.