diff --git a/_posts/2015-08-18-multiboot-kernel.md b/_posts/2015-08-18-multiboot-kernel.md
index 0fc385fa..38f05484 100644
--- a/_posts/2015-08-18-multiboot-kernel.md
+++ b/_posts/2015-08-18-multiboot-kernel.md
@@ -214,7 +214,7 @@ Now it's time to boot our OS. We will use [QEMU]:
 [QEMU]: https://en.wikipedia.org/wiki/QEMU
 
 ```
-qemu-system-x86_64 -drive format=raw,file=os.iso
+qemu-system-x86_64 -cdrom os.iso
 ```
 ![qemu output](/images/qemu-ok.png)
 
@@ -268,7 +268,7 @@ clean:
     @rm -r build
 
 run: $(iso)
-    @qemu-system-x86_64 -drive format=raw,file=$(iso)
+    @qemu-system-x86_64 -cdrom $(iso)
 
 iso: $(iso)
 
diff --git a/_posts/2015-09-02-set-up-rust.md b/_posts/2015-09-02-set-up-rust.md
index 317a9f4b..9d479726 100644
--- a/_posts/2015-09-02-set-up-rust.md
+++ b/_posts/2015-09-02-set-up-rust.md
@@ -232,7 +232,7 @@ Such a boot loop is most likely caused by some [CPU exception][exception table].
 [Triple Fault]: http://wiki.osdev.org/Triple_Fault
 
 ```
-> qemu-system-x86_64 -d int -no-reboot -drive format=raw,file=build/os-x86_64.iso
+> qemu-system-x86_64 -d int -no-reboot -cdrom build/os-x86_64.iso
 SMM: enter
 ...
 SMM: after RSM
diff --git a/_posts/2016-01-01-remap-the-kernel.md b/_posts/2016-01-01-remap-the-kernel.md
index c2ca0e38..8e14e890 100644
--- a/_posts/2016-01-01-remap-the-kernel.md
+++ b/_posts/2016-01-01-remap-the-kernel.md
@@ -707,7 +707,7 @@ A QEMU boot load indicates that some CPU exception occured. We can see all throw
 [qemu debugging]: {% post_url 2015-09-02-set-up-rust %}#debugging
 
 ```bash
-> qemu-system-x86_64 -d int -no-reboot -drive format=raw,file=build/os-x86_64.iso
+> qemu-system-x86_64 -d int -no-reboot -cdrom build/os-x86_64.iso
 ...
 check_exception old: 0xffffffff new 0xe
      0: v=0e e=0002 i=0 cpl=0 IP=0008:000000000010ab97 pc=000000000010ab97
diff --git a/set-up-gdb.md b/set-up-gdb.md
index 1213dbea..d606f4d2 100644
--- a/set-up-gdb.md
+++ b/set-up-gdb.md
@@ -9,7 +9,7 @@ To make QEMU listen for a gdb connection, we add the `-s` flag to the `run` targ
 
 ```make
 run: $(iso)
-	@qemu-system-x86_64 -drive format=raw,file=$(iso) -s
+	@qemu-system-x86_64 -cdrom $(iso) -s
 ```
 This allows us to connect a debugger at any time, for example to investigate why a panic occurred.
 
@@ -17,7 +17,7 @@ To wait for a debugger connection on startup, we add a `debug` target to the Mak
 
 ```make
 debug: $(iso)
-	@qemu-system-x86_64 -drive format=raw,file=$(iso) -s -S
+	@qemu-system-x86_64 -cdrom $(iso) -s -S
 ```
 It is identical to the `run` target except for the additional `-S` flag. This flag causes QEMU to freeze on startup and wait until a debugger is connected. Now it _should_ be possible to connect gdb.