Re: [Users] [Spice-devel] Fedora 18 and usb pass-through
Hi, On 06/03/2013 05:13 PM, Ryan Wilkinson wrote: Any more info. on this issue? No not really, you're the only one seeing this, some random idea: -Is udevd running properly on the box with the problem ? -Have you tried putting selinux in permissive mode? -Have you perhaps build some things (ie libusb) from source ? Regards, Hans ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] Fedora 18 and usb pass-through
Hi, On 05/30/2013 08:22 AM, Itamar Heim wrote: On 05/29/2013 02:03 AM, Ryan Wilkinson wrote: I've noticed with Fedora 17 that usb devices plugged in after a spice session is initiated automagically pass-through to the virtual desktop without manually selecting them but not so with Fedora 18. They pass through if you manually select them from the drop down bar. Any way to make 18 work like 17?? Fedora-18 and Fedora-17 remote-viewer should work the same. Notice that usb devices are only automagically passed-through if remote-viewer has the keyboard focus when the device gets plugged in! Also HID devices are excluded from automatic redirection. Regards, Hans ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] Fedora 18 and usb pass-through
Hi, On 05/30/2013 04:17 PM, Ryan Wilkinson wrote: Hans, Thanks for the info. Remote viewer has keyboard focus when attempting usb pass-through. Just tried again to confirm. These are the two package versions I'm seeing that are installed: virt-viewer.x86_64 0.5.4-3.fc18 virt-viewer.i686 0.5.3-1.fc17 And you can pass the device through manually from the menu? Can you do lsusb -v with the device plugin and then copy and paste the output for the device in question into your next mail ? Regards, Hans ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] Fedora 18 and usb pass-through
Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 2 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood1 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0100 power Port 2: .0100 power Device Status: 0x0001 Self Powered Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice3.06 iManufacturer 3 Linux 3.6.10-4.fc18.x86_64 uhci_hcd iProduct2 UHCI Host Controller iSerial 1 :00:1d.3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 2 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood1 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0100 power Port 2: .0303 lowspeed power enable connect Device Status: 0x0001 Self Powered On Thu, May 30, 2013 at 8:27 AM, Hans de Goede hdego...@redhat.com mailto:hdego...@redhat.com wrote: Hi, On 05/30/2013 04:17 PM, Ryan Wilkinson wrote: Hans, Thanks for the info. Remote viewer has keyboard focus when attempting usb pass-through. Just tried again to confirm. These are the two package versions I'm seeing that are installed: virt-viewer.x86_64 0.5.4-3.fc18 virt-viewer.i686 0.5.3-1.fc17 And you can pass the device through manually from the menu? Can you do lsusb -v with the device plugin and then copy and paste the output for the device in question into your next mail ? Regards, Hans ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] USB support
Hi, On 05/09/2012 04:11 PM, Nerijus Baliunas wrote: Hello, What is the best option for USB support in ovirt Windows guests now? I see there are quite a lot of recent patches in this area. That depends mostly on which OS you're running on the client, if you're running Linux clients I would use the new opensource USB redirection support in Spice. This is not yet supported in ovirt, but if you use Fedora-16/17 or RHEL-6.3 beta on the hosts, then you can just inject the necessary xml bits into the libvirt xml file vdsm generates using a vdsm hook, the necessary bits are given here: http://hansdegoede.livejournal.com/11084.html This requires using Spice as display protocol and remote-viewer as the client, and is currently only supported with Linux clients, we're working on also adding support for USB-redirection to the windows builds of spice-gtk remote-viewer. You may want to first play a bit with this using Fedora-16 host + client to see how all the bits fit together, a quick start for Fedora-16 is here: http://hansdegoede.livejournal.com/11084.html Regards, Hans ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] oVirt console plans
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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] oVirt console plans
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=FF28----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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] oVirt console plans
Hi, On 02/01/2012 06: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) 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 Ok, so you're testing the console under Windows clients? Otherwise this is not all that relevant, and it would be good to know which Linux version you are using for the tests. When testing outside of ovirt I have used both spiec and spicey to connect to the guest console: Ok, some more questions: * Are you using the windows or linux version of spicec /spicy for your testing? * Which versions? (output rpm -q spice-gtk spice-client would help) * Can you try building installing the latest spice (0.10.1) and/or spice-gtk (0.9) on a Linux client machine and try the spicec / spicy from that and see if that makes a difference? I just tried a RHEL-5 vm on a RHEL-6.2 host without the agent and the mouse works fine. Regards, Hans ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Spice-devel] oVirt console plans
Hi, On 02/02/2012 09:58 PM, Brown, Chris (GE Healthcare) wrote: Hans, Here are the results of testing I did with and without usbtablet. No usbtablet assumes spice defaults EG: PS2 mouse BTW for now I am using a VDSM hook script to enable usbtablet and workaround the issues. (TY Andy C.) Thanks for this list, it is good to hear that the VDSM hook script helps as a workaround for you. But I would like to fix this so that things work without such a workaround. My first guess is that the relative mouse mode not working is a client issue, hence I was wondering if you could give some more info about the client machines you're using. And if you're willing to run some tests with a different client version. If you want I can do some scratchbuilds for you of the latest client versions so that you will have RPM's to install (for the Linux clients only). I have the following questions about the client(s) which you're using: * Are you using the windows or linux version of spicec /spicy for your testing? * Which versions? (output rpm -q spice-gtk spice-client would help) * Can you try building installing the latest spice (0.10.1) and/or spice-gtk (0.9) on a Linux client machine and try the spicec / spicy from that and see if that makes a difference? I just tried a RHEL-5 vm on a RHEL-6.2 host without the agent and the mouse works fine. Note I've already tried to reproduce your issue with a RHEL-6 qemu host and spicec-0.10.1 and spicy-0.9 Linux clients and the relative mouse mode was working fine with either client. Thanks Regards, Hans Spice defaults: - 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 Spice + usbtablet results: - Red Hat 7.3 -- Mouse useable - Red Hat 9 -- Mouse useable - Fedora core 1 - 14 -- Mouse useable - Fedora core 15 Mouse useable - Fedora core 16 Mouse useable - Red Hat Enterprise 3.x -- Mouse useable - Red Hat Enterprise 4.x -- Mouse useable - Red Hat Enterprise 5.x -- Mouse useable - Red Hat Enterpise 6.x -- Mouse useable - SLES 10 -- Mouse useable - SLES 11 -- Mouse useable - SLES 11 SP1 -- Mouse useable - OpenSUSE 11.1 -- Mouse useable - OpenSUSE 11.2 -- Mouse useable - OpenSUSE 11.3 -- Mouse useable - OpenSUSE 11.4 -- Mouse useable - Windows 2000 SP4 -- Mouse useable - Windows XP -- Mouse useable - Windows Vista -- Mouse useable - Windows Server 2003 -- Mouse useable - Windows Server 2003 R2 -- Mouse useable - Windows Server 2008 -- Mouse useable - Windows Server 2008 R2 -- Mouse useable - Solaris 10 Update9 -- Mouse unusable (still does not work w/solaris) - Solaris 11 Express -- Mouse unusable (still does not work w/solaris) - Solaris 11 -- Mouse unusable (still does not work w/solaris) regards, Chris -Original Message- From: Hans de Goede [mailto:hdego...@redhat.com] Sent: Thursday, February 02, 2012 2:04 PM To: Brown, Chris (GE Healthcare) Cc: Itamar Heim; André Felício; spice-de...@lists.freedesktop.org; users@ovirt.org Subject: Re: [Spice-devel] [Users] oVirt console plans Hi, On 02/01/2012 06: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) 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
