[Bug 118121] New: KVM - unhandled rdmsr - VFIO+Radeon R9 380, Win10 Guest

[bugzilla-daemon@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=118121

            Bug ID: 118121
           Summary: KVM - unhandled rdmsr - VFIO+Radeon R9 380, Win10
                    Guest
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.5.x and below
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: mparnell@gmail.com
        Regression: No

This only happens when attempting to run Just Cause 3, one of the most buggy
games currently known to exist...

Host CPU : 4790K Devil's Canyon
VFIO GPU: Radeon R9 380

Guest OS: Win10 64

Other than the attached dmesg selection and the attached command I use to run
the VM, I have seen no real issues so far as usage goes, the machine feels as
good as bare metal.

I start the machine using:

qemu-system-x86_64 -enable-kvm -m 16384 -cpu
host,kvm=off,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time \
-serial none \
-parallel none \
-nodefaults \
-nodefconfig \
-name Windows \
-soundhw hda \
-rtc base=localtime \
-vga none \
-net nic,macaddr=52:54:00:00:00:01,model=virtio,name=net0 \
-device vfio-pci,host=0000:01:00.0 \
-usb -usbdevice host:1532:0037 \
-usb -usbdevice host:2516:001a \
-net user \
-device virtio-scsi-pci,id=scsi \
-drive
if=pflash,format=raw,readonly,file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
\
-drive if=pflash,format=raw,file=/tmp/my_vars.fd \
-drive
file=/home/ili/vm/windoze.img,id=disk,format=raw,if=none,cache=none,if=virtio \
-drive
file=/media/ili/vms/games.img,id=disk2,format=raw,if=none,cache=none,if=virtio 

(Off topic: The only drawback is the reset issue I think many of us suffer, as
I have to reboot the host machine if I power off the guest and want to start it
back up at a later time. The interesting thing there is that I don't run into
this with q35, but with my hardware configuration Windows doesn't play nice
using Q35, it seems. I could just be missing a configuration setting there
though.)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.