Description of problem:
Process is not normal in win2016 and win2016-efi guests after v2v conversion

Version-Release number of selected component (if applicable):
virt-v2v-2.3.4-6.el9.x86_64
libguestfs-1.50.1-6.el9.x86_64
nbdkit-server-1.36.1-1.el9.x86_64
libnbd-1.18.1-3.el9.x86_64
virtio-win-1.9.35-0.el9.noarch

How reproducible:
100%

Steps to Reproduce:
1.Prepare a win2016 or win2016-efi guest on VMware, the CPU is normal, pls refer to screenshot 'win2016-CPU-before'

2.Convert win2016 or win2016-efi guest from VMware by virt-v2v

1. virt-v2v -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk8.0.1 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api  -op /home/rhvpasswd -os nfs_data esx8.0-win2016-x86_64-efi -v -x |& tee > v2v-convert-win2016-guest.log

3.Check cpu status for guest and find CPU is abnormal, pls refer to screenshot 'win2016-CPU-after"

Actual results:
As above description

Expected results:
Process status shows normal in win2016 guest after v2v conversion

Additional info:
1.Can't reproduce this problem with win2022, win2019, win11, win10 guests