Description of problem: Using the tools-ISO 3.3.9 with RHEV-M 3.3 (is30), when you install the tools-ISO, you lose the mouse during the install and can only use the keyboard to restart the VM after the install is completed. I have actually seen this with a few tools-ISO revisions, like 3.3.8 and 3.3.7 and not sure exactly when this became an issue. I tested this with a Win 7x64 guest, but I believe it happens on any other Windows guests. Version-Release number of selected component (if applicable): rhev-guest-tools-iso-3.3-9.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. See above. 2. 3. Actual results: You lose mouse control during the tools-ISO install. Expected results: You don't lose mouse control during the tools-ISO install. Additional info:
Hi Bill A few question: 1. Does it help if you use the keyboard to stop vdservice (windows-key + r ==> cmd (as admin) ==> net stop vdservice ) 2. Does it help if you restart the vdservice ? ==> net start vdservice 2. Does rhev-guest-agent work when that happens ? 3. Can you please provide the installer logs and the vdservice.log/vdagent.log ? Thanks, Uri.
I could not reproduce this on my Win7 x64 VM ( using rhev-guest-tools 3.3-9 ). I tried both installing and upgrading (from rhev-guest-tools 3.2-8)
As Uri could not reproduce. I'm removing the 3.3.0 and blocker flags. Please bring them back if a reproducer is available
We had (I guess) the same bug already reported - bug 988390 which was closed as dup of bug 1025122 and this bug has "fixed in version" - virtio-win-prewhql-0.1-74, reported against RHEL7 and closed as CURRENTRELEASE. This version of virtioser does not seem to be included in RHEVM Guest Tools yet - I found on WinXP virtioser version 51.65.104.7000 from 3.3.-9 Tools while virtio-win-prewhql-0.1-74 has 51.65.104.7400.
Created attachment 847684 [details] Install logs of the VM in question
Awaiting the new version to test this.
ok, 3.4.6, tested with w7 64bit.
Problematic on w2k3 32bit.
10:43 <lveyde> the bug was fixed in build 74, but the latest release haven't updated the drivers for XP and 2K3 ... 10:43 <lveyde> they are still taken from build 70
Since it is a regression, it seems as if we also need the latest serial drivers for 2003/XP. Naturally, it will be shipped for both RHEL7 and RHEL6.
Gal, Vadim, We probably need to add XP/2003 to the build once.
We still build virtio serial device driver for WXP and WNet on a regular basis. It how it looks like in build 92: ├── Wnet │ ├── amd64 │ │ ├── vioser.cat │ │ ├── vioser.inf │ │ ├── vioser.pdb │ │ ├── vioser.sys │ │ ├── vioser-test.exe │ │ ├── vioser-test.pdb │ │ └── WdfCoInstaller01009.dll │ └── x86 │ ├── vioser.cat │ ├── vioser.inf │ ├── vioser.pdb │ ├── vioser.sys │ ├── vioser-test.exe │ ├── vioser-test.pdb │ ├── viostor.cat │ └── WdfCoInstaller01009.dll ├── WXp │ └── x86 │ ├── vioser.cat │ ├── vioser.inf │ ├── vioser.pdb │ ├── vioser.sys │ ├── vioser-test.exe │ ├── vioser-test.pdb │ └── WdfCoInstaller01009.dll
Submission 1700050 and 1700057 pass whql certification so QE are all set. it should be assigned to Jen or mikeb or packaging.. Lev, Since windows XP is not in certification list any more,so there is no way to generate same driver cat file for both winxp and windows 2003 ,pls try to find a workaround. if this change influence you generating MSI package. More details referring to http://msdn.microsoft.com/en-us/library/windows/hardware/dn468203.aspx. Thanks, Mike
Lijin ,pls verify this bug on virtio-win-1.3.1.el7 Thanks, Mike
test with following scenarios,guest works well in both scenarios,can move the mouse correctly. 1.boot guest and install RHEV-toolsSetUp.exe,then upgrade vioserial driver 2.login in guest as administrator,disable UAC,install vioserial driver,then install rhev-agent.msi package info: rhev-guest-tools-iso-3.5-9.el6ev.noarch virtio-win-1.7.3-1.el7.noarch kernel-3.10.0-223.el7.x86_64 qemu-kvm-rhev-2.1.2-20.el7.x86_64 spice-server-0.12.4-9.el7.x86_64 seabios-1.7.5-5.el7.x86_64 qemu-kvm command: /usr/libexec/qemu-kvm -name 096RNGWIN764LQW -enable-kvm -m 2G -smp 2 -uuid fd6d0358-0027-449b-b9e8-71e3b417bf5c -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/096RNGWIN764LQW,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=096RNGWIN764LQW,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/usr/share/virtio-win/virtio-win.iso,if=none,id=drive-fdc0-0-0,format=raw,cache=none -device ide-cd,drive=drive-fdc0-0-0,id=cd11 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:39:65:9b:1d,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -spice disable-ticketing,port=5900 -vga qxl -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,path=/tmp/tt0,server,nowait,id=channel0 -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -drive file=/usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso,if=none,id=driver-cd -device ide-cd,drive=driver-cd,id=cd1,bus=ide.0,unit=1 -monitor stdio
Move status to Verified according to above comment
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0289.html