I am trying to passthrough R9 Nano to a VM, and facing some problems. After Windows 7 has been installed, the latest AMD Crimson edition driver is installed. At first time, the driver works properly. There appears to have the problem when I power off the vm and restart it. The driver was not working until I reboot the host. Here is my system. Manufacturer: Supermicro Product Name: X10DAi CPU: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz memory: 8GB linux kernel: 3.19.0 $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.19.0 root=UUID=fc28306a-e168-406a-805d-cadf70de53ec ro quiet splash intel-iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 vt.handoff=7 I tried to use qemu version 2.3.1, 2.4.1, and 2.5.1. I also added the device id number into the function vfio_setup_resetfn(), but the problem remains. I start my virtual machine with the following code. qemu-system-x86_64 -enable-kvm \ -M pc -m 4096 -cpu host \ -smp 4,sockets=1,cores=4,threads=1 \ -rtc base=localtime \ -vnc :0 \ -vga none \ -device lsi,id=scsi0,bus=pci.0 \ -device vfio-pci,host=03:00.0,x-vga=on \ -device vfio-pci,host=03:00.1 \ -hda $1 \ -monitor stdio
Hi, I'am experiencing the same problem with my 'R9 Fury' (also Fiji), but I'm unable to install AMD Crimson drivers for a few weeks now. Last working version was 16.3.1 (I think). Now, when the installer is trying to update/install the display driver, my screen goes blank, and the HOST (as well as the VM) hangs. Only a power off can help. Until 16.3.1 the screen went blank also (and the GPU fans started to spin at max speed), but the VM/HOST did NOT hang. If more info is required, I am glad to provide them :) See you, Michael
I've got a VM which uses an R9 Nano via passthrough. Like Michael said, my system hangs both the VM and the host machine when installing AMD drier updates. Likewise my VM freezes and the fan revs up to maximum upon a normal resart of the VM, or I change anything in the QEMU startup command (e.g. adding another hard drive to the VM). And the only way to stop either of those issues is to power off the host machine. The only way I have been able to change the driver for my card is during a fresh install of Windows when no drivers are previously installed (aside from the basic prepackaged ones are within Windows). Then I can get the lastest drivers I already downloaded from another hard drive and install them on my system, and it will work for the most part. However this doesn't address the core issue. Whilst I'm unsure if this website is the appropriate place to file this bug report, the previous two posts are the only place I've seen this exact issue mentioned.
Please try the latest 4.9 kernel or my 4.10-wip branch: https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.10-wip
It seems, it's not a vfio issue. There are (possibly) some firmware/hw problems, as it happens also on bare metal Windows (at least on my machine): https://community.amd.com/thread/204651
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/66.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.