Update virtual_machines.md

doc.zih.tu-dresden.de/docs/software/virtual_machines.md

@@ -7,7 +7,7 @@ The Singularity container setup requires a Linux machine with root privileges, t
 and a compatible kernel. If some of these requirements cannot be fulfilled, then there is also the
 option of using the provided virtual machines (VM) on ZIH systems.
 
-Currently, starting VMs is only possible on partitions `ml` and `hpdlf`. The VMs on the ML nodes are
+Currently, starting VMs is only possible on the cluster `power` (and `hpdlf`?). The VMs on the power nodes are
 used to build singularity containers for the Power9 architecture and the HPDLF nodes to build
 Singularity containers for the x86 architecture.
 
@@ -18,7 +18,7 @@ The Slurm parameter `--cloud=kvm` specifies that a virtual machine should be sta
 ### On Power9 Architecture
 
 ```console
-marie@login$ srun --partition=ml --nodes=1 --cpus-per-task=4 --hint=nomultithread --cloud=kvm --pty /bin/bash
+marie@login.power$ srun --nodes=1 --cpus-per-task=4 --hint=nomultithread --cloud=kvm --pty /bin/bash
 srun: job 6969616 queued and waiting for resources
 srun: job 6969616 has been allocated resources
 bash-4.2$
@@ -26,6 +26,7 @@ bash-4.2$
 
 ### On x86 Architecture
 
+_to be updated...._
 ```console
 marie@login$ srun --partition=hpdlf --nodes=1 --cpus-per-task=4 --hint=nomultithread --cloud=kvm --pty /bin/bash
 srun: job 2969732 queued and waiting for resources
@@ -48,7 +49,7 @@ bash-4.2$ cat /tmp/marie_2759627/activate
 if ! grep -q -- "Key for the VM on the partition ml" "/home/marie/.ssh/authorized_keys" > /dev/null; then
   cat "/tmp/marie_2759627/kvm.pub" >> "/home/marie/.ssh/authorized_keys"
 else
-  sed -i "s|.*Key for the VM on the partition ml.*|ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC3siZfQ6vQ6PtXPG0RPZwtJXYYFY73TwGYgM6mhKoWHvg+ZzclbBWVU0OoU42B3Ddofld7TFE8sqkHM6M+9jh8u+pYH4rPZte0irw5/27yM73M93q1FyQLQ8Rbi2hurYl5gihCEqomda7NQVQUjdUNVc6fDAvF72giaoOxNYfvqAkw8lFyStpqTHSpcOIL7pm6f76Jx+DJg98sXAXkuf9QK8MurezYVj1qFMho570tY+83ukA04qQSMEY5QeZ+MJDhF0gh8NXjX/6+YQrdh8TklPgOCmcIOI8lwnPTUUieK109ndLsUFB5H0vKL27dA2LZ3ZK+XRCENdUbpdoG2Czz Key for the VM on the partition ml|" "/home/marie/.ssh/authorized_keys"
+  sed -i "s|.*Key for the VM on the cluster power.*|ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC3siZfQ6vQ6PtXPG0RPZwtJXYYFY73TwGYgM6mhKoWHvg+ZzclbBWVU0OoU42B3Ddofld7TFE8sqkHM6M+9jh8u+pYH4rPZte0irw5/27yM73M93q1FyQLQ8Rbi2hurYl5gihCEqomda7NQVQUjdUNVc6fDAvF72giaoOxNYfvqAkw8lFyStpqTHSpcOIL7pm6f76Jx+DJg98sXAXkuf9QK8MurezYVj1qFMho570tY+83ukA04qQSMEY5QeZ+MJDhF0gh8NXjX/6+YQrdh8TklPgOCmcIOI8lwnPTUUieK109ndLsUFB5H0vKL27dA2LZ3ZK+XRCENdUbpdoG2Czz Key for the VM on the cluster power|" "/home/marie/.ssh/authorized_keys"
 fi
 
 ssh -i /tmp/marie_2759627/kvm root@192.168.0.6
@@ -79,8 +80,8 @@ rm -rf /tmp/sbuild-*
 ```
 
 If that does not help, e.g., because one build alone needs more than the available disk memory, then
-it will be necessary to use the `tmp` folder on `scratch`. In order to ensure that the files in the
-temporary folder will be owned by root, it is necessary to set up an image inside `/scratch/tmp`
+it will be necessary to use the `tmp` folder on `/data/horse`. In order to ensure that the files in the
+temporary folder will be owned by root, it is necessary to set up an image inside `/data/horse/tmp`
 instead of using it directly. E.g., to create a 25 GB of temporary memory image:
 
 ```console