December 30, 20178 yr Hi, I setup a Windows 10 Pro VM on my unRAID v6.3.5. I access the VM using VNC Viewer 6.17.1113 from OSX 10.9. Nothing is passthrough (no PCIe or USB controller). I just remote to it using the keyboard and mouse on my MAC. I was able to do the installation fine and use it for a bit. But at one point, the mouse stopped working. I was still able to use the keyboard fine though so the VM has not froze. I restarted the VM and the mouse is back working fine for some time then it stops working again. I searched through the forum and found similar issues when a USB controller is passed through or using a mouse plugged into the unRAID system (which is neither the case here). Any idea what could cause this? Not sure what log file would help here but I'll be happy to provide anything that can help. Below is the XML of the VM. Thanks <domain type='kvm'> <name>001 Windows 10</name> <uuid>eb19a00d-4700-b96f-9c63-b7cf661e37ea</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/eb19a00d-4700-b96f-9c63-b7cf661e37ea_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/001 Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/Win10_1709_English_x64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.126-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:87:53:df'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Edited December 30, 20178 yr by Parigot
December 30, 20178 yr 12 minutes ago, Parigot said: I access the VM using VNC Viewer 6.17.1113 from OSX 10.9. Try using a different VNC client, or perhaps enable RDP in windows and use RDP to access it.
December 30, 20178 yr Author 3 hours ago, jonathanm said: Try using a different VNC client, or perhaps enable RDP in windows and use RDP to access it. Trying with Microsoft RDP 8.0.43 for OSX and so far it works fine. Will keep it as is for a few days see if I encounter any issue otherwise that post will be resolved. Thanks!
October 25, 20187 yr On 12/29/2017 at 4:35 PM, Parigot said: Hi, I setup a Windows 10 Pro VM on my unRAID v6.3.5. I access the VM using VNC Viewer 6.17.1113 from OSX 10.9. Nothing is passthrough (no PCIe or USB controller). I just remote to it using the keyboard and mouse on my MAC. I was able to do the installation fine and use it for a bit. But at one point, the mouse stopped working. I was still able to use the keyboard fine though so the VM has not froze. I restarted the VM and the mouse is back working fine for some time then it stops working again. Been experiencing the same thing here. I lose the ability to click whenever I switch from the VNC viewer to say Firefox (so I can watch some SpaceInvader One ) and back to the VNC viewer. Keyboard input is still functioning. This is happening with: VNC Viewer 6.18.907 Tiger VNC 1.9.0 Unraid's browser based VNC viewer VM logs from Unraid show a long string of: qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 **Update** I am losing the mouse after applying some changes inside the Windows VM. This last time, I lost the mouse after enabling networking in Windows 10 so that I can access the user shares on the array. 2018-10-25 07:40:33.079+0000: Domain id=9 is tainted: high-privileges 2018-10-25 07:40:33.079+0000: Domain id=9 is tainted: host-cpu 2018-10-25T07:40:33.123658Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) Web search turns up: Bug 1611984 qemu prompt "qxl_cursor: not implemented: type 1" when boot Win2008R2 guest reported: 2018-08-03 https://bugzilla.redhat.com/show_bug.cgi?id=1611984 And: https://patchwork.ozlabs.org/patch/965487/ Monochrome cursors are still used by Windows guests with the QXL-WDDM-DOD driver. Such cursor types have one odd feature, inversion of colors. GDK does not seem to support it, so implement an alternative solution: fill the inverted pixels and add an outline to make the cursor more visible. Tested with the text cursor in Notepad and Windows 10. cursor_set_mono is also used by the vmware GPU, so add a special check to avoid breaking its 32bpp format (tested with Kubuntu 14.04.4). I was unable to find a guest which supports the 1bpp format with a vmware GPU. The old implementation was buggy and removed in v2.10.0-108-g79c5a10cdd ("qxl: drop mono cursor support"), this version improves upon that by adding bounds validation, clarifying the semantics of the two masks and adds a workaround for inverted colors support. Looks like the bug was patched and the commit pushed through September 3–5, 2018. I guess now we wait for Lime Tech to push through the update? Not sure how it works on their end. Either way we the end users will have to wait. Fingers crossed. **Update** Using a RDP like Splashtop, the mouse works fine from the client and also from any USB mice that are pushed through to the VM. Edited October 25, 20187 yr by Zer0Nin3r RDP VS VNC = Mice working in R.D. clients
May 1, 20197 yr I also encountered this issue qxl_cursor: not implemented: type 1 The workaround that I am using is to switch to Cirrus as the VNC video driver. Hope this helps someone.
Archived
This topic is now archived and is closed to further replies.