Jump to content
Cross_5

VM Unknown PCI header type '127'

16 posts in this topic Last Reply

Recommended Posts

Posted (edited)

Hey if I setting up a Win10 VM and select my Radeon RX 580 became I two defferent error. 1) Unknown PCI header type '127' or same time 2) unable to execute QEMU command 'cont': Resetting the Virtual Machine is required.

 

PCI Slot1: NVIDIA NVS 300

PCI Slot2: Radeon RX580

 

Have anyone are idee?

 

Screenshot_20190706-082840_Chrome.thumb.jpg.8f21b753c69a318db22779d32dfd5bc4.jpgScreenshot_20190706-082913_Chrome.thumb.jpg.8ae1ab7b208d0672414f56aadfddb35b.jpg

Edited by Cross_5

Share this post


Link to post
Posted (edited)

I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start.

 

Please report this to gigabyte here: https://esupport.gigabyte.com

 

The more who complain the more likely they will test future BIOS on unRAID.

Edited by dodgypast

Share this post


Link to post
7 hours ago, dodgypast said:

I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start.

 

Just to confirm, I've had to do exactly this on two boards from two different manufacturers (Gigabyte and MSI).

 

Essentially, you need the bios that predates "- Support new upcoming AMD cpu." 

Share this post


Link to post

further research led me to this link:
https://forum.level1techs.com/t/attention-amd-vfio-users-do-not-update-your-bios/142685

 

It's an AMD issues with the BIOS code they're giving to OEMs.

 

It would be nice to know what the developers are doing to try and get AMD to do something about it... or even acknowledge / warn users that their product cannot perform one of it's heavily advertised features in a significant set of circumstances.

Share this post


Link to post
On 7/8/2019 at 8:24 AM, dodgypast said:

I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start.

 

Please report this to gigabyte here: https://esupport.gigabyte.com

 

The more who complain the more likely they will test future BIOS on unRAID.

I've try Bios version F40, F31, F30 and F6 now but not work and are new error: Did not find USB device 046d:c07c

all version under F40 the same error and if I add my Radeon RX 580 to the VM error: unknown pci source type 'vendor'.

 

Which version work at you??

Share this post


Link to post
3 hours ago, dodgypast said:

F25 for the ax370. I saw someone mention F5 working for a x470 gigabyte board.

Thank you, F5 work but I must set up a new vm. Old VM dont work.

Share this post


Link to post

I had / have exactly this problem.

 

I also have the Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING-CF - currently with F6 Bios Version.

 

Until F6 everything is working fine. Since F30 (also F31 and F40) there is exactly this "VM Unknown PCI header type '127'" error with my Nvidia Cards.

 

I hope there will be another update after F40 - and I hope these bugs will be resolved because it would be a shame if I couldn't upgrade to Ryzen3 because of buggy bios-updates.

 

 

biosversion.JPG

Share this post


Link to post

F41b for Gigabyte Boards (with AGESA 1.0.0.3AB) is out ... I'm not able to test this version until the next couple of days ... maybe someone else can test ...

Share this post


Link to post
Posted (edited)
20 hours ago, sturmstar said:

F41b for Gigabyte Boards (with AGESA 1.0.0.3AB) is out ... I'm not able to test this version until the next couple of days ... maybe someone else can test ...

I've tested it and it doesn't work for the ax370 board, I would imagine it's the same on the x470 as it's based on the same AGESA.

Edited by dodgypast

Share this post


Link to post

F42a for Gigabyte with AGESA 1.0.0.3ABB is out - rumors says that the issue with VFIO is finally fixed. Perhaps I'm able to test this tommorow

Share this post


Link to post

I just tested it. It still doesn't work with F42a. 😭

 

Same problems and errors

 

Going Back to f6 again

Share this post


Link to post
6 hours ago, sturmstar said:

I just tested it. It still doesn't work with F42a. 😭

 

Same problems and errors

 

Going Back to f6 again

Thank you for the Test. 👍

Share this post


Link to post

Curious to know if the issue affect x570 boards as well, or just x3/470

Share this post


Link to post
On 8/4/2019 at 3:43 AM, helin0x said:

Curious to know if the issue affect x570 boards as well, or just x3/470

with 1003ab bios  MSI x570 ACE has exactly the same problem(AER ERROR),but with kernel patch there is not pci 127 type error for x570.

There is an update 1003abb bios update that I havent test yet

Share this post


Link to post
On 8/22/2019 at 11:29 AM, Leoyzen said:

with 1003ab bios  MSI x570 ACE has exactly the same problem(AER ERROR),but with kernel patch there is not pci 127 type error for x570.

There is an update 1003abb bios update that I havent test yet

How do you do the kernel patch?

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.