diff options
Diffstat (limited to 'blog/gentoo-on-gcloud.org')
-rw-r--r-- | blog/gentoo-on-gcloud.org | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/blog/gentoo-on-gcloud.org b/blog/gentoo-on-gcloud.org index d826e53..2ab530e 100644 --- a/blog/gentoo-on-gcloud.org +++ b/blog/gentoo-on-gcloud.org @@ -1,8 +1,8 @@ -* gentoo on google cloud +* Gentoo On Google Cloud Google Cloud only provides Debian and a few other operating system images by default, but does allow bringing your own ISO. -** gentoo official qcow2 images +** Gentoo Official QCOW2 Images The first thing I tried was booting one of Gentoo's official qcow2 images directly. @@ -18,7 +18,7 @@ After doing these steps, I created a new vm instance with the Gentoo qcow2 image I am not exactly sure what is wrong with gcloud, but these images boot fine in qemu for me. -** hijacking a debian image +** Hijacking A Debian Image Instead of using one of the official Gentoo images, we decided to "hijack" one of gclouds already booting Debian images. To do this, I created a new instance using the default Debian boot disk, and then cloned the instance's disk while the instance was shut down. Then I booted the instance back up, and attached the clone'd disk to the instance. @@ -31,6 +31,6 @@ The trick that got it to boot, was clearing out the old EFI binaries completely, After installing our new bootloader, I shut down the instance, detached the boot disk, and reattached the Gentoo disk as the new boot disk. Then booted into Gentoo! -* tldr +* TLDR To get it to boot, you hijack a working image by making a new rootfs on the rootfs partition, replace the kernel, initramfs and then the bootloader with a "removable" bootloader (aka ~grub-install --removable~). |