-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
rhel-9.0.0
-
None
-
Moderate
-
rhel-virt-tools
-
ssg_virtualization
-
5
-
False
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
-
57,005
Description of problem:
windows guest fails to install qemu-ga sometimes because of system error 258 after v2v conversion
Version-Release number of selected component (if applicable):
virt-v2v-1.44.0-1.el9.1.x86_64
libguestfs-1.45.5-1.el9.x86_64
guestfs-tools-1.46.1-2.el9.x86_64
libvirt-7.0.0-6.el9.x86_64
qemu-kvm-6.0.0-2.el9.x86_64
virtio-win-1.9.15-3.el9.noarch
libguestfs-winsupport-8.2-1.el9.x86_64
rhv4.4.6.3-0.8.el8ev
How reproducible:
80%
Steps to Reproduce:
1.Prepare win2016 guests and set different date format in guest on VMware, then convert guests from VMware to rhv4.4 by v2v
#virt-v2v -ic vpx://root@10.73.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -ip /home/passwd -o rhv-upload -oo rhv-direct -oc https://hp-dl360eg8-03.lab.eng.pek2.redhat.com/ovirt-engine/api -oo rhv-cluster=NFS -op /home/rhvpasswd -of raw -os nfs_data -b ovirtmgmt $win2016_guest_set_different_date_format
Check if qemu-ga can be installed automatically after after v2v conversion, get below result:
Short_date Long_date Qemu-ga running
M/d/yyyy MMMM d,yyyy NO
MM/dd/yy MMMM d,yyyy NO 50% YES 50%
d/M/y dddd d MMMM yyyy NO
dd.MM.yyyy dddd,d.MMMM yyyy NO
dd-MMM-yy dddd, MMMM d,yyyy NO
yyyy/MM/dd dd MMMM yyyy NO
yy/MM/dd MMMM d,yyyy NO
yyyy/M/d yyyy'年'M'月'd'日' NO
2.Check firstboot log and qemu-ga log, found there is no error about date in firstboot log, but found error message 'Failed to grab execution mutex. Sytem error 258 ' in qemu-ga.msi log, please refer to screenshot'log-info-for-qemu-ga-not-install-after-rhel9-v2v'
3.Check powershell command in 0001-install-qemu-ga-x86_64-msi, the command is 'powershell.exe -command \"$d = (get-date).AddSeconds(120); $FormatHack = ($([System.Globalization.DateTimeFormatInfo]::CurrentInfo.ShortDatePattern) -replace 'M+/', 'MM/') -replace 'd+/', 'dd/'; schtasks.exe /Create /SC ONCE /ST $d.ToString('HH:mm') /SD $d.ToString($FormatHack) /RU SYSTEM /TN Firstboot-qemu-ga /TR \\"C:\qemu-ga-x86_64.msi /forcerestart /qn /l+*vx C:\qemu-ga-x86_64.msi.log\""'
Actual results:
As above description
Expected results:
Qemu-ga can install in windows guest automatically after v2v conversion when original guest has set some specific date format
Additional info:
I think the problem has relationship with rhev-apt, because qemu-ga also can't installed automatically in windows guest sometimes when I converted the windows guest without rhev-apt installed on rhel8.4 v2v server,details pls refer to the steps to reproduce in https://bugzilla.redhat.com/show_bug.cgi?id=1895323#c36.
But the installation of qemu-ga will be more stable if rhev-apt is existing on rhel8.4 v2v server during conversion, details pls refer to the steps to reproduce in https://bugzilla.redhat.com/show_bug.cgi?id=1895323#c39
- external trackers