| Summary: | (virtio-win-1.1.17)Virtio serial driver fails to be installed on win2k8-32/64. | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | dawu | ||||||||||||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||
| Priority: | urgent | ||||||||||||||||||
| Version: | 6.1 | CC: | lihuang, michen, ndai, qzhang, ykaul | ||||||||||||||||
| Target Milestone: | rc | Keywords: | TestBlocker | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2011-02-10 09:10:03 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||||
Can I see setupapi.app and setupapi.dev files located under %Root%:\Windows\inf\ directory? Thanks, Vadim. Created attachment 475322 [details]
setupapi.app
Created attachment 475323 [details]
setupapi.dev
(In reply to comment #5) > Created attachment 475323 [details] > setupapi.dev Looks like not the vioserial driver, but WdfCoInstaller fails, while trying to install WDF framework. Is it a first-time attempt to install vioserial driver on a freshly installed VM? Dawn, can you please try installing balloon driver on the same VM and share the results? Thanks, Vadim. Hi Vadim, yes, it's a first-time attempt to install vioserial driver on a freshly installed VM with virtio-win 1.1.17, I have tried vioserial driver and balloon driver with latest build 1.1.18 again on a freshly install guest win2k8-64, the same thing happened, all of them can not be installed. Please refer to the update attached "setupapi_bug670462.tar" for details. Best Regards, Dawn Created attachment 475351 [details]
setupapi_bug670462.tar
(In reply to comment #9) > Hi Vadim, > > yes, it's a first-time attempt to install vioserial driver on a freshly > installed > VM with virtio-win 1.1.17, I have tried vioserial driver and balloon driver > with latest build 1.1.18 again on a freshly install guest win2k8-64, the same > thing happened, all of them can not be installed. Hi Dawn, Can you try to install balloon from 1.1.16 on the same VM ? Thank you, Vadim. Please refer to the update > attached "setupapi_bug670462.tar" for details. > > Best Regards, > Dawn Hi Vadim, The same result for balloon driver from 1.1.16 on the same VM, actually this issue happened on 1.1.16 before, but some times it can be installed successfully ,since we were busy finishing whql submission task at that time, we didn't report this issue. Now for 1.1.17 and 1.1.18, we always fail to install it on win2k8-32/64, so we file this bug. Best Regards, Dawn (In reply to comment #12) > Hi Vadim, > > The same result for balloon driver from 1.1.16 on the same VM, actually this > issue happened on 1.1.16 before, but some times it can be installed > successfully ,since we were busy finishing whql submission task at that time, > we didn't report this issue. Now for 1.1.17 and 1.1.18, we always fail to > install it on win2k8-32/64, so we file this bug. > > Best Regards, > Dawn Hi, Dawn. Will it be true to say that this problem is reproducible on W2K8 (SP1 ??) platforms only? Kind Regards, Vadim. (In reply to comment #13) > (In reply to comment #12) > > Hi Vadim, > > > > The same result for balloon driver from 1.1.16 on the same VM, actually this > > issue happened on 1.1.16 before, but some times it can be installed > > successfully ,since we were busy finishing whql submission task at that time, > > we didn't report this issue. Now for 1.1.17 and 1.1.18, we always fail to > > install it on win2k8-32/64, so we file this bug. > > > > Best Regards, > > Dawn > > Hi, Dawn. > > Will it be true to say that this problem is reproducible on W2K8 (SP1 ??) > platforms only? Hi Vadim, yes, this problem is reproducible on w2k8-32/64 sp1 platforms only, win2k8-R2 and the others are OK. Best Regards, Dawn > Kind Regards, > Vadim. > thing happened, all of them can not be installed. Please refer to the update
> attached "setupapi_bug670462.tar" for details.
>
> Best Regards,
> Dawn
Hi Dawn.
Can you please post the setup action log (%windir%\setupact.log) file as well?
Thank you,
Vdim.
Hi Vadim, Setup action log file "setupact.log" has been posted, please refer to the attached. From setupact.log, looks like the KMDF version (1.7.6001) in win2k8 is older than the coinstaller's version (1.9.7600). Actually the system had been upgrade before test. For upgrade KMDF I have tried several methods ,flowing is the details: 1. Enable "Windows Update" and install serial driver again, after a long time, driver install with time out error, seems like the online upgrade failed,please refer to the attached screen shot "serial_driver_install_fail.png". 2. I tried to force a reinstallation of the KMDF runtime by deleting Wdf<MajorVersionNumber><MinorVersionNumber>.sys from the %windir%\system32\drivers folder, however I failed to delete this file with prompt of no permission, actually I logged into system with administrator and the UAC is also disabled. please refer to http://msdn.microsoft.com/en-us/library/ff540793%28v=vs.85%29.aspx 3. I tried the final method which is to download the latest WDK and insall it on the guest, it works, looks like the KMDF upgrade successfully,both serial and balloon drivers can be installed without any error. But you'll have to keep "Windows Update" enabled,seems the KMDF is online upgraded via the installed WDK. please refer to attached "setupact_successful" for the setup action log file after I successfully install serial and balloon driver when installed WDK. Hope above information can be helpful for you. For guest win2k8-64 on host 10.66.72.40, I create another account "dawu" with administrator permission, the password is "Assentor01", you can have a try with this account. ncviewer: 10.66.72.40:1 Best Regards, Dawn Dawn Created attachment 475733 [details]
setupact.log for unsuccessful driver installation
Created attachment 475734 [details]
setupact_successful_afterKMDFupgrade.log
Created attachment 475735 [details]
Serial_install_timeout.png
(In reply to comment #21) > Hi Vadim, > > Setup action log file "setupact.log" has been posted, please refer to the > attached. > > From setupact.log, looks like the KMDF version (1.7.6001) in win2k8 is older > than the coinstaller's version (1.9.7600). Actually the system had been upgrade > before test. > > For upgrade KMDF I have tried several methods ,flowing is the details: > 1. Enable "Windows Update" and install serial driver again, after a long time, > driver install with time out error, seems like the online upgrade failed,please > refer to the attached screen shot "serial_driver_install_fail.png". > > 2. I tried to force a reinstallation of the KMDF runtime by deleting > Wdf<MajorVersionNumber><MinorVersionNumber>.sys from the > %windir%\system32\drivers folder, however I failed to delete this file with > prompt of no permission, actually I logged into system with administrator and > the UAC is also disabled. please refer to > http://msdn.microsoft.com/en-us/library/ff540793%28v=vs.85%29.aspx > > 3. I tried the final method which is to download the latest WDK and insall it > on the guest, it works, looks like the KMDF upgrade successfully,both serial > and balloon drivers can be installed without any error. But you'll have to keep > "Windows Update" enabled,seems the KMDF is online upgraded via the installed > WDK. please refer to attached "setupact_successful" for the setup action log > file after I successfully install serial and balloon driver when installed WDK. > > Hope above information can be helpful for you. > > For guest win2k8-64 on host 10.66.72.40, I create another account "dawu" with > administrator permission, the password is "Assentor01", you can have a try with > this account. ncviewer: 10.66.72.40:1 > > > Best Regards, > Dawn > Dawn Hi Dawn, Thank you for your efforts. Unfortunately, I still have a problem with accessing 10.66.72.40. I'm almost sure it happens due to my vpn connection. Anyway, could you please verify that Windows Update service (Start->Administrative Tools->Services) is not disabled on your system. Actually, "Startup type" for WU must be set to "Automatic" or "Automatic (Delayed Start)" state. Best regards, Vadim. Hi Vadim, I have tried to enable WU service and set "Startup type" as "Automatic" or "Automatic (Delayed Start)" state, serial and balloon driver can be installed successfully on win2k8 32/64. Best Regards, Dawn (In reply to comment #26) > Hi Vadim, > > I have tried to enable WU service and set "Startup type" as "Automatic" or > "Automatic (Delayed Start)" state, serial and balloon driver can be installed > successfully on win2k8 32/64. > > Best Regards, > Dawn (In reply to comment #26) > Hi Vadim, > > I have tried to enable WU service and set "Startup type" as "Automatic" or > "Automatic (Delayed Start)" state, serial and balloon driver can be installed > successfully on win2k8 32/64. > > Best Regards, > Dawn Thank you, Dawn. Yes, it was the problem. AFAIK, it could be a situation when WU is disabled on Vista/W2K8. The real problem is that Vista/W2K8 come with pre-installed WDF 1.7 and should be updated to 1.9. But update is not possible when WU service disabled. Actually, it is not a bug IMO, but should be pointed to our documentation team and to our Installation guys. Kind regards, Vadim. |
Created attachment 474030 [details] serial_driver_install_fail Description of problem: Virtio serial driver for 1.1.17 fails to be installed on win2k8-32/64, please refer to the attached "serial_driver_install_fail" for screen shot. Version-Release number of selected component (if applicable): virtio-win-1.1.17 qemu-kvm-0.12.1.2-2.129.el6 kernel-2.6.32-95.el6 How reproducible: always Steps to Reproduce: 1.Start guest with following command: /usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k8-64-virtio-upgrade.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=00:10:20:3F:21:13,bus=pci.0,addr=0x4,id=net0 -boot c -uuid 1212a123-ea30-4ccf-9ea2-eee6719ea2eb -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -name win2k8-32-serial -vnc :1 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 -chardev pty,id=channel0 -device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0 2.Follow below steps to install virtio serial driver for 1.1.17: Right click "Computer" -> "Properties" -> "Device Manager" -> Right click "PCI Simple Communications Controller" under "Other devices" -> click "Update Driver Software..." -> "Browse my computer for driver software" -> click "Browse" button to select the driver file (or click "Let me pick from a list of device drivers on my computer") -> click "Next" to install driver. Actual results: Driver fails to be installed with error info, please refer to the attached "serial_driver_install_fail" for screen shot. Expected results: Driver should be installed without any error.