Intel's stuff is really iffy about ACS unless you buy one of the
overpriced two thousand dollar processors, they use it for artificial
market segmentation so that they can say the desktop processors and the
E3 etc doesn't "support" sr-iov etc.
If you want to do this without spending lots of mo
On Fri, 31 Mar 2017 13:36:36 -0700
Joshua Hoblitt wrote:
> On 03/31/2017 01:22 PM, Alex Williamson wrote:
> >> which does claim ACS support in the overview sheet. Does anyone know if
> >> ACS is indeed working with the "pex 8747" and/or the sm x1?sat series of
> >> motherboards? Alternatively, d
On 03/31/2017 01:22 PM, Alex Williamson wrote:
>> which does claim ACS support in the overview sheet. Does anyone know if
>> ACS is indeed working with the "pex 8747" and/or the sm x1?sat series of
>> motherboards? Alternatively, does anyone know of an E3-1200 motherboard
>> that does have working
On Fri, 31 Mar 2017 12:43:56 -0700
Joshua Hoblitt wrote:
> Hi Folks,
>
> Long time listener (~2days), first time...
>
> Based on years of pain-free experience with VF NICs, I naively thought
> that installing a second GPU in a desktop for VM pass through would be a
> straight forward task. Thi
try set
2017-03-31 21:24 GMT+02:00 Patrick O'Callaghan :
> On Sun, 2017-03-26 at 08:18 -0600, Alex Williamson wrote:
>> On Sat, Mar 25, 2017 at 1:12 PM, Tom Smithhisler
>> wrote:
>>
>> > Hello,
>> >
>> > I’m trying to work through yet another Code 43 error. I’ve followed Alex
>>
Hi Folks,
Long time listener (~2days), first time...
Based on years of pain-free experience with VF NICs, I naively thought
that installing a second GPU in a desktop for VM pass through would be a
straight forward task. This has turned out to be an incorrect
assumption. I have two desktop syste
On Sun, 2017-03-26 at 08:18 -0600, Alex Williamson wrote:
> On Sat, Mar 25, 2017 at 1:12 PM, Tom Smithhisler
> wrote:
>
> > Hello,
> >
> > I’m trying to work through yet another Code 43 error. I’ve followed Alex
> > Williamson’s VFIO blog to try to pass through my GPU to a guest. My GPU is
> > a
I checked dmesg on the host and when I boot up the VM I’m getting the following:
[ +1.471291] vfio-pci :01:00.0: Invalid PCI ROM header signature:
expecting 0xaa55, got 0x
[ +0.31] vfio-pci :01:00.0: Invalid PCI ROM header signature:
expecting 0xaa55, got 0x
I’m guessing p
On Fri, 31 Mar 2017 16:59:50 +0200
Manuel Ullmann wrote:
> > Run rom-fixer on your dumped ROM and it will prompt for updating the
> > PCI vendor ID, device ID, and checksum. Use lspci -n to determine the
> > correct device ID for your IGD. Thanks,
> >
> > Alex
> Thanks a lot, that got it back
> Run rom-fixer on your dumped ROM and it will prompt for updating the
> PCI vendor ID, device ID, and checksum. Use lspci -n to determine the
> correct device ID for your IGD. Thanks,
>
> Alex
Thanks a lot, that got it back to booting. Would the rom fixer also be
appropriate for fixing ROMs of a
Hi Alex,
Thanks very much, I'll lean on IT a bit to try and test this with a newer
kernel, but it looks like it's definitely been addressed in later kernels. What
I really need is to get a new system with wider IOVA support.
Obviously your X79 board supports 48-bits, looking through Intel's dat
11 matches
Mail list logo
