aboutsummaryrefslogtreecommitdiffhomepage
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/2021-12-02-toying-with-virtio/index.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/content/2021-12-02-toying-with-virtio/index.md b/content/2021-12-02-toying-with-virtio/index.md
index c2ff031..8dbab9f 100644
--- a/content/2021-12-02-toying-with-virtio/index.md
+++ b/content/2021-12-02-toying-with-virtio/index.md
@@ -35,8 +35,8 @@ Additionally we setup `/etc/passwd` and `/etc/shadow` with an entry for the
`root` user with the password `1234`, so we can login via the virtio console
later.
-```sh
-{{ include_range(path="content/2021-12-02-toying-with-virtio/build_initramfs.sh", start=31, end=67) }}
+```sh,hide_lines=1-30 68-1000
+{{ include(path="content/2021-12-02-toying-with-virtio/build_initramfs.sh") }}
```
The full build script is available under [build_initramfs.sh][build-initramfs].
@@ -48,8 +48,8 @@ below.
The pci configurations are enabled because in qemu the virtio console front-end
device (the one presented to the guest) is attached to the pci bus.
-```sh
-{{ include_range(path="content/2021-12-02-toying-with-virtio/build_kernel.sh", start=32, end=38) }}
+```sh,hide_lines=1-31 39-1000
+{{ include(path="content/2021-12-02-toying-with-virtio/build_kernel.sh") }}
```
The full build script is available under [build_kernel.sh][build-kernel].
@@ -122,8 +122,8 @@ First we enable general support for block devices and then for virtio block
devices. Additionally we enable support for the `ext2` filesystem because we
are creating an ext2 filesystem to back the virtio block device.
-```sh
-{{ include_range(path="content/2021-12-02-toying-with-virtio/build_kernel.sh", start=40, end=47) }}
+```sh,hide_lines=1-39 48-1000
+{{ include(path="content/2021-12-02-toying-with-virtio/build_kernel.sh") }}
```
The full build script is available under [build_kernel.sh][build-kernel].
@@ -131,8 +131,8 @@ The full build script is available under [build_kernel.sh][build-kernel].
Next we are creating the ext2 filesystem image. This we'll do by creating an
`128M` blob and format it with ext2 afterwards. Then we can mount the image
via a `loop` device and populate the filesystem.
-```sh
-{{ include_range(path="content/2021-12-02-toying-with-virtio/build_ext2.sh", start=3, end=7) }}
+```sh,hide_lines=1-2 8-1000
+{{ include(path="content/2021-12-02-toying-with-virtio/build_ext2.sh") }}
```
Before booting the guest we will attach the virtio block device to the VM.
@@ -179,8 +179,8 @@ shown below.
First we enable general support for networking and TCP/IP and then enable the
core networking driver and the virtio net driver.
-```sh
-{{ include_range(path="content/2021-12-02-toying-with-virtio/build_kernel.sh", start=49, end=62) }}
+```sh,hide_lines=1-48 63-1000
+{{ include(path="content/2021-12-02-toying-with-virtio/build_kernel.sh") }}
```
The full build script is available under [build_kernel.sh][build-kernel].
@@ -243,8 +243,8 @@ libc resolver functions.
Additionally we assign a static ip to the `eth0` network interface, bring the
interface up and define the default route via the host `10.0.2.2`.
-```sh
-{{ include_range(path="content/2021-12-02-toying-with-virtio/build_initramfs.sh", start=69, end=85) }}
+```sh,hide_lines=1-68 86-1000
+{{ include(path="content/2021-12-02-toying-with-virtio/build_initramfs.sh") }}
```
The full build script is available under [build_initramfs.sh][build-initramfs].