sed -i "s|.*Key for the VM on the ml partition.*|ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC3siZfQ6vQ6PtXPG0RPZwtJXYYFY73TwGYgM6mhKoWHvg+ZzclbBWVU0OoU42B3Ddofld7TFE8sqkHM6M+9jh8u+pYH4rPZte0irw5/27yM73M93q1FyQLQ8Rbi2hurYl5gihCEqomda7NQVQUjdUNVc6fDAvF72giaoOxNYfvqAkw8lFyStpqTHSpcOIL7pm6f76Jx+DJg98sXAXkuf9QK8MurezYVj1qFMho570tY+83ukA04qQSMEY5QeZ+MJDhF0gh8NXjX/6+YQrdh8TklPgOCmcIOI8lwnPTUUieK109ndLsUFB5H0vKL27dA2LZ3ZK+XRCENdUbpdoG2Czz Key for the VM on the ml partition|" "/home/rotscher/.ssh/authorized_keys"
fi
if ! grep -q -- "Key for the VM on the ml partition" "/home/rotscher/.ssh/authorized_keys" >& /dev/null; then
sed -i "s|.*Key for the VM on the ml partition.*|ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC3siZfQ6vQ6PtXPG0RPZwtJXYYFY73TwGYgM6mhKoWHvg+ZzclbBWVU0OoU42B3Ddofld7TFE8sqkHM6M+9jh8u+pYH4rPZte0irw5/27yM73M93q1FyQLQ8Rbi2hurYl5gihCEqomda7NQVQUjdUNVc6fDAvF72giaoOxNYfvqAkw8lFyStpqTHSpcOIL7pm6f76Jx+DJg98sXAXkuf9QK8MurezYVj1qFMho570tY+83ukA04qQSMEY5QeZ+MJDhF0gh8NXjX/6+YQrdh8TklPgOCmcIOI8lwnPTUUieK109ndLsUFB5H0vKL27dA2LZ3ZK+XRCENdUbpdoG2Czz Key for the VM on the ml partition|" "/home/rotscher/.ssh/authorized_keys"
fi
ssh -i /tmp/rotscher_2759627/kvm root@192.168.0.6
bash-4.2$ source /tmp/rotscher_2759627/activate
Last login: Fri Jul 24 13:53:48 2020 from gateway
[root@rotscher_2759627 ~]#
ssh -i /tmp/rotscher_2759627/kvm root@192.168.0.6
bash-4.2$ source /tmp/rotscher_2759627/activate
Last login: Fri Jul 24 13:53:48 2020 from gateway
[root@rotscher_2759627 ~]#
```
## Example usage
## Automation
We provide [Tools](VMTools) to automate these steps. You may just type
**startInVM --arch=power9** on a tauruslogin node and you will be inside
the VM with everything mounted.
We provide [Tools](VMTools.md) to automate these steps. You may just type `startInVM --arch=power9`
on a tauruslogin node and you will be inside the VM with everything mounted.
## Known Issues
### Temporary Memory
The available space inside the VM can be queried with **df -h**.
Currently the whole VM has 8G and with the installed operating system,
6.6GB of available space.
The available space inside the VM can be queried with `df -h`. Currently the whole VM has 8G and
with the installed operating system, 6.6GB of available space.
Sometimes the Singularity build might fail because of a disk
out-of-memory error. In this case it might be enough to delete leftover
temporary files from Singularity:
Sometimes the Singularity build might fail because of a disk out-of-memory error. In this case it
might be enough to delete leftover temporary files from Singularity:
rm -rf /tmp/sbuild-*
```Bash
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 instead of using it directly. E.g., to create a 25GB of
temporary memory image:
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
instead of using it directly. E.g., to create a 25GB of temporary memory image:
