Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hello,
Reproduced this issue on virtio-win-0.1.110 version.
Verified this issue on virtio-win-0.1.112 verion.Steps same as comment #0.
Actual results:
Installer does not stuck on "Setup is starting Windows" page but another issues occur. According to the comment#0 step, after press "S" button, press the enter, the message "The file txtsetup.oem could not be found" will show. Detail please refer to picture1. Then Press enter to continue install, system will report message "Setup did not find any hard disk drivers installed in your computer". Detail please refer to the attached picture2.
Add I also tried install viostor to a virtio-blk device in pre-installed winXP OS, It's successful.
Best Regards!
Peixiu Hou
(In reply to Peixiu Hou from comment #7)
> Reproduced this issue on virtio-win-0.1.126 verion. Steps same as comment#0.
> The actual result is same with comment#4.
Can you point to the relevant vfd file location?
Thanks,
Vadim.
(In reply to Vadim Rozenfeld from comment #8)
> (In reply to Peixiu Hou from comment #7)
> > Reproduced this issue on virtio-win-0.1.126 verion. Steps same as comment#0.
> > The actual result is same with comment#4.
>
> Can you point to the relevant vfd file location?
> Thanks,
> Vadim.
Hi Vadim,
The vfd file location is virtio-win-prewhql-126/Wxp/x86/.
virtio-win-prewhql-126.vfd including file as follows:
viostor.cat
viostor.inf
viostor.pdb
viostor.sys
WdfCoInstaller01009.dll
Best Regards~
Peixiu Hou
(In reply to Peixiu Hou from comment #10)
> (In reply to Vadim Rozenfeld from comment #8)
> > (In reply to Peixiu Hou from comment #7)
> > > Reproduced this issue on virtio-win-0.1.126 verion. Steps same as comment#0.
> > > The actual result is same with comment#4.
> >
> > Can you point to the relevant vfd file location?
> > Thanks,
> > Vadim.
>
> Hi Vadim,
>
> The vfd file location is virtio-win-prewhql-126/Wxp/x86/.
> virtio-win-prewhql-126.vfd including file as follows:
> viostor.cat
> viostor.inf
> viostor.pdb
> viostor.sys
> WdfCoInstaller01009.dll
>
> Best Regards~
> Peixiu Hou
That's good, but can you please attach vfd image for the future investigation?
I'm mostly interested in seeing contents of txtsetup.oem file.
Btw, wdf coinstaller is not required for viostor driver, and driver's binaries and inf file must be placed under \i386\WinXP location
Best regards,
Vadim.
Hi Vadiam,
I tried to test with virtio-win-1.9.0-2, also can reproduce this issue.
Used vfd file is /usr/share/virtio-win/virtio-win-1.9.0_x86.vfd.
Best Regards~
Peixiu Hou
Even though WinXP EOL can we give it another try on rhel 7.5 and virtio-win drivers from virtio-win-1.9.3 (tried several times but cannot reproduce it so far).
Thanks,
Vadim.
(In reply to Vadim Rozenfeld from comment #15)
> Even though WinXP EOL can we give it another try on rhel 7.5 and virtio-win
> drivers from virtio-win-1.9.3 (tried several times but cannot reproduce it
> so far).
Sure.
I will update when result come out.
Thanks
I can reproduce this issue with build 110,hit "The file txtsetup.oem could not be found" error.
Can NOT reproduce it with virtio-win-1.9.0-3.el7.noarch, guest can be installed correctly.
So this issue should be fixed already.
Close this bug.
(In reply to lijin from comment #17)
> I can reproduce this issue with build 110,hit "The file txtsetup.oem could
> not be found" error.
>
> Can NOT reproduce it with virtio-win-1.9.0-3.el7.noarch, guest can be
> installed correctly.
>
> So this issue should be fixed already.
>
> Close this bug.
Thanks a lot.
Vadim.
Created attachment 1109157 [details] picture1