<div dir="ltr"><div style="font-size:12.8px"><div><div><div><div>After some time I found that it's not a hard freeze... I misinterpreted it for a long time, because keyboard didn't react on caps or num key and image was frozen. Actually I found that system is working and I can execute commands, so I got output of dmesg and lspci after the binding and it seems that binding succeed.<br><br></div>lspci:<br><br>01:00.0 0300: 1002:6938 (rev f1) (prog-if 00 [VGA controller])<br> Subsystem: 1458:22c8<br> Kernel driver in use: vfio-pci<br> Kernel modules: amdgpu<br><br>01:00.1 0403: 1002:aad8<br> Subsystem: 1458:aad8<br> Kernel driver in use: vfio-pci<br> Kernel modules: snd_hda_intel<br><br>02:00.0 0300: 10de:104a (rev a1) (prog-if 00 [VGA controller])<br> Subsystem: 1458:362a<br> Kernel driver in use: nvidia<br> Kernel modules: nouveau, nvidia_drm, nvidia<br><br></div>dmesg:<br><br>[ 338.322244] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem<br><br></div><div>And if I try to launch vm I also get in systemctl:<br><br>kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem<br>kernel: vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x270<br>kernel: vfio_ecap_init: 0000:01:00.0 hiding ecap 0x1b@0x2d0<br>kernel: pmd_set_huge: Cannot satisfy [mem 0xb0000000-0xb0200000] with a huge-page mapping due to MTRR override.<br></div><br></div>amd drivers are blacklisted, so there is no drivers associated with gpu before binding to the vfio as I see from lspci.<br><br></div><span style="font-size:12.8px">And I've got one more thought - while nvidia gpu has nvidia driver loaded, desktop enviroment isn't rendered via it, but via "Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)" as stated in "details" of gnome. So after binding amd gpu to the vfio-pci something starting to going wrong with video output.</span><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">So I've deleted nvidia driver (tried to use nouveau but failed to do this atm.) and binded amd gpu to the pci_stub, after that I was able to boot vm, but it seems it shares output with desktop (I don't even know what's going on there), because on other monitor input there is no image and I was able to switch from vm to linux desktop once. After all I think there is no issue with vfio here, but strange behaviour of nvidia drivers and my wrong configuration (I still don't know how to make even nouveau drivers work...).</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">I think this issue can be closed.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">And thank you for your answer!</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">werman</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-25 20:41 GMT+03:00 Zir Blazer <span dir="ltr"><<a href="mailto:zir_blazer@hotmail.com" target="_blank">zir_blazer@hotmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><div dir="ltr">If it hard freezes when executing the vfio bind script for the Radeon, its probable than the crash happens either when it gets unbinded from the radeon Driver, or attached to vfio-pci in a dirty state. I don't see it blacklisted anywhere, so try doing so so it doesn't get initialized and try again. If you're using only the GeForce for the host, you aren't missing anything by doing so.<div><br></div><div>Add this to the Kernel Parameters:</div><div><br></div><div>modprobe.blacklist=radeon</div><div><br></div><div>If that works, I'm curious why the behavior change with the new Kernel...</div> </div></div> <br>_______________________________________________<br> vfio-users mailing list<br> <a href="mailto:vfio-users@redhat.com">vfio-users@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br> <br></blockquote></div><br></div>