***UPDATE 2***

See posts below for fix.  Essentially the most obvious symptom of my particular issue was the VM not booting and the system log getting completely filled with a message like:

vfio-pci 0000:65:00.0: BAR 1: can't reserve [mem 0x38bfe0000000-0x38bfefffffff 64bit pref]

 

 

***UPDATE***

I dumped the BIOS myself and that still didn't work.  But I did discover a work-around to my problem.  If I boot up the system with no display attached, my board will leave the GPU unbound.  I can then load up a VM without issue.  Having to unplug my HDMI cable every time I reboot is not ideal.  So any more suggestions will still be appreciated.

 

***END UPDATE***

So I've attempted to pass through my GPU via the vbios edit method (see link below). When I attempt to run the VM, I get no display output while one of the cpu cores gets pegged at 100%.  If I choose a different similar (presumably incorrect) vbios, the VM freezes with no CPU activity.   I'm using a Ryzen 3600X on a MSI X470 Gaming Plus Mobo (newest stable BIOS), with a GTX 1060 3GB (EVGA SC).  

 

SpaceInvader One's Video Guide

 

 

Does anyone have any ideas on what the problem is?  Help would be GREATLY appreciated. 

Edited May 27, 20215 yr by Marc_G2

Amd bios bug introduced with support for 3000 processors. You can try the kernel here to fix it. 

 

 

Thanks for the suggestion. I was able to virtualization working using VNC.  So I was thinking the virtualization bugs got fixed.  I will try out the kernel later today.

Well I tried out those alternate kernal files, and still no luck.  I'm still getting the same behavior.  I will try adding a second GPU to see if I can get that working.

I dumped the BIOS myself and that still didn't work.  But I did discover a work-around to my problem.  If I boot up the system with no display attached, my board will leave the GPU unbound.  I can then load up a VM without issue.  Having to unplug my HDMI cable every time I reboot is not ideal.  So any more suggestions will still be appreciated.

On 9/21/2019 at 5:27 PM, Marc_G2 said:

So I've attempted to pass through my GPU via the vbios edit method (see link below). When I attempt to run the VM, I get no display output while one of the cpu cores gets pegged at 100%.

What does the syslog look like when this is happening? Post diagnostics.  See my GPU efforts here:

 

20 hours ago, dgaschk said:

What does the syslog look like when this is happening? Post diagnostics.  See my GPU efforts here:

 

 

 

The issue I'm having is exactly as you described above.   Should these lines be applicable to all hardware configurations?

 

#fix video for VM
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind

 

 

 

Yes. Those lines unbind the console. Enter them on the command line to see if they work. Make sure everything is working.  When you reboot the effects will be undone. Add the lines to flash/config/go so they are executed on every reboot. See my sig for go file info. 

That fixed it!   I'm surprised this issue wasn't reported on until recently.  What do think is the cause?

 

 

First of all a big thanks to @dgaschk for posting this solution! After upgrading my CPU and mainboard I ran into this issue. Your solution fixed the problem without any further issues. Thanks a lot!

I am, however, curious about the origin of this problem. Could you explain to me what these commands actually do? Which "console" us unbound? Why does this problem exist in the first place? 

 

Best,

Michael