I follow the following documentation : https://sylva-projects.gitlab.io/docs/Operations/special-operations/kubevirt-procedures First, I have created a user with owner right on the workload cluster, and use the kubeconfig given by Rancher. When I deploy the VM with the given yaml file, the VM is deployed in the default namespace : ``` kubectl apply -f cirros-vm.yaml --kubeconfig ocalif2-wc-owner-kubeconfig virtualmachine.kubevirt.io/sylva-tests-cirros-vm-sma created ``` But the VM remains in Starting state : ``` kubectl get vms --kubeconfig ocalif2-wc-owner-kubeconfig NAME AGE STATUS READY sylva-tests-cirros-vm 22m Starting False ``` The VM is not in a good shape : ``` Status: Conditions: Last Probe Time: 2025-04-03T09:00:44Z Last Transition Time: 2025-04-03T09:00:44Z Message: virt-launcher pod has not yet been scheduled Reason: PodNotExists Status: False Type: Ready Last Probe Time: <nil> Last Transition Time: 2025-04-03T09:00:44Z Message: failed to create pod for vmi default/sylva-tests-cirros-vm-sma, it needs a privileged namespace to run: pods "virt-launcher-sylva-tests-cirros-vm-sma-c2qqk" is forbidden: violates PodSecurity "restricted:latest": seccompProfile (pod or containers "container-disk-binary", "volumecontainerdisk-init", "compute", "volumecontainerdisk", "guest-console-log" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost") Reason: FailedCreate Status: False Type: Synchronized Created: true Desired Generation: 1 Observed Generation: 1 Printable Status: Starting Run Strategy: Always ``` Also, the deletion doesn't work. The documentation should describe how to deploy VMs with owner or members rights.