Gaurav Mehta

The nvidia-driver-runtime image cannot be pulled by your nodes ``` nvidia-driver-runtime-5vvwn 0/1 ImagePullBackOff 0 21h ``` This image is not shipped in the iso and needs to be pulled to...

The private registry is a container registry. I do not think microOS contains a registry of its own. You could use something like [goharbor](https://goharbor.io/) to get started with a private...

are you able to ssh to all your nodes and just run `docker pull rancher/harvester-nvidia-driver-toolkit:v1.3-20240307` if the nodes can pull this image then the addon should work

we should improve the device plugin pcidevices controller to monitor resource usage: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources additional changes may be needed in the harvester api to federate plugin info from all nodes for...

@hoo29 any chance we could please have a support bundle from this cluster?

that looks like a k8s workload, may be better option is to just recreate it?

the mutating webhook fixes are now available in rc2

There are 2 issues: 1. nvidia driver toolkit addon needs a UI enhancement to allow users to specify an override image and location for GPU driver. Currently enabling the addon...

The easiest way to test is as follows: * Create a KVM instance with 2 disks, in my case I created one with two 250G disks  * Boot with...

any chance we could have a support bundle or the logs of the virt-launcher pod? this could be related to: https://github.com/harvester/pcidevices/issues/29, where if a device is part of a iommu...