summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxengineering <me@xengineering.eu>2025-10-16 20:35:31 +0200
committerxengineering <me@xengineering.eu>2025-10-16 20:36:25 +0200
commit85cfcdc1b231992897fe9fb1f5e026acbd99a665 (patch)
tree4cce89be4e6ce3ea22c53ada94bfffcfb9ce5dbd
parent7a1a5d7f1aab5e4968c0d7d6559a80552d3a39b0 (diff)
downloadwebsite-85cfcdc1b231992897fe9fb1f5e026acbd99a665.tar
website-85cfcdc1b231992897fe9fb1f5e026acbd99a665.tar.zst
website-85cfcdc1b231992897fe9fb1f5e026acbd99a665.zip
articles: arch-installation: Use qemu-img dd
This avoids saving a multi-gigabyte image file to disk and streams directly to the target block device.
-rw-r--r--content/articles/arch-installation.md18
1 files changed, 6 insertions, 12 deletions
diff --git a/content/articles/arch-installation.md b/content/articles/arch-installation.md
index cf183cb..57c7196 100644
--- a/content/articles/arch-installation.md
+++ b/content/articles/arch-installation.md
@@ -202,20 +202,14 @@ exit
poweroff
```
-Optionally the QEMU image can be converted to a binary image to flash it to a
-physical drive like an USB stick or SSD.
+The virtual machine image can be written to a physical drive like a boot stick
+or SSD with `qemu-img`. For that the `/dev/null` in the following command has
+to be replaced by the path to the correct drive. A mistake here might lead to
+the destruction of the current system with no way back. Use with care and only
+if you know what you are doing.
```
-qemu-img convert -f qcow2 -O raw archlinux.qcow2 archlinux.img
-```
-
-This image can be written to the target device (`/dev/sdb` in this case). It is
-very important to select the correct target and triple-check the following
-command before execution. If the currently used system is the target it is
-simply overwritten without any way back!
-
-```
-dd if=archlinux.img of=/dev/sdb bs=512 status=progress
+qemu-img dd -f qcow2 -O raw if=archlinux.qcow2 of=/dev/null
```
Otherwise the virtual machine image can be started again with QEMU without the