[feedback needed] VirtIO Windows Drivers - new installer

Good morning - I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service. I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help. The system is 2012 R2 fully patched. Thank you for all your hard work! [image: 2019-10-30_11-12-00.png]

Hi Steve, Thanks for the feedback, 2012r2 is supported and should work. I tried it now on my own ovirt local installation and all went well. Can you please try to run the installation from cmd\powershell and generate logs, You can do so by running: msiexec /i [PATH TO MSI] /L*V [PATH TO SAVE LOGS] Here is a guide: https://www.advancedinstaller.com/user-guide/qa-log.html When you are done please send us the logs and I will try and figure it out Good luck, and thanks for the feedback Gal On Wed, Oct 30, 2019 at 5:55 PM Steve Graham <sdg1972@gmail.com> wrote:
Good morning -
I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service.
I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help.
The system is 2012 R2 fully patched.
Thank you for all your hard work!
[image: 2019-10-30_11-12-00.png] _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VOL3355YK2S76R...

Gal, etc - Attached are the install logs from install attempts on 2012R2 and Win10 instances. I had the same results with both. I'm able to dig through the folders and manually install each INF but the executable doesn't pan out and I don't get the guest agent, etc. Thank you Steve On Thu, Oct 31, 2019 at 9:12 AM Gal Zaidman <gzaidman@redhat.com> wrote:
Hi Steve,
Thanks for the feedback, 2012r2 is supported and should work. I tried it now on my own ovirt local installation and all went well.
Can you please try to run the installation from cmd\powershell and generate logs, You can do so by running: msiexec /i [PATH TO MSI] /L*V [PATH TO SAVE LOGS] Here is a guide: https://www.advancedinstaller.com/user-guide/qa-log.html
When you are done please send us the logs and I will try and figure it out
Good luck, and thanks for the feedback Gal
On Wed, Oct 30, 2019 at 5:55 PM Steve Graham <sdg1972@gmail.com> wrote:
Good morning -
I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service.
I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help.
The system is 2012 R2 fully patched.
Thank you for all your hard work!
[image: 2019-10-30_11-12-00.png] _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VOL3355YK2S76R...

Hi Steve, Thanks for the logs. I can see that the installer tried to install the drivers\agents, installed balloon, qemufwcfg succesfully but *couldn't find a device for the drivers*: *netkvm*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\netkvm.inf_amd64_c316d81195f48726\netkvm.inf" on the Machine. *pvpanic*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\pvpanic.inf_amd64_e493cebce79d8b24\pvpanic.inf" on the Machine. *qemupciserial*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\qemupciserial.inf_amd64_eaede2016b3cdb88\qemupciserial.inf" on the Machine. *qxldod*" No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\qxldod.inf_amd64_268918d1049a0130\qxldod.inf" on the Machine. *viorng*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\viorng.inf_amd64_e56fd31caf25cfdc\viorng.inf" on the Machine. *vioscsi*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vioscsi.inf_amd64_e6dc8ad10aca370e\vioscsi.inf" on the Machine. *vioser*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vioser.inf_amd64_ec2c73376757f2f6\vioser.inf" on the Machine. *viostor*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\viostor.inf_amd64_f8d533b832f6ca6a\viostor.inf" on the Machine. First of all, I will open a bug to add better error messages to help debug does issues. Second, it is weird for me that you are able to install the drivers manually with the INF file, are you sure they got installed? notice that the fact that you are able to right-click on an INF file, install it, and get "The operation completed successfully" message doesn't mean that the driver got installed. So to follow up and debug that issue, because I can't reproduce on my env, can you do the following *on a fresh windows VM with no drivers*: 1. open up a powershell prompt and run: driverquery.exe /V /FO list > list_no_drivers.txt 2. on the CD go to a driver that is not installed folder (make sure that it is not installed by mistake of the output of the previous command), like vioserial, find the correct folder, and install the driver, then run: driverquery.exe /V /FO list > list_no_drivers2.txt and check to see if the driver got installed. 3. get devcon.exe and run: devcon.exe hwids * > hw_ids.txt please send me the 3 files to have a look. Adding virtio-win and @Vadim Rozenfeld <vrozenfe@redhat.com> , Do you know what can be the cause of the drivers not finding matching devices? Thanks On Thu, Oct 31, 2019 at 8:08 PM Steve Graham <sdg1972@gmail.com> wrote:
Gal, etc -
Attached are the install logs from install attempts on 2012R2 and Win10 instances. I had the same results with both. I'm able to dig through the folders and manually install each INF but the executable doesn't pan out and I don't get the guest agent, etc.
Thank you
Steve
On Thu, Oct 31, 2019 at 9:12 AM Gal Zaidman <gzaidman@redhat.com> wrote:
Hi Steve,
Thanks for the feedback, 2012r2 is supported and should work. I tried it now on my own ovirt local installation and all went well.
Can you please try to run the installation from cmd\powershell and generate logs, You can do so by running: msiexec /i [PATH TO MSI] /L*V [PATH TO SAVE LOGS] Here is a guide: https://www.advancedinstaller.com/user-guide/qa-log.html
When you are done please send us the logs and I will try and figure it out
Good luck, and thanks for the feedback Gal
On Wed, Oct 30, 2019 at 5:55 PM Steve Graham <sdg1972@gmail.com> wrote:
Good morning -
I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service.
I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help.
The system is 2012 R2 fully patched.
Thank you for all your hard work!
[image: 2019-10-30_11-12-00.png] _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VOL3355YK2S76R...

On Sun, 2019-11-03 at 17:20 +0200, Gal Zaidman wrote:
Hi Steve, Thanks for the logs. I can see that the installer tried to install the drivers\agents, installed balloon, qemufwcfg succesfully but couldn't find a device for the drivers: netkvm: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\netkvm.inf_amd64_c316 d81195f48726\netkvm.inf" on the Machine. pvpanic: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\pvpanic.inf_amd64_e49 3cebce79d8b24\pvpanic.inf" on the Machine. qemupciserial: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\qemupciserial.inf_amd 64_eaede2016b3cdb88\qemupciserial.inf" on the Machine. qxldod" No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\qxldod.inf_amd64_2689 18d1049a0130\qxldod.inf" on the Machine. viorng: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\viorng.inf_amd64_e56f d31caf25cfdc\viorng.inf" on the Machine. vioscsi: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vioscsi.inf_amd64_e6d c8ad10aca370e\vioscsi.inf" on the Machine. vioser: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vioser.inf_amd64_ec2c 73376757f2f6\vioser.inf" on the Machine. viostor: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\viostor.inf_amd64_f8d 533b832f6ca6a\viostor.inf" on the Machine.
First of all, I will open a bug to add better error messages to help debug does issues.
Second, it is weird for me that you are able to install the drivers manually with the INF file, are you sure they got installed? notice that the fact that you are able to right-click on an INF file, install it, and get "The operation completed successfully" message doesn't mean that the driver got installed.
So to follow up and debug that issue, because I can't reproduce on my env, can you do the following on a fresh windows VM with no drivers: 1. open up a powershell prompt and run: driverquery.exe /V /FO list > list_no_drivers.txt 2. on the CD go to a driver that is not installed folder (make sure that it is not installed by mistake of the output of the previous command), like vioserial, find the correct folder, and install the driver, then run: driverquery.exe /V /FO list > list_no_drivers2.txt and check to see if the driver got installed. 3. get devcon.exe and run: devcon.exe hwids * > hw_ids.txt
please send me the 3 files to have a look.
Adding virtio-win and @Vadim Rozenfeld , Do you know what can be the cause of the drivers not finding matching devices?
There can be several reasons for that. It can be that the relevant device is just missing, wrong platform version or justmismatching between platform and driver bitness. Please try installing the drivers manually and see if it works fine. Checking device installation log file SetupAPI.dev.log is always a quite useful thing to understand the installation problems better. Best,Vadim.
Thanks On Thu, Oct 31, 2019 at 8:08 PM Steve Graham <sdg1972@gmail.com> wrote:
Gal, etc - Attached are the install logs from install attempts on 2012R2 and Win10 instances. I had the same results with both. I'm able to dig through the folders and manually install each INF but the executable doesn't pan out and I don't get the guest agent, etc.
Thank you
Steve On Thu, Oct 31, 2019 at 9:12 AM Gal Zaidman <gzaidman@redhat.com> wrote:
Hi Steve, Thanks for the feedback, 2012r2 is supported and should work. I tried it now on my own ovirt local installation and all went well.
Can you please try to run the installation from cmd\powershell and generate logs, You can do so by running: msiexec /i [PATH TO MSI] /L*V [PATH TO SAVE LOGS] Here is a guide: https://www.advancedinstaller.com/user-guide/qa-log.html
When you are done please send us the logs and I will try and figure it out
Good luck, and thanks for the feedback Gal On Wed, Oct 30, 2019 at 5:55 PM Steve Graham <sdg1972@gmail.com> wrote:
Good morning - I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win- guest-tools" service.
I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help.
The system is 2012 R2 fully patched.
Thank you for all your hard work!
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VOL3355YK2S76R...

