Correct
1 Like
Hey, first of all thanks for the work!
now my very noob stupid question:
how do i ensure the kernel options as shown in the README?
CONFIG_FTRACE=y
CONFIG_KPROBES=y
CONFIG_PCI_QUIRKS=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_FUNCTION_TRACER=y
1 Like
Most kernels already have all these options enabled. You can confirm by checking /boot/config-$(uname -r) which is the config file for your current running kernel.
1 Like
thanks for the quick reply but i cant check this command:
drwxr-xr-x 6 root root 4096 7. Nov 11:23 .
drwxr-xr-x 20 root root 4096 7. Nov 11:21 ..
-rw-r--r-- 1 root root 40960 23. Okt 14:26 amd-ucode.img
drwx------ 3 root root 4096 1. Jan 1970 efi
drwxr-xr-x 6 root root 4096 7. Nov 11:24 grub
-rw-r--r-- 1 root root 31251925 7. Nov 11:23 initramfs-5.4-x86_64-fallback.img
-rw-r--r-- 1 root root 10070972 7. Nov 11:23 initramfs-5.4-x86_64.img
-rw-r--r-- 1 root root 31218777 7. Nov 11:23 initramfs-5.7-x86_64-fallback.img
-rw-r--r-- 1 root root 9714873 7. Nov 11:23 initramfs-5.7-x86_64.img
-rw-r--r-- 1 root root 31343463 7. Nov 11:24 initramfs-5.8-x86_64-fallback.img
-rw-r--r-- 1 root root 9727906 7. Nov 11:23 initramfs-5.8-x86_64.img
-rw-r--r-- 1 root root 31423641 7. Nov 11:24 initramfs-5.9-x86_64-fallback.img
-rw-r--r-- 1 root root 9730085 7. Nov 11:24 initramfs-5.9-x86_64.img
-rw-r--r-- 1 root root 21 1. Nov 14:42 linux54-x86_64.kver
-rw-r--r-- 1 root root 21 28. Aug 22:21 linux57-x86_64.kver
-rw-r--r-- 1 root root 21 1. Nov 15:09 linux58-x86_64.kver
-rw-r--r-- 1 root root 20 1. Nov 15:24 linux59-x86_64.kver
drwxr-xr-x 2 root root 4096 1. Jun 12:34 memtest86+
drwxr-xr-x 2 root root 4096 29. Okt 14:35 syslinux
-rw-r--r-- 1 root root 6498624 7. Nov 11:22 vmlinuz-5.4-x86_64
-rw-r--r-- 1 root root 6681472 7. Okt 08:17 vmlinuz-5.7-x86_64
-rw-r--r-- 1 root root 6804736 7. Nov 11:22 vmlinuz-5.8-x86_64
-rw-r--r-- 1 root root 8128640 7. Nov 11:22 vmlinuz-5.9-x86_64
i use Manjaro 
no idea then I am sorry, you will need to check your distros documentation.
You can just check the āconfigā file in their repository: https://gitlab.manjaro.org/packages/core
For the 5.9 kernel it is here: https://gitlab.manjaro.org/packages/core/linux59/-/blob/master/config
1 Like
you are my hero! thanks! 
hi,
great work
Just tried this on linux mint 20, 5.4.0-54-lowlatency, sapphire rx 570, works with linux, windows 10, except macos X Mojave, Catalina, Big Sur
thank you very much!
Wow! Iām blown away, i just gave it a try and itās pretty damn good, it is definitely more stable than the kernel patch. Sometimes, i was getting some system freezes after a VM restart or shutdown, i tried to reboot/shutdown my VMs a couple of times and no issue so far with the vendor-reset module, so sweet <3
You guys are amazing 
Is there a way to support your work throuigh Paypal, Koffi or anything else?
Keep it up the great job guys <3
Thanks @blackmennewstyle, at this juncture in time @belfrypossum has invested far more time then I have on this project (and hardware) and as such I have asked him for donation details if he has such a means to do so. I will update the OP when a details and a decision has been made.
2 Likes
Do you mind giving me a quick rundown on how to build this particular guest? I have a Navi10 card and an AMD host I can test with so Iād like to see if I can reproduce it.
Hey there @gnif 
Considered to reply to you in this thread instead of Discord in hope others might benefit from my results as well eventually.
I switched to Linux 5.9.8-2-default which is the latest kernel as it seems in Tumbleweed right now and compiling as well as running your vendor-reset module works great now! 
I can shutdown the VM, let the module do its thing and boot back into it as I desire.
However, now that I have done that (without reboot of my host anyway) Windows inside the VM canāt detect the Adrenalin drivers for my 5700 Pulse and keeps things at a fancy small (for todayās standards) 800x600 resolution 
I donāt know yet whether this is because of something that went wrong, potentially inside Windows itself but otherwise this is huge progress for me 
1 Like
Most distros keeps current config in /proc/config.gz, so you can do
zcat /proc/config.gz
Works in my Manjaro.
1 Like
hereās the XML:
pretty standard gaming VM setup. just a Bullseye guest instead of Windows.
i havent yet ran tests with a windows guest.
1 Like
After a couple of reboots to see what happens, I have to tell that running sudo modprobe vendor-reset wonāt cut it for me anymore 
After the first time having a 800x600 resolution, I rebooted and tried again.
The VM booted but would instantly shutdown again because it had some issue.
Now, the module can no longer reset my graphics card, to put it that way.
Itās as before I compiled the module :<
Still awesome stuff and if I knew how to help out better, I would.
For those that wish to donate to this project please use @belfrypossumās KoFi account over here:
5 Likes
Anyone here with a Radeon VII got this working? I get no graphics on the guest after shutting down/starting it.
dmesg snippets:
I donāt seem to be able to replicate this in my testing. It works in all cases for me. However, I didnāt try autostart from boot, so perhaps thatās the difference. My other thought would be the seeming variation in the different Navi 10 boards, my 5600 XT may behave slightly differently from your 5700.
1 Like
I can actually second these results from Mathew.
Havenāt yet use destroy on my VM but after the first time being successful, shutdown and restart and reboots all fail.
1 Like
Do you mind sharing the output of dmesg the next time this happens?
1 Like