[vfio-users] Frequent crashing with Overwatch

Abdulla Bubshait darkstego at gmail.com
Fri Apr 14 21:02:58 UTC 2017


MSRs are already disabled, it used to work fine, and now it crashes if I am
in the game after a short while, sometimes it is right as I start the game,
other times I can play for 3-5 minutes before it just crashes.

On Fri, Apr 14, 2017 at 3:59 PM Nick Sarnie <commendsarnex at gmail.com> wrote:

> Have you guys tried disabling MSRs?
>
> On Fri, Apr 14, 2017 at 3:26 PM, Abdulla Bubshait <darkstego at gmail.com>
> wrote:
> > I would also like to chime in that this behaviour started popping up for
> me
> > too. I am guessing it was introduced in a recent Overwatch update. I
> used to
> > play the game fine on my setup until recently. Now, for some reason the
> game
> > crashes after a while and I am unsure what could be causing it.
> >
> > On Tue, Apr 11, 2017 at 4:57 AM Jesse Kennedy <jesse at jkennedy.pw> wrote:
> >>
> >> Hello,
> >>
> >> I've been experience very frequent crashing while playing Overwatch.
> >> Usually, I can go for a while without crashing. But once it starts
> crashing,
> >> it will continue to crash every few minutes until I restart the VM.
> >> Sometimes I have to restart the host to fix it. The "crashes" are 70%
> >> application crashing, 20% VM freezing, and 10% BSOD. The BSOD codes are
> >> inconsistent, but one such code was MEMORY_MANAGEMENT. I play many other
> >> games, but Overwatch is the only one that causes crashes.
> >>
> >> Nothing suspect in kernel logs or /var/log/libvirt/qemu/win10.log. Is
> >> there anything I can do to get better visibility on what's happening so
> I
> >> can troubleshoot? Could it be a hardware issue?
> >>
> >> qemu line from log:
> >> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> >> QEMU_AUDIO_DRV=none /usr/sbin/qemu-system-x86_64 -name
> >> guest=win10,debug-threa
> >> ds=on -S -object
> >>
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-win10/master-key.aes
> >> -machine pc-i440fx-2.6,accel=kvm,usb
> >> =off,vmport=off,dump-guest-core=off -cpu
> >>
> core2duo,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=whatever,kvm=off
> >> -drive file=/u
> >> sr/share/ovmf/x64/ovmf_x64.bin,if=pflash,format=raw,unit=0,readonly=on
> >> -drive file=/var/lib/libvirt/qemu/nvram/win10_VARS.fd,if=pflash,format=
> >> raw,unit=1 -m 6000 -realtime mlock=off -smp
> 6,sockets=1,cores=3,threads=2
> >> -uuid ca607e58-3a83-411c-b74c-65e4c2ca565d -display none -no-user-co
> >> nfig -nodefaults -chardev
> >>
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-win10/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.disa
> >> ble_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device
> >> nec-usb-xhci,id=usb,bus=pci.0,addr=0x6 -device lsi,id=scsi0,bus=pci.0,
> >> addr=0x9 -device ahci,id=sata0,bus=pci.0,addr=0xc -device
> >> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -device
> >> usb-hub,id=hub0,bus=u
> >> sb.0,port=1 -drive
> >>
> file=/dev/nvme0n1,format=raw,if=none,id=drive-sata0-0-0,serial=windows,cache=none,aio=native
> >> -device ide-hd,bus=sata0.0,dri
> >> ve=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive
> >>
> file=/dev/disk/by-id/ata-ST4000DX001-1CE168_Z3074HEX,format=raw,if=none,id=drive-virtio-dis
> >> k0,cache=none,aio=native -device
> >>
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0xb,drive=drive-virtio-disk0,id=virtio-disk0
> >> -netdev tap,fd=26,id=host
> >> net0,vhost=on,vhostfd=29 -device
> >>
> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5d:02:0a,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
> >> =2,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -chardev
> >>
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/win10.agent,server,nowa
> >> it -device
> >>
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> >> -device usb-tablet,id=input2,
> >> bus=usb.0,port=4 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
> >> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=ch
> >> arredir0,name=usbredir -device
> >> usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1.1 -chardev
> >> spicevmc,id=charredir1,name=usbredir -device
> >> usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=1.2 -device
> >> vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0xa -device
> vfio-pci,host=
> >> 01:00.1,id=hostdev1,bus=pci.0,addr=0x2 -device
> >> vfio-pci,host=00:14.0,id=hostdev2,bus=pci.0,addr=0xe -device
> >> vfio-pci,host=00:1f.3,id=hostdev3,
> >> bus=pci.0,addr=0xd -device
> >> vfio-pci,host=00:1f.0,id=hostdev4,bus=pci.0,addr=0xf -device
> >> vfio-pci,host=00:1f.2,id=hostdev5,bus=pci.0,addr=0x10
> >> -device vfio-pci,host=00:1f.4,id=hostdev6,bus=pci.0,addr=0x11 -device
> >> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -object rng-random,id=
> >> objrng0,filename=/dev/random -device
> >> virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x8 -device
> >> pvpanic,ioport=1285 -msg timestamp=on
> >>
> >> Specs:
> >> Arch/Windows 10
> >> 6700k, 3 cores/2 threads to guest, core2duo model
> >> 32GB, 6GB to guest
> >> 1080 GTX
> >>
> >> Kernel line:
> >> rw quiet splash rd.modules-load=vfio-pci modules-load=vfio-pci
> >> intel_iommu=on,igfx_off iommu=pt intremap=no_x2apic_optout
> >> transparent_hugepage=never isolcpus=2-7
> >>
> >> Thanks
> >> _______________________________________________
> >> vfio-users mailing list
> >> vfio-users at redhat.com
> >> https://www.redhat.com/mailman/listinfo/vfio-users
> >
> >
> > _______________________________________________
> > vfio-users mailing list
> > vfio-users at redhat.com
> > https://www.redhat.com/mailman/listinfo/vfio-users
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20170414/1aa01db2/attachment.htm>


More information about the vfio-users mailing list