thor2002ro

Members
  • Posts

    51
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

thor2002ro's Achievements

Rookie

Rookie (2/14)

14

Reputation

  1. Works great i have some suggestions...option to backup docker.img its useful of you have lots of custom dockers..... And i think flash backup could use compression..... The rest looks good. Good job 👌
  2. Seams everyone is ignoring the fact that your server will need to permanently phone home.... Guess next will be pushing ad's to the server web interface..... Not ok with this..... My server should be fully private....
  3. I will update it when I get some time but currently a little swamped at work the current kernel works great at the moment so not in any hurry I didn't observe any issues with the current build on my server
  4. As I remember the 5700xt reset issue is with non referance/founder edition cards doesn't matter what kernel version are you on.....
  5. Sorry to hear that.... My vega 56 has been great.... With the reset module apart from not being able to reboot a vm... I need to shut it down and start it up again if I need to reboot
  6. sounds weird.... don't know about plex... I use jellyfin and emby.... I have a GTX970(primary) and a Vega56 I use nvidia for transcoding and can start vm with it no issue... I don't need to shutdown any docker container.... or prepare it in any way.... and after the VM is stopped the driver resumes.... when VM is started the docker container trascodes with CPU.... when the GPU is available again it switches back to gpu on the next transcode When transcoding usually power state should be P2 .... and P0 when idle in power saving.... Also starting and stopping a VM with nvidia usually resets the nvidia persistence mode this is tested extensively since I use it every day nvidia for linux VM and vega for gaming vm I never once need to reset the nvidia card.... never seen P8 state.... when transcoding.... seams like its playing video ..... the "nvidia-smi -pm 1" command the nvidia install is using should enable persistence mode for all cards.... as mentioned until a VM uses it then it resets .... I will investigate the nvidia-persistence daemon maybe it will better keep the cards persistence mode enabled.... you could try to disable autostart at any docker that uses the card and see if stopping and starting vm with passthrough is fine .... depending on the platform you are using might be IOMMU issues.... don't forget to look at the system log and dmesg in command line
  7. I wouldn't .... if they changed the version of the md driver ....but on the other hand it wont explode....it wont start the array that's it...
  8. glad you fixed it.... I really need to make a plugin like install method.... to make stuff easier.... PS: after some testing it seams amdgpu driver doesn't need to be blacklisted if you use AMD GPU for VM passthrough to windows VM, works great.... but not so great with linux VM crashes the driver....
  9. dono what to say.... maybe it was a flash write error .... try to overwrite the files again and be sure to safely remove the flash stick and try again....
  10. no..... you dont need the original files ..... but the kernel you are loading seams to be 5.9.4 not 5.10rc4..... so the bzimage is not the right one for sure....
  11. you need to update the hole thing not just the packages.... the packages are tied to the kernel.... bzimage and bzmodules