Not a problem I am happy to help in any way that I can. To Clarify I executed the same tests with the same results using both RHEV and ovirt. I am using: RHEV 3.0.1 oVirt (FC16 + oVirt Nightly builds)
Node wise I use EL6 in my case Scientific Linux 6.x. The behavior I observe with the mouse in windows or legacy linux guests for example with a spice console is: - Erratic mouse movements - mouse jumps all over the spice console randomly - Mouse stuck to console border - the mouse simply sticks to the top of the console (EG: first row of pixels) and moves left to right there only. - No left or right mouse input seems to be recognized in either of the above cases The spice console used in both the case of RHEV or ovirt: --> http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/rhevm-spice-client-3.0-21.el6.src.rpm For ovirt I rebuild the above rpm and extract the msi and cabs then place them into the appropriate (/usr/share/rhevm/rhevm.ear/...) locations When testing outside of ovirt I have used both spiec and spicey to connect to the guest console: Installed spice packages versions on my EL6 (SL6.2) client in that case: spice-gtk-tools-0.6-2.el6.x86_64 spice-glib-0.6-2.el6.x86_64 spice-vdagent-0.8.1-3.el6.x86_64 spice-xpi-2.4-4.el6.x86_64 spice-client-0.8.2-7.el6.x86_64 spice-server-0.8.2-5.el6.x86_64 spice-gtk-0.6-2.el6.x86_64 Installed spice packages on the EL6 (SL6.2) nodes spice-server-0.8.2-5.el6.x86_64 spice-vdagent-0.8.1-3.el6.x86_64 - Chris -----Original Message----- From: Hans de Goede [mailto:hdego...@redhat.com] Sent: Wednesday, February 01, 2012 3:36 AM To: Brown, Chris (GE Healthcare) Cc: Itamar Heim; André Felício; spice-devel@lists.freedesktop.org; us...@ovirt.org Subject: Re: [Spice-devel] [Users] oVirt console plans Hi, On 01/31/2012 07:58 PM, Hans de Goede wrote: > Hi, > > On 01/31/2012 05:40 PM, Brown, Chris (GE Healthcare) wrote: >> at the cli level (winxp guest): >> >> Spice Console: >> /usr/libexec/qemu-kvm -S -M rhel6.2.0 -cpu Nehalem -enable-kvm -m >> 1024 -smp 1,sockets=1,cores=1,threads=1 -name winxp -uuid >> 02465bab-b7f5-49ce-a1ec-4ffbe933a989 -smbios type=1,manufacturer=Red >> Hat,product=RHEV >> Hypervisor,version=6.2-0.1.rolling,serial=FF200008-FFFF-FFFF-FFFF-002 >> 1286B0EA2_00:21:28:6B:0E:9E,uuid=02465bab-b7f5-49ce-a1ec-4ffbe933a989 >> -nodefconfig -nodefaults -chardev >> socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server >> ,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc >> base=2012-01-31T16:37:58,driftfix=slew -no-shutdown -device >> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 >> -drive >> file=/rhev/data-center/42e81130-4b83-11e1-b521-00144f8d7c32/d5dcf4fd- >> 1650-4b40-8fe3-b17f95e3d5c5/images/dba69993-fb0b-4205-8269-f192f5ac1f >> 9a/90909c9b-aee9-4da1-a417-63bdd3ed5396,if=none,id=drive-ide0-0-0,for >> mat=raw,serial=05-8269-f192f5ac1f9a,cache=none,werror=stop,rerror=sto >> p,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-id > e0-0-0,id=ide0-0-0,bootindex=2 -drive > 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,bootindex= > 1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:39:6f:01,bus=pci.0 > ,addr=0x3 -chardev > socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/winxp.com.r > edhat.rhevm.vdsm,server,nowait -device > virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann > el0,name=com.redhat.rhevm.vdsm -chardev > spicevmc,id=charchannel1,name=vdagent -device > virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=chann > el1,name=com.redhat.spice.0 -usb -spice > port=5900,tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tl > s-channel=main,tls-channel=inputs -k en-us -vga qxl -global > qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4 >> > > Thanks, that explains, no usb-tablet (which is ok for spice since the > agent is better, and the usb-tablet causes a significant cpu usage > even when idle), but also no ps2 mouse, so no mouse emulation at all. I > believe this is an ovirt bug. On second thought, scrap that. My bad, given how the commandline has -nodefconfig -nodefaults, which means no default devices are created and there was no -device for a ps2 mouse on the cmdline I assumed that there would be no ps2 mouse emulation enabled in the vm. However I'm wrong my reasoning was too logical and the qemu cmdline is not always logical... Despite the -nodefconfig -nodefaults the vm will include ps2 mouse emulation. So this is *not* an oVirt bug. Still this exercise was not without result, what it shows is that using spice with a relative mouse (or server mode mouse in spice terms) is not working for you Chris. This probably is an issue with the spice client you are using. Chris, I've some questions to help us debug this: 1) In what way is the mouse not working, not working at all, or ... ? 2) Which client are you using (spicec, spicy, virt-viewer)? 3) Which version of this client are you using? 4) On which platform/os is the client running 5) Did you build the client from source, or downloaded it somewhere, if you downloaded it, where from? 6) Which version of qemu and spice-server are you using on the host, if the hosed is rpm based, can you please do rpm -q qemu spice-server and include the output in your reply? Regards, Hans _______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