Good afternoon - I completely rebuilt the host and virtual machine and the installation went through perfectly. I performed a few rollbacks and patches and it still installed without issue. Not sure what I did differently but I'm not complaining. Thanks for your help and thanks again for all the hard work. Steve On Mon, Nov 4, 2019 at 3:41 AM Vadim Rozenfeld <vrozenfe@redhat.com> wrote:
On Sun, 2019-11-03 at 17:20 +0200, Gal Zaidman wrote:
Hi Steve,
Thanks for the logs. I can see that the installer tried to install the drivers\agents, installed balloon, qemufwcfg succesfully but *couldn't find a device for the drivers*: *netkvm*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\netkvm.inf_amd64_c316d81195f48726\netkvm.inf" on the Machine. *pvpanic*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\pvpanic.inf_amd64_e493cebce79d8b24\pvpanic.inf" on the Machine. *qemupciserial*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\qemupciserial.inf_amd64_eaede2016b3cdb88\qemupciserial.inf" on the Machine. *qxldod*" No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\qxldod.inf_amd64_268918d1049a0130\qxldod.inf" on the Machine. *viorng*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\viorng.inf_amd64_e56fd31caf25cfdc\viorng.inf" on the Machine. *vioscsi*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vioscsi.inf_amd64_e6dc8ad10aca370e\vioscsi.inf" on the Machine. *vioser*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vioser.inf_amd64_ec2c73376757f2f6\vioser.inf" on the Machine. *viostor*: No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\viostor.inf_amd64_f8d533b832f6ca6a\viostor.inf" on the Machine.
First of all, I will open a bug to add better error messages to help debug does issues.
Second, it is weird for me that you are able to install the drivers manually with the INF file, are you sure they got installed? notice that the fact that you are able to right-click on an INF file, install it, and get "The operation completed successfully" message doesn't mean that the driver got installed.
So to follow up and debug that issue, because I can't reproduce on my env, can you do the following *on a fresh windows VM with no drivers*: 1. open up a powershell prompt and run: driverquery.exe /V /FO list > list_no_drivers.txt 2. on the CD go to a driver that is not installed folder (make sure that it is not installed by mistake of the output of the previous command), like vioserial, find the correct folder, and install the driver, then run: driverquery.exe /V /FO list > list_no_drivers2.txt and check to see if the driver got installed. 3. get devcon.exe and run: devcon.exe hwids * > hw_ids.txt
please send me the 3 files to have a look.
Adding virtio-win and @Vadim Rozenfeld <vrozenfe@redhat.com> , Do you know what can be the cause of the drivers not finding matching devices?
There can be several reasons for that. It can be that the relevant device is just missing, wrong platform version or just mismatching between platform and driver bitness. Please try installing the drivers manually and see if it works fine. Checking device installation log file *SetupAPI.dev.log * is always a quite useful thing to understand the installation problems better.
Best, Vadim.
Thanks
On Thu, Oct 31, 2019 at 8:08 PM Steve Graham <sdg1972@gmail.com> wrote:
Gal, etc -
Attached are the install logs from install attempts on 2012R2 and Win10 instances. I had the same results with both. I'm able to dig through the folders and manually install each INF but the executable doesn't pan out and I don't get the guest agent, etc.
Thank you
Steve
On Thu, Oct 31, 2019 at 9:12 AM Gal Zaidman <gzaidman@redhat.com> wrote:
Hi Steve,
Thanks for the feedback, 2012r2 is supported and should work. I tried it now on my own ovirt local installation and all went well.
Can you please try to run the installation from cmd\powershell and generate logs, You can do so by running: msiexec /i [PATH TO MSI] /L*V [PATH TO SAVE LOGS] Here is a guide: https://www.advancedinstaller.com/user-guide/qa-log.html
When you are done please send us the logs and I will try and figure it out
Good luck, and thanks for the feedback Gal
On Wed, Oct 30, 2019 at 5:55 PM Steve Graham <sdg1972@gmail.com> wrote:
Good morning -
I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service.
I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help.
The system is 2012 R2 fully patched.
Thank you for all your hard work!
[image: 2019-10-30_11-12-00.png] _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VOL3355YK2S76R...
participants (3)
-
Gal Zaidman
-
Steve Graham
-
Vadim Rozenfeld