I would agree with this assessment. Spice while nice is an issue with windows and older linux/etc guests as well. A few issues until the qxl paravirtual guest drivers are in place in the guest: - windows guests --> erratic mouse movement and controls = install via KBD and add drivers by hand/kbd - fix for windows guests = use templates or load from images that have been syspreped or slipstreamed w/driver - older linux guests = ? EX: custom spins or old 2.4 based stuff - non linux guests bsd/solaris/android = ? Just my 2 cents, but VNC or vrdp(VirtualBox) has worked well with all of the above guests when it concerns remote consoles. - Chris -----Original Message----- From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of André Felício Sent: Monday, January 30, 2012 1:10 PM To: users(a)ovirt.org Subject: [Users] oVirt console plans There are plans to enable other types of console for oVirt? Access by VNC or RPD? There are many SO (windows) that access by SPICE is a little tricky. VNC seems to be a more portable. -- At.te, André Felício http://www.felicio.com.br _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

There are plans to enable other types of console for oVirt? Access by VNC or RPD? There are many SO (windows) that access by SPICE is a little tricky.

VNC seems to be a more portable.

>> There are many SO (windows) that access by SPICE is a little tricky. > > What's tricky with Spice? If there's anything we can do to help make Spice > easier to use, let us know. I tried compiling spice-xpi for windows it several times and it still fails. Anyone have the spice-client and spice-xpi compiled for windows?

OVirt appears VNC console in the option but does not have a way to access it over webadmin.

You can just rebuild the current RHEV spice-xpi source RPM and drop the resulting files into you ovirt install. - Found here: http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/r... - rpmbuild --rebuild rhevm-spice-client-3.0-21.el6.src.rpm (install dependent packages via yum if build fails due to deps, not that many needed) - unpack the resulting spice-xpi client isntallers and cabs from the rpms using: rpm2cpio - rpm2cpio <nameofrpm> | cpio -ivd - place the files into their corresponding locations on your ovirt install. - you can find the paths where things go via rpm -qlp <packagename> replace "rhevm" with "engine" pathing wise - Pathing on ovirt should be something like: --> /usr/share/ovirt-engine/engine.ear/engineanger.ear/ --> /usr/share/ovirt-engine/enginer.ear/userportal.ear/ovirt.org... -restart jboss and you will be good to go

>> There are many SO (windows) that access by SPICE is a little tricky. > > What's tricky with Spice? If there's anything we can do to help make > Spice easier to use, let us know. I tried compiling spice-xpi for windows it several times and it still fails. Anyone have the spice-client and spice-xpi compiled for windows?

OVirt appears VNC console in the option but does not have a way to access it over webadmin.

On 01/31/2012 07:38 AM, Brown, Chris (GE Healthcare) wrote: >I did some more extensive testing tonight to see how many guests would have issues with a SPICE based console. This testing was specifically during guest OS install time. On how many of them was the Spice guest agent installed? Without it, you will not have client-side mouse, which contributes to a much better mouse behaviour. > >Here is the list and the results >- Red Hat 7.3 --> Mouse unusable >- Red Hat 9 --> Mouse unusable >- Fedora core 1 - 14 --> Mouse unusable >- Fedora core 15 Mouse useable >- Fedora core 16 Mouse useable >- Red Hat Enterprise 3.x --> Mouse unusable >- Red Hat Enterprise 4.x --> Mouse unusable >- Red Hat Enterprise 5.x --> Mouse unusable >- Red Hat Enterpise 6.x --> Mouse useable >- SLES 10 --> Mouse unusable >- SLES 11 --> Mouse unusable >- SLES 11 SP1 --> Mouse unusable >- OpenSUSE 11.1 --> Mouse unusable >- OpenSUSE 11.2 --> Mouse useable >- OpenSUSE 11.3 --> Mouse useable >- OpenSUSE 11.4 --> Mouse useable

>- Windows 2000 SP4 --> Mouse unusable >- Windows XP --> Mouse unusable >- Windows Vista --> Mouse unusable >- Windows Server 2003 --> Mouse unusable >- Windows Server 2003 R2 --> Mouse unusable >- Windows Server 2008 --> Mouse unusable >- Windows Server 2008 R2 --> Mouse unusable

>- Solaris 10 Update9 --> Mouse unusable >- Solaris 11 Express --> Mouse unusable >- Solaris 11 --> Mouse unusable Out of curiosity, and assuming you haven't spent all night on this - how are you testing so many different operating systems? And moreover, if you are already into testing so many, any other issues encountered? Networking works OK across all of them? Impressive work, Y. > >Of the above guests all of them were fine with a VNC console. >The windows guests could be loaded via vnc then the qxl drivers installed after install and all was well. >However the older Linux guests and all solaris guests were not able to be made to work with spice during run time forcing VNC to be used if mouse interaction is required. > >IMHO if spice will be the only supported console type then some work needs to be done to take older linux guests and other operating systems into consideration. >This particularly applies to the PuP when developers or users are loading guests from scratch. > >- Chris > >________________________________ > >From: Brown, Chris (GE Healthcare) >Sent: Mon 1/30/2012 2:09 PM >To: 'Itamar Heim'; André Felício >Cc: spice-devel(a)lists.freedesktop.org; users(a)ovirt.org; David Blechter >Subject: RE: [Users] oVirt console plans > > > >You can just rebuild the current RHEV spice-xpi source RPM and drop the resulting files into you ovirt install. >- Found here: http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/r... >- rpmbuild --rebuild rhevm-spice-client-3.0-21.el6.src.rpm (install dependent packages via yum if build fails due to deps, not that many needed) >- unpack the resulting spice-xpi client isntallers and cabs from the rpms using: rpm2cpio >- rpm2cpio<nameofrpm> | cpio -ivd >- place the files into their corresponding locations on your ovirt install. >- you can find the paths where things go via rpm -qlp<packagename> replace "rhevm" with "engine" pathing wise >- Pathing on ovirt should be something like: >--> /usr/share/ovirt-engine/engine.ear/engineanger.ear/ >--> /usr/share/ovirt-engine/enginer.ear/userportal.ear/ovirt.org... >-restart jboss and you will be good to go > >- Chris > >-----Original Message----- >From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Itamar Heim >Sent: Monday, January 30, 2012 2:01 PM >To: André Felício >Cc: spice-devel(a)lists.freedesktop.org; users(a)ovirt.org; David Blechter >Subject: Re: [Users] oVirt console plans > >On 01/30/2012 09:58 PM, André Felício wrote: >>>>There are many SO (windows) that access by SPICE is a little tricky. >>>What's tricky with Spice? If there's anything we can do to help make >>>Spice easier to use, let us know. >>I tried compiling spice-xpi for windows it several times and it still >>fails. Anyone have the spice-client and spice-xpi compiled for >>windows? >cc'ing spice-devel to provide input on status/availability of spice-xpi for windows and/or spice-activex. > >>OVirt appears VNC console in the option but does not have a way to >>access it over webadmin. >_______________________________________________ >Users mailing list &gt;Users(a)ovirt.org >http://lists.ovirt.org/mailman/listinfo/users > > >_______________________________________________ >Users mailing list &gt;Users(a)ovirt.org >http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Spice-devel mailing list Spice-devel(a)lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel

I did some more extensive testing tonight to see how many guests would have issues with a SPICE based console. This testing was specifically during guest OS install time. Here is the list and the results - Red Hat 7.3 --> Mouse unusable - Red Hat 9 --> Mouse unusable - Fedora core 1 - 14 --> Mouse unusable

- Fedora core 15 Mouse useable - Fedora core 16 Mouse useable - Red Hat Enterprise 3.x --> Mouse unusable - Red Hat Enterprise 4.x --> Mouse unusable - Red Hat Enterprise 5.x --> Mouse unusable - Red Hat Enterpise 6.x --> Mouse useable - SLES 10 --> Mouse unusable - SLES 11 --> Mouse unusable - SLES 11 SP1 --> Mouse unusable - OpenSUSE 11.1 --> Mouse unusable - OpenSUSE 11.2 --> Mouse useable - OpenSUSE 11.3 --> Mouse useable - OpenSUSE 11.4 --> Mouse useable

Hi, On 01/31/2012 06:38 AM, Brown, Chris (GE Healthcare) wrote: > I did some more extensive testing tonight to see how many guests > would have issues with a SPICE based console. This testing was > specifically during guest OS install time. > > Here is the list and the results > - Red Hat 7.3 --> Mouse unusable > - Red Hat 9 --> Mouse unusable > - Fedora core 1 - 14 --> Mouse unusable These are all past there EOL, also see my remark below which certainly applies to these. > - Fedora core 15 Mouse useable > - Fedora core 16 Mouse useable > - Red Hat Enterprise 3.x --> Mouse unusable > - Red Hat Enterprise 4.x --> Mouse unusable > - Red Hat Enterprise 5.x --> Mouse unusable > - Red Hat Enterpise 6.x --> Mouse useable > - SLES 10 --> Mouse unusable > - SLES 11 --> Mouse unusable > - SLES 11 SP1 --> Mouse unusable > - OpenSUSE 11.1 --> Mouse unusable > - OpenSUSE 11.2 --> Mouse useable > - OpenSUSE 11.3 --> Mouse useable > - OpenSUSE 11.4 --> Mouse useable Looking at the above list it sounds to me like you had the usb-tablet enabled in the vm config, that is not a good idea for Linux versions which have an xorg which does not support device hotplug. May I suggest that you re-run the tests without the usb-tablet enabled?

This may also help with the problems with other operating systems. Regards, Hans

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-0021286B0EA2_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-f192f5ac1f9a/90909c9b-aee9-4da1-a417-63bdd3ed5396,if=none,id=drive-ide0-0-0,format=raw,serial=05-8269-f192f5ac1f9a,cache=none,werror=stop,rerror=stop,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-id

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-0021286B0EA2_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-f192f5ac1f9a/90909c9b-aee9-4da1-a417-63bdd3ed5396,if=none,id=drive-ide0-0-0,format=raw,serial=05-8269-f192f5ac1f9a,cache=none,werror=stop,rerror=stop,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.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -usb -spice port=5900,tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-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.

Regards, Hans _______________________________________________ Spice-devel mailing list Spice-devel(a)lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel

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-0021286B0EA2_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-f192f5ac1f9a/90909c9b-aee9-4da1-a417-63bdd3ed5396,if=none,id=drive-ide0-0-0,format=raw,serial=05-8269-f192f5ac1f9a,cache=none,werror=stop,rerror=stop,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.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -usb -spice port=5900,tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-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.

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/r... 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:hdegoede@redhat.com] Sent: Wednesday, February 01, 2012 3:36 AM To: Brown, Chris (GE Healthcare) Cc: Itamar Heim; André Felício; spice-devel(a)lists.freedesktop.org; users(a)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

On 02/01/2012 07:04 PM, Brown, Chris (GE Healthcare) wrote: > 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) Hans - is there any downside/conflict if usbtablet is passed when local mouse/agent is used? if not, we could pass usbtablet when booting a guest not known to have the agent installed from previous run?

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:

From that angle developers using the PuP are still have a use case in that regard.

I did some more extensive testing tonight to see how many guests would have issues with a SPICE based console. This testing was specifically during guest OS install time. Here is the list and the results - Red Hat 7.3 --> Mouse unusable - Red Hat 9 --> Mouse unusable - Fedora core 1 - 14 --> Mouse unusable

- Fedora core 15 Mouse useable - Fedora core 16 Mouse useable - Red Hat Enterprise 3.x --> Mouse unusable - Red Hat Enterprise 4.x --> Mouse unusable - Red Hat Enterprise 5.x --> Mouse unusable - Red Hat Enterpise 6.x --> Mouse useable - SLES 10 --> Mouse unusable - SLES 11 --> Mouse unusable - SLES 11 SP1 --> Mouse unusable - OpenSUSE 11.1 --> Mouse unusable - OpenSUSE 11.2 --> Mouse useable - OpenSUSE 11.3 --> Mouse useable - OpenSUSE 11.4 --> Mouse useable

On 01/30/2012 09:10 PM, André Felício wrote: >There are plans to enable other types of console for oVirt? Access by >VNC or RPD? > >There are many SO (windows) that access by SPICE is a little tricky. What's tricky with Spice? If there's anything we can do to help make Spice easier to use, let us know.

On 01/30/2012 10:25 PM, Adam Litke wrote: >On Mon, Jan 30, 2012 at 09:20:03PM +0200, Yaniv Kaul wrote: >>On 01/30/2012 09:10 PM, André Felício wrote: >>>There are plans to enable other types of console for oVirt? Access by >>>VNC or RPD? >>> >>>There are many SO (windows) that access by SPICE is a little tricky. >>What's tricky with Spice? If there's anything we can do to help make >>Spice easier to use, let us know. >I had a couple of issues when using spice that I can contribute to the >discussion: > >* The Firefox plugin is not widely available for non-RH Linux distros. >* I did not find any documentation for creating an optimal Linux guest with > spice. (Windows documentation seems a bit more complete).

>* The QXL device was showing up as a Standard VGA Controller in my Windows XP > guest.

>* Without optimizations, spice video and cursor responsiveness seemed much > slower than vnc over a compressed SSH tunnel. > I warmly suggest involving the Spice team with the above issues, I'm sure they'll be happy to help. Some look like bugs, some configuration, some will indeed require some development work. I know specifically the Spice XPI is getting some attention - it had a new version released yesterday. Y. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users