Re: [vfio-users] Igd passthrough not working on w10, works with ubuntu

2019-03-11 Thread Alex Williamson
[re-adding vfio-users] On Mon, 11 Mar 2019 18:23:14 +0100 Cor Saelmans wrote: > Thank you Alex for your reply. > > I tested earlier today with a fresh install of my ubuntu host in legacy > mode and this worked directly without any further customization. > > Just reinstalled my host back to EFI

Re: [vfio-users] "Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff" when attempting to dump PCI ROM

2019-03-11 Thread Alex Williamson
On Mon, 11 Mar 2019 01:46:03 -0400 Nicolas Roy-Renaud wrote: > Hey, Alex, thanks for replying. > > It seems like you're right on the Mem- part. > > [user@OCCAM ~]$ lspci -s 07:00.0 -vvv > 07:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] > (rev a1) (prog-if 00 [VGA

Re: [vfio-users] "Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff" when attempting to dump PCI ROM

2019-03-11 Thread Nicolas Roy-Renaud
Just retried this morning after waking my computer up from sleep (and having previously loaded a VM from earlier) and this time, the ROM dump did succeed. Diffing the contents of lspci from then and now , the device does appear to have changed power state

Re: [vfio-users] "Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff" when attempting to dump PCI ROM

2019-03-11 Thread Auger Eric
Hi Nicolas, Alex, On 3/11/19 9:39 AM, Auger Eric wrote: > Hi Nicolas, > > On 3/10/19 11:06 PM, Nicolas Roy-Renaud wrote: >> I've seen a lot of people before reccomand VFIO newcomers to flash their >> GPU if they couldn't get their passthrough working right before, and >> since I know how potentia

Re: [vfio-users] "Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff" when attempting to dump PCI ROM

2019-03-11 Thread Auger Eric
Hi Nicolas, On 3/10/19 11:06 PM, Nicolas Roy-Renaud wrote: > I've seen a lot of people before reccomand VFIO newcomers to flash their > GPU if they couldn't get their passthrough working right before, and > since I know how potentially risky and avoidable this sort of procedure > is (since QEMU le