From 709545920eb703be6bcc759c31a241727072cccd Mon Sep 17 00:00:00 2001 From: Henry Wang Date: Thu, 8 Dec 2022 00:14:20 -0500 Subject: [PATCH] docs: Consolidate AArch64 cloud-img related doc into README Signed-off-by: Henry Wang --- README.md | 14 ++++++++------ docs/arm64.md | 11 ----------- 2 files changed, 8 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index c5910a5c7..dfd2b9978 100644 --- a/README.md +++ b/README.md @@ -199,8 +199,10 @@ For the disk image the same Ubuntu image as before can be used. This contains an `ext4` root filesystem. ```shell -$ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img -$ qemu-img convert -p -f qcow2 -O raw focal-server-cloudimg-amd64.img focal-server-cloudimg-amd64.raw +$ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img # x86-64 +$ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-arm64.img # AArch64 +$ qemu-img convert -p -f qcow2 -O raw focal-server-cloudimg-amd64.img focal-server-cloudimg-amd64.raw # x86-64 +$ qemu-img convert -p -f qcow2 -O raw focal-server-cloudimg-arm64.img focal-server-cloudimg-arm64.raw # AArch64 ``` #### Booting the guest VM @@ -258,10 +260,10 @@ Further details can be found in the [release documentation](docs/releases.md). As of 2022-10-13, the following cloud images are supported: -- [Ubuntu Bionic](https://cloud-images.ubuntu.com/bionic/current/) (bionic-server-cloudimg-amd64.img) -- [Ubuntu Focal](https://cloud-images.ubuntu.com/focal/current/) (focal-server-cloudimg-amd64.img) -- [Ubuntu Jammy](https://cloud-images.ubuntu.com/jammy/current/) (jammy-server-cloudimg-amd64.img ) -- [Fedora 36](https://fedora.mirrorservice.org/fedora/linux/releases/36/Cloud/x86_64/images/) (Fedora-Cloud-Base-36-1.5.x86_64.raw.xz) +- [Ubuntu Bionic](https://cloud-images.ubuntu.com/bionic/current/) (bionic-server-cloudimg-{amd64,arm64}.img) +- [Ubuntu Focal](https://cloud-images.ubuntu.com/focal/current/) (focal-server-cloudimg-{amd64,arm64}.img) +- [Ubuntu Jammy](https://cloud-images.ubuntu.com/jammy/current/) (jammy-server-cloudimg-{amd64,arm64}.img ) +- [Fedora 36](https://fedora.mirrorservice.org/fedora/linux/releases/36/Cloud/) ([Fedora-Cloud-Base-36-1.5.x86_64.raw.xz](https://fedora.mirrorservice.org/fedora/linux/releases/36/Cloud/x86_64/images/) / [Fedora-Cloud-Base-36-1.5.aarch64.raw.xz](https://fedora.mirrorservice.org/fedora/linux/releases/36/Cloud/aarch64/images/)) Direct kernel boot to userspace should work with a rootfs from most distributions although you may need to enable exotic filesystem types in the diff --git a/docs/arm64.md b/docs/arm64.md index b1440d9f1..0c0efd3e8 100644 --- a/docs/arm64.md +++ b/docs/arm64.md @@ -7,17 +7,6 @@ booting and direct-kernel booting. The document covers both methods. All the steps are based on Ubuntu. We use the Ubuntu cloud image for guest VM disk. -### Disk image - -Download the Ubuntu cloud image and convert the image type. - -```bash -$ pushd $CLOUDH -$ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-arm64.img -$ qemu-img convert -p -f qcow2 -O raw focal-server-cloudimg-arm64.img focal-server-cloudimg-arm64.raw -$ popd -``` - ## Direct-kernel booting Alternativelly, you can build your own kernel for guest VM. This way, UEFI is