diff --git a/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md b/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md
index 0b03ddf927aeed68d8726797ed04db373d24b9b3..aaf73acd36ba494ac74a5afc6f1d85ede92d3077 100644
--- a/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md
+++ b/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md
@@ -35,14 +35,19 @@ in which case you'd need to change that when moving to ZIH systems.
 
 ## Build a Singularity Container in a Job
 
-To build a Singularity container on ZIH systems simply run:
+To build a Singularity container for the power9-architecture on ZIH systems simply run:
 
 ```console
 marie@login$ buildSingularityImage --arch=power9 myContainer.sif myDefinition.def
 ```
 
-This command will submit a batch job and immediately return. Note that while Power9 is currently
-the only supported architecture, the parameter is still required. If you want it to block while the
+To build a singularity image on the x86-architecture, run:
+
+```console
+marie@login$ buildSingularityImage --arch=x86 myContainer.sif myDefinition.def
+```
+
+These commands will submit a batch job and immediately return. If you want it to block while the
 image is built and see live output, add the option `--interactive`:
 
 ```console
@@ -99,12 +104,18 @@ needs to be re-generated on every script run.
 ## Start a Job in a VM
 
 Especially when developing a Singularity definition file it might be useful to get a shell directly
-on a VM. To do so simply run:
+on a VM. To do so on the power9-architecture, simply run:
 
 ```console
 startInVM --arch=power9
 ```
 
+To do so on the x86-architecture, run:
+
+```console
+startInVM --arch=x86
+```
+
 This will execute an `srun` command with the `--cloud=kvm` parameter, wait till the VM is ready,
 mount all folders (just like `buildSingularityImage`, see the Filesystem section above) and come
 back with a bash inside the VM. Inside that you are root, so you can directly execute `singularity