Hi Patrick,    Your qemu log indicate that you're using qxl display card and 
spice together with  VGA pass-through. And you can see the VM output directly 
from on one of the HDMI output. Are u sure one of your VGA card is pass-through 
to the VM and is working? I'm asking because I heard they won't work together.
    Well suppose that do works. Please check if the keyboard is still 
functional when the mouse die in the VM. Use e.g. the "windows" key or alt+tab 
for testing. If keyboard is fine, try to find a process named "vdagent.exe", 
kill it (it'll re-spawn) and see if mouse comeback.
Regards,Daimon 

    On Wednesday, April 19, 2017 8:16 PM, Patrick O'Callaghan <p...@usb.ve> 
wrote:
 

 On Sat, 2017-04-15 at 06:27 -0700, Jamie Lawrence wrote:
> > On Apr 15, 2017, at 2:52 AM, Patrick O'Callaghan <p...@usb.ve> wrote:
> > 
> > It never happens when using the host, only in the VM. Note that I don't
> > have a KVM switch. It's an HDMI switch that connects the monitor to the
> > two GPUs. The problem corrects itself if I reboot the guest, not the
> > host.
> 
> Ditto - the host is fine; once I return mouse control to the host, it behaves 
> normally.
> 
> In my case a KVM/switch doesn't come in to play; I am using a Displayport 
> KVM, but the mouse devices are not connected to it - they're attached to the 
> host via an external hub. (I'm only using the KVM to switch video cards to 
> one monitor.)
> 
> I will try to make it happen again and look for log messages later today.

It happened again. This is my QEMU log:

2017-04-18 11:33:00.313+0000: starting up libvirt version: 2.2.0, package: 
2.fc25 (Fedora Project, 2016-11-14-21:04:29, 
buildvm-25.phx2.fedoraproject.org), qemu version: 2.7.1(qemu-2.7.1-5.fc25), 
hostname: Bree
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin 
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name guest=NewWin10,debug-threads=on -S 
-object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-NewWin10/master-key.aes
 -machine pc-i440fx-2.7,accel=kvm,usb=off,vmport=off -cpu 
host,hv_time,hv_vendor_id=SomeString,kvm=off -drive 
file=/usr/share/edk2/ovmf/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on 
-drive 
file=/var/lib/libvirt/qemu/nvram/NewWin10_VARS.fd,if=pflash,format=raw,unit=1 
-m 8192 -mem-prealloc -mem-path /dev/hugepages/libvirt/qemu -realtime mlock=off 
-smp 4,sockets=1,cores=2,threads=2 -uuid 98bd845f-366b-4988-a6c1-c17b69fea84b 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-NewWin10/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc 
base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet 
-no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot 
strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x9.0x7 -device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x9 
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x9.0x1 
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x9.0x2 
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive 
if=none,id=drive-ide0-0-1,readonly=on -device 
ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive 
file=/home/poc/Win10/Windows10.raw,format=raw,if=none,id=drive-virtio-disk0,cache=writeback,aio=threads
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1d:55:89,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -spice 
port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
 -device 
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev 
spicevmc,id=charredir0,name=usbredir -device 
usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev 
spicevmc,id=charredir1,name=usbredir -device 
usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device 
vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device 
vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0xa -device 
usb-host,hostbus=1,hostaddr=5,id=hostdev2,bus=usb.0,port=1 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/6 (label charserial0)
main_channel_link: add main channel client
red_qxl_set_cursor_peer: 
inputs_connect: inputs channel client create
2017-04-18T16:14:08.649575Z qemu-system-x86_64: libusb_release_interface: -4 
[NO_DEVICE]

Only the last line looks relevant.

There is nothing in dmesg.

poc

_______________________________________________
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users


   
_______________________________________________
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users

Reply via email to