Thank you all for your input.
After much testing back and forth, eight Windows installs etc. This is what I've found:
Deleting <vmport state='off' /> via "sudo virsh edit my_machine" fixes random reboots which start appearing as soon as I pass my R9 290 GPU through.
It also makes Win 10 list my passed through GPU as "AMD Radeon R9 200 series" instead of "Microsoft Basic Display Adapter", which in turn makes higher resolutions available.
I am able to install AMD's driver version 14.12 (amd-catalyst-omega-14.12-with-dotnet45-win7-64bit.exe), but the newer Crimson drivers cause reboots.
Also a lot of my initial headaches might have come from the lack of host reboots. Power the Win10 guest on/off a sufficient number of times, suspend the host etc. and things stop working before the host reboots. Is this something to with power management of the vfio-pci claimed gpu?
Dos deleting <vmport state='off' /> make sense? It should result in <vmport state='on' /> which is the default. This vmport is some VMware IO port as far as I understand. Why do I need this turned on (i.e. remove the directive which turns it off)?
Thank you for all your inputs
P.S. Had a game of Rocket League (without sound, not yet confired) with mouse and keyboard provided by Synergy. Worked like a dream.
On 04/19/2016 08:22 AM, Quentin Deldycke wrote: