ctab579

@gvkhna Thank you for that lengthy writeup! That will probably help many people extensively. However, I have a question about your config. Am I understanding that you recreate your cluster (and more importantly your database; e.g.: etcd) every time UnRaid boots? That is what I would like to avoid. Thanks!

Running KinD is better than nothing. Can you post your cluster config and deployment as an example? I couldn't confidently deploy k3d and insure that I wouldn't lose the sqlite data. (I guess I could have just tested it).

Hello, Today I attempted to upgrade to Beta25, and unfortunately, the only VM I run would not start. The VM is a Ubuntu server 18.04.4. This VM has my iGPU from my 8700K passed through used for jellyfin. I am currently running 6.8.3 and it works. I am not isolating this GPU via VFIO. My go file has the following at the bottom: modprobe i915 chmod -R 777 /dev/dri This currently allows 6.8.3 the iGPU to be used by unraid when the VM is not running, and by the VM when it is running. After upgrading, I attempted to both use the existing configuration, I upgraded the configuration (for network configuration as shown in spaceinvader one's video), and tried to rerun. I attempted to isolate the iGPU via VFIO, rebooted, and tried to rerun. In each case the core 0 of the passed through cores was pinned at 100%, but the VM never started. The VM log did not throw any warnings. I also noticed that despite being in the go file /dev/dri did not exist until after manually entering modprobe i915 into the console. I have reverted back to 6.8.3 for the time being, but I am wondering if I missed something, or if there is something I need to do to resolve this issue. Thank you.