Hide Forgot
Description of problem: instlling virtio-serial driver will not work unitl restart the guest(e.g:win2008-64bit). Version-Release number of selected component (if applicable): host info: 2.6.32-425.el6.x86_64 qemu-kvm-0.12.1.2-2.415.el6.x86_64 guest info: win2008-64bit virtio-win-prewhql-0.1-72(virtio-serial driver) How reproducible: 100% Steps to Reproduce: 1.boot a win2008-64bit guest with virtio-serial. e.g:...-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=org.qemu.guest_agent.0,bus=virtio-serial0.0,id=port1,nr=1 2.install the virtio-serial driver(virtio-win-prewhql-0.1-72). ...\virtio-win-prewhql-0.1-72\Wnet\amd64\serial 3. Actual results: after step 2, after install virtio-serial driver, it will prompt a message, like: the hardware your installing will not work until restart your computer. Expected results: it should work well after complete install immediately, no need to restart it. Additional info: Trying results for windows guest with virtio-serial driver(virtio-win-prewhql-0.1-72): win8-64-virtio.qcow2 ------- work well win8-32-virtio.qcow2 ------- work well win2008r2-64-virtio.qcow2 ------- work well win7-32-virtio.qcow2 ------- work well win2008-32-virtio.qcow2 ------- work well win2008-64.qcow2 <----------------- need to restart win7-64-virtio.qcow2 ------- work well win2012-64-virtio.qcow2 ------- work well win2012r2-64-virtio.qcow2 ------- work well
> Actual results: > after step 2, after install virtio-serial driver, it will prompt a message, > like: the hardware your installing will not work until restart your computer. It means that someone was keeping an open handle or reference to virtio-serial. IIRC installer should be able to handle this condition by closing such applications. Vadim.
Does the win2008-64.qcow2 image have another service that uses the virtio-serial? Like spice's vdagent or ovirt-guest-agent?
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
(In reply to Gal Hammer from comment #2) > Does the win2008-64.qcow2 image have another service that uses the > virtio-serial? Like spice's vdagent or ovirt-guest-agent? No other service to use it, we always met this issue on win2008-64bit guest.
It seems that the reboot is required after an upgrade of the WDF: From the %windir%\setupact.log file: WdfCoInstaller: [12/26/2013 10:36.35.062] ReadComponents: WdfSection for Driver Service VirtioSerial using KMDF lib version Major 0x1, minor 0x9 WdfCoInstaller: [12/26/2013 10:36.35.062] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7600 WdfCoInstaller: [12/26/2013 10:36.35.078] DIF_INSTALLDEVICE: KMDF in-memory version: 1.7.6001 WdfCoInstaller: [12/26/2013 10:36.35.109] DIF_INSTALLDEVICE: KMDF on-disk version: 1.7.6001 WdfCoInstaller: [12/26/2013 10:36.35.109] Service Wdf01000 is running WdfCoInstaller: [12/26/2013 10:36.35.140] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller's version.
Created attachment 841879 [details] setupact.log
Created attachment 841880 [details] setupapi.dev.log
Installation on Windows 2008 64-bit might requires an upgrade of the WDF driver framework. If such an upgrade is performed then a restart is needed in order to complete the install process.