From a9b95ed8c38691218eac4d0dc863f10e6fc7611f Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 23 Apr 2025 11:10:13 +0200 Subject: [PATCH 01/11] docs(ins): init migrate docs --- .../migrating-vms-vmware-scaleway.mdx | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx new file mode 100644 index 0000000000..fce989697b --- /dev/null +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -0,0 +1,13 @@ +--- +meta: + title: Migrating VMware virtual machines to Scaleway Instances + description: Find out how to migrate virtual VMware machines to Scaleway Instances. + h1: Migrating VMware virtual machines to Scaleway Instances + paragraph: Find out how to migrate virtual VMware machines to Scaleway Instances. +dates: + validation: 2025-03-03 + posted: 2023-02-22 +categories: + - compute +tags: instance type production production-optimized range POP2 ENT1 +--- From 61d2ef420cd145be5f107f3cce0b0e767e56e881 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 23 Apr 2025 11:53:44 +0200 Subject: [PATCH 02/11] docs(ins): update --- .../migrating-vms-vmware-scaleway.mdx | 144 ++++++++++++++++++ 1 file changed, 144 insertions(+) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index fce989697b..d01dcbd3f7 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -11,3 +11,147 @@ categories: - compute tags: instance type production production-optimized range POP2 ENT1 --- + +## Validating the inventory of machines to migrate + +Identify the virtual machines (VMs) to migrate on your VMware plattform: + +- Disk configuration (number, size, type) +- Network configuration (number of NICs, type) +- Boot type (BIOS or UEFI) + + +## Preparing a Scaleway Instance to manage the migration + +1. [Create a new instance](/instances/how-to/create-an-instance/) and log into it [using SSH](/instances/how-to/connect-to-instance/). +2. Install the following CLI tools, required for the migration of your virtual machine: + - `qemu-img` — for converting VMDK to QCOW2 + ```sh + apt install qemu-utils + ``` + - `scw` — for Scaleway operations + ```sh + curl -s https://raw.githubusercontent.com/scaleway/scaleway-cli/master/scripts/get.sh | sh + ``` + - `aws` — for uploading to S3 + ``` + curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" + unzip awscliv2.zip + sudo ./aws/install + ``` + - `govmomi` — for interacting with vCenter + ``` + curl -L -o - "https://github.com/vmware/govmomi/releases/latest/download/govc_$(uname -s)_$(uname -m).tar.gz" | tar -C /usr/local/bin -xvzf - govc + ``` + +3. Configure credentials for the tools: + - For Scaleway: `scw init` + - For AWS/S3: Refer to [Using Object Storage with the AWS-CLI](https://www.scaleway.com/en/docs/object-storage/api-cli/object-storage-aws-cli/) + - For vCenter: credentials and VPN (if needed) + +## Downloading VMDK files using govmomi + +Download the VMDK file from vCenter: + +```bash +govc export.ovf -vm +``` + + + Adjust this based on your `govmomi`/`govc` setup and environment. + + +## Converting the VMDK file to QCOW2** + +Convert the downloaded VMDK file to QCOW2 using `qemu-img`: + +```bash +qemu-img convert -O qcow2 .vmdk .qcow2 +``` + +### (Optional): Mounting the QCOW2 file and system configuration + +1. Mount the QCOW2 image on your Instance: + ```bash + sudo modprobe nbd + sudo qemu-nbd -c /dev/nbd0 .qcow2 + ``` + Make any changes (e.g., install cloud-init, remove VMware tools). + +2. Unmount the file: + +```bash +sudo qemu-nbd -d /dev/nbd0 +``` + +## Uploading the QCOW2 image to Scaleway Object Storage + +Upload the converted disk: + +```bash +aws s3 cp .qcow2 s3:/// +``` + +## Importing the QCOW2 image from Object Storage into Scaleway as a volume + +Import into a new volume: + +```bash +scw instance volume import qcow2-from-s3 \ + s3-url=s3:///.qcow2 \ + name= \ + project-id= \ + zone= +``` + +> You can retrieve project ID and zone using `scw project list` and `scw zone list`. + +--- + +### **Step 8: Create an image from the imported volume** + +```bash +scw instance image create-from-volume \ + volume-id= \ + name= \ + zone= +``` + +--- + +### **Step 9: Create Private Networks if needed** + +```bash +scw vpc private-network create \ + name= \ + ipam-configs.0.cidr= +``` + +--- + +### **Step 10: Boot an instance with the image and attach PN** + +Create a new server: + +```bash +scw instance server create \ + name= \ + image-id= \ + commercial-type= \ + zone= \ + private-nics.0.private-network-id= +``` + +Start the server: + +```bash +scw instance server start server-id= zone= +``` + +--- + +## ✅ Final Notes + +- Run `scw --help` or `scw instance server create --help` for more guidance. +- Double-check your Scaleway **region/zone compatibility** (e.g., `fr-par-1`, `nl-ams-1`, etc.). +- Ensure the image is cloud-ready: ideally includes `cloud-init`. \ No newline at end of file From 53a1f80cfac072dd1d620c57498f2319c488a7e4 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 23 Apr 2025 14:23:36 +0200 Subject: [PATCH 03/11] docs(ins): content --- .../migrating-vms-vmware-scaleway.mdx | 73 +++++++------------ 1 file changed, 27 insertions(+), 46 deletions(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index d01dcbd3f7..10ed904e00 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -12,6 +12,13 @@ categories: tags: instance type production production-optimized range POP2 ENT1 --- +Migrating virtual machines from one platform to another can be a complex process, especially when moving from a proprietary environment like VMware to a cloud-based infrastructure like Scaleway. +However, with the right tools and a step-by-step approach, you can successfully migrate your VMware virtual machines to Scaleway Instances, taking advantage of the scalability, flexibility, and cost-effectiveness of the cloud. + +This guide will walk you through the process of migrating your VMware virtual machines to Scaleway Instances, covering everything from preparing your Scaleway Instance to managing the migration, converting VMDK files to QCOW2, +uploading the QCOW2 image to Scaleway Object Storage, and finally, creating an image from the imported volume and booting an instance with the image. +By following these steps, you'll be able to seamlessly migrate your VMware virtual machines to Scaleway Instances, ensuring minimal downtime and optimal performance. + ## Validating the inventory of machines to migrate Identify the virtual machines (VMs) to migrate on your VMware plattform: @@ -23,7 +30,7 @@ Identify the virtual machines (VMs) to migrate on your VMware plattform: ## Preparing a Scaleway Instance to manage the migration -1. [Create a new instance](/instances/how-to/create-an-instance/) and log into it [using SSH](/instances/how-to/connect-to-instance/). +1. [Create a new Instance](/instances/how-to/create-an-instance/) to handle the migration and log into it [using SSH](/instances/how-to/connect-to-instance/). 2. Install the following CLI tools, required for the migration of your virtual machine: - `qemu-img` — for converting VMDK to QCOW2 ```sh @@ -47,14 +54,20 @@ Identify the virtual machines (VMs) to migrate on your VMware plattform: 3. Configure credentials for the tools: - For Scaleway: `scw init` - For AWS/S3: Refer to [Using Object Storage with the AWS-CLI](https://www.scaleway.com/en/docs/object-storage/api-cli/object-storage-aws-cli/) - - For vCenter: credentials and VPN (if needed) + - For vCenter: credentials and VPN (if needed): + ``` + export GOVC_PASSWORD= + export GOVC_USERNAME=root + export GOVC_INSECURE=1 + export GOVC_URL= + ``` ## Downloading VMDK files using govmomi Download the VMDK file from vCenter: ```bash -govc export.ovf -vm +govc export.ovf -vm /path/to/image ``` @@ -73,15 +86,16 @@ qemu-img convert -O qcow2 .vmdk .qcow2 1. Mount the QCOW2 image on your Instance: ```bash - sudo modprobe nbd - sudo qemu-nbd -c /dev/nbd0 .qcow2 + modprobe nbd + qemu-nbd -c /dev/nbd0 .qcow2 ``` Make any changes (e.g., install cloud-init, remove VMware tools). + 2. Unmount the file: ```bash -sudo qemu-nbd -d /dev/nbd0 +qemu-nbd -d /dev/nbd0 ``` ## Uploading the QCOW2 image to Scaleway Object Storage @@ -92,44 +106,20 @@ Upload the converted disk: aws s3 cp .qcow2 s3:/// ``` -## Importing the QCOW2 image from Object Storage into Scaleway as a volume - -Import into a new volume: - -```bash -scw instance volume import qcow2-from-s3 \ - s3-url=s3:///.qcow2 \ - name= \ - project-id= \ - zone= -``` - -> You can retrieve project ID and zone using `scw project list` and `scw zone list`. - ---- +## Importing the QCOW2 image from Object Storage into Scaleway as a SBS snaphot -### **Step 8: Create an image from the imported volume** +Import into a new snapshot: ```bash -scw instance image create-from-volume \ - volume-id= \ - name= \ - zone= +scw instance snapshot create zone=fr-par-1 name= volume-type=b_ssd bucket= key= ``` ---- -### **Step 9: Create Private Networks if needed** +## (Optional) Create Private Networks if needed -```bash -scw vpc private-network create \ - name= \ - ipam-configs.0.cidr= -``` ---- -### **Step 10: Boot an instance with the image and attach PN** +## Booting an instance with the image and attaching the PN Create a new server: @@ -138,20 +128,11 @@ scw instance server create \ name= \ image-id= \ commercial-type= \ - zone= \ - private-nics.0.private-network-id= + zone= ``` Start the server: ```bash scw instance server start server-id= zone= -``` - ---- - -## ✅ Final Notes - -- Run `scw --help` or `scw instance server create --help` for more guidance. -- Double-check your Scaleway **region/zone compatibility** (e.g., `fr-par-1`, `nl-ams-1`, etc.). -- Ensure the image is cloud-ready: ideally includes `cloud-init`. \ No newline at end of file +``` \ No newline at end of file From 7514d5002bc4d66ce4053b25bee8f706894dc5c2 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 29 Apr 2025 13:53:25 +0200 Subject: [PATCH 04/11] docs(instances): add vmware migration docs --- menu/navigation.json | 4 +++ .../migrating-vms-vmware-scaleway.mdx | 34 ++++++------------- 2 files changed, 14 insertions(+), 24 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index e347a21d35..4694c45db7 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -1698,6 +1698,10 @@ "label": "Identifying devices of an Instance", "slug": "identify-devices" }, + { + "label": "Migrating VMware virtual machines to Scaleway Instances", + "slug": "migrating-vms-vmware-scaleway" + }, { "label": "Preventing outgoing DDOS", "slug": "preventing-outgoing-ddos" diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 10ed904e00..ecad6f5c97 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -5,11 +5,11 @@ meta: h1: Migrating VMware virtual machines to Scaleway Instances paragraph: Find out how to migrate virtual VMware machines to Scaleway Instances. dates: - validation: 2025-03-03 - posted: 2023-02-22 + validation: 2025-04-29 + posted: 2024-04-29 categories: - compute -tags: instance type production production-optimized range POP2 ENT1 +tags: instance type production vmware esxi migratio --- Migrating virtual machines from one platform to another can be a complex process, especially when moving from a proprietary environment like VMware to a cloud-based infrastructure like Scaleway. @@ -74,7 +74,7 @@ govc export.ovf -vm /path/to/image Adjust this based on your `govmomi`/`govc` setup and environment. -## Converting the VMDK file to QCOW2** +## Converting the VMDK file to QCOW2 Convert the downloaded VMDK file to QCOW2 using `qemu-img`: @@ -91,7 +91,6 @@ qemu-img convert -O qcow2 .vmdk .qcow2 ``` Make any changes (e.g., install cloud-init, remove VMware tools). - 2. Unmount the file: ```bash @@ -108,31 +107,18 @@ aws s3 cp .qcow2 s3:/// ## Importing the QCOW2 image from Object Storage into Scaleway as a SBS snaphot -Import into a new snapshot: +1. Import the image into a new snapshot: ```bash -scw instance snapshot create zone=fr-par-1 name= volume-type=b_ssd bucket= key= +scw block snapshot import-from-object-storage bucket= key= name= size= ``` - - -## (Optional) Create Private Networks if needed - - - -## Booting an instance with the image and attaching the PN - -Create a new server: +2 . Create a volume from the snapshot: ```bash -scw instance server create \ - name= \ - image-id= \ - commercial-type= \ - zone= +scw instance image create snapshot-id= arch=x86_64 ``` -Start the server: +3. Create the server from the image: ```bash -scw instance server start server-id= zone= -``` \ No newline at end of file +scw instance server create image= type= From 0d1263b487f99974c0becb8b2a0a1867dcdd221b Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 10:05:40 +0200 Subject: [PATCH 05/11] feat(ins): content --- .../migrating-vms-vmware-scaleway.mdx | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index ecad6f5c97..8d32612c32 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -9,7 +9,7 @@ dates: posted: 2024-04-29 categories: - compute -tags: instance type production vmware esxi migratio +tags: instance type production vmware esxi migration --- Migrating virtual machines from one platform to another can be a complex process, especially when moving from a proprietary environment like VMware to a cloud-based infrastructure like Scaleway. @@ -24,8 +24,17 @@ By following these steps, you'll be able to seamlessly migrate your VMware virtu Identify the virtual machines (VMs) to migrate on your VMware plattform: - Disk configuration (number, size, type) + + If multiple disks are present, repeat the same steps to create several snapshots and group them as a single Scaleway image. + - Network configuration (number of NICs, type) + + If multiple NICs are needed, several Private Networks can be added to the Instance later. + - Boot type (BIOS or UEFI) + + Only UEFI boot is compatible with Scaleway Instances + ## Preparing a Scaleway Instance to manage the migration @@ -89,7 +98,7 @@ qemu-img convert -O qcow2 .vmdk .qcow2 modprobe nbd qemu-nbd -c /dev/nbd0 .qcow2 ``` - Make any changes (e.g., install cloud-init, remove VMware tools). + Make any changes (e.g., install cloud-init, add VirtIO drivers, remove VMware tools). 2. Unmount the file: @@ -112,7 +121,7 @@ aws s3 cp .qcow2 s3:/// ```bash scw block snapshot import-from-object-storage bucket= key= name= size= ``` -2 . Create a volume from the snapshot: +2 . Create a Scaleway image from the snapshot: ```bash scw instance image create snapshot-id= arch=x86_64 @@ -122,3 +131,5 @@ scw instance image create snapshot-id= arch=x86_64 ```bash scw instance server create image= type= + + From d2fea01bbb373953c64ccd4f1069f4f28249e00f Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 10:40:55 +0200 Subject: [PATCH 06/11] docs(ins): add pn command --- .../migrating-vms-vmware-scaleway.mdx | 43 ++++++++++--------- 1 file changed, 22 insertions(+), 21 deletions(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 8d32612c32..5773e78d71 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -5,8 +5,8 @@ meta: h1: Migrating VMware virtual machines to Scaleway Instances paragraph: Find out how to migrate virtual VMware machines to Scaleway Instances. dates: - validation: 2025-04-29 - posted: 2024-04-29 + validation: 2025-05-14 + posted: 2025-05-14 categories: - compute tags: instance type production vmware esxi migration @@ -101,35 +101,36 @@ qemu-img convert -O qcow2 .vmdk .qcow2 Make any changes (e.g., install cloud-init, add VirtIO drivers, remove VMware tools). 2. Unmount the file: - -```bash -qemu-nbd -d /dev/nbd0 -``` + ```bash + qemu-nbd -d /dev/nbd0 + ``` ## Uploading the QCOW2 image to Scaleway Object Storage Upload the converted disk: - -```bash -aws s3 cp .qcow2 s3:/// -``` + ```bash + aws s3 cp .qcow2 s3:/// + ``` ## Importing the QCOW2 image from Object Storage into Scaleway as a SBS snaphot 1. Import the image into a new snapshot: - -```bash -scw block snapshot import-from-object-storage bucket= key= name= size= -``` + ```bash + scw block snapshot import-from-object-storage bucket= key= name= size= + ``` 2 . Create a Scaleway image from the snapshot: - -```bash -scw instance image create snapshot-id= arch=x86_64 -``` + ```bash + scw instance image create snapshot-id= arch=x86_64 + ``` 3. Create the server from the image: + ```bash + scw instance server create image= type= + ``` -```bash -scw instance server create image= type= - +### Adding private NICs to the Instance (otional) +Create a private NIC for the Instance, allowing it to connect to an [existing Private Network](/vpc/quickstart/#how-to-create-a-private-network) + ```bash + scw instance private-nic create server-id= private-network-id= ipam-ip-ids.{0}= + ``` \ No newline at end of file From fa0ae8e102dffc7feb224f15f63edf358b666fe7 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 10:49:17 +0200 Subject: [PATCH 07/11] docs(ins): fix typo --- .../reference-content/migrating-vms-vmware-scaleway.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 5773e78d71..115c21cf96 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -2,6 +2,7 @@ meta: title: Migrating VMware virtual machines to Scaleway Instances description: Find out how to migrate virtual VMware machines to Scaleway Instances. +content: h1: Migrating VMware virtual machines to Scaleway Instances paragraph: Find out how to migrate virtual VMware machines to Scaleway Instances. dates: @@ -34,7 +35,7 @@ Identify the virtual machines (VMs) to migrate on your VMware plattform: - Boot type (BIOS or UEFI) Only UEFI boot is compatible with Scaleway Instances - + ## Preparing a Scaleway Instance to manage the migration From cf62997a673d7c4b1bf7f55867659c0662f5267d Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 14:58:04 +0200 Subject: [PATCH 08/11] feat(ins): add warning for windows --- .../reference-content/migrating-vms-vmware-scaleway.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 115c21cf96..7d6fc98f1c 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -37,6 +37,9 @@ Identify the virtual machines (VMs) to migrate on your VMware plattform: Only UEFI boot is compatible with Scaleway Instances + + If your virtual machine is running Windows, make sure to install the [virtiofs drivers](https://virtio-fs.gitlab.io/howto-windows.html) before exporting the VM. + ## Preparing a Scaleway Instance to manage the migration From 2d692bd5a28c9abf2d43c1d1c2c8c435da4b2de9 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 17:00:57 +0200 Subject: [PATCH 09/11] Apply suggestions from code review Co-authored-by: Fabien Malfoy --- .../reference-content/migrating-vms-vmware-scaleway.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 7d6fc98f1c..4318489e16 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -22,7 +22,7 @@ By following these steps, you'll be able to seamlessly migrate your VMware virtu ## Validating the inventory of machines to migrate -Identify the virtual machines (VMs) to migrate on your VMware plattform: +Identify the virtual machines (VMs) to migrate on your VMware platform: - Disk configuration (number, size, type) From f7425cf47a8ec29460a71891de04ad22b1b96afd Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 17:17:15 +0200 Subject: [PATCH 10/11] feat(ins): update content --- .../reference-content/migrating-vms-vmware-scaleway.mdx | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 4318489e16..5c35f34431 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -43,7 +43,7 @@ Identify the virtual machines (VMs) to migrate on your VMware platform: ## Preparing a Scaleway Instance to manage the migration -1. [Create a new Instance](/instances/how-to/create-an-instance/) to handle the migration and log into it [using SSH](/instances/how-to/connect-to-instance/). +1. [Create a new Instance](/instances/how-to/create-an-instance/) (running Ubuntu 24.04 or Debian 12) to handle the migration and log into it [using SSH](/instances/how-to/connect-to-instance/). 2. Install the following CLI tools, required for the migration of your virtual machine: - `qemu-img` — for converting VMDK to QCOW2 ```sh @@ -102,8 +102,11 @@ qemu-img convert -O qcow2 .vmdk .qcow2 modprobe nbd qemu-nbd -c /dev/nbd0 .qcow2 ``` - Make any changes (e.g., install cloud-init, add VirtIO drivers, remove VMware tools). - + Make any changes (e.g., install `cloud-init`, `scaleway-ecosystem`, add VirtIO drivers, remove VMware tools). + + - The `cloud-init` package is required for the Instance to work correctly in the Scaleway environment. + - Installing the [scaleway-ecosystem](https://github.com/scaleway/scaleway-packages/releases) package is also highly recommeneded. + 2. Unmount the file: ```bash qemu-nbd -d /dev/nbd0 From bcad17bc56a4d751619e9ad6c210bcd23cca51f3 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 14 May 2025 17:32:30 +0200 Subject: [PATCH 11/11] Update pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx Co-authored-by: Fabien Malfoy --- .../reference-content/migrating-vms-vmware-scaleway.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx index 5c35f34431..2d25bddd93 100644 --- a/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx +++ b/pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx @@ -105,7 +105,7 @@ qemu-img convert -O qcow2 .vmdk .qcow2 Make any changes (e.g., install `cloud-init`, `scaleway-ecosystem`, add VirtIO drivers, remove VMware tools). - The `cloud-init` package is required for the Instance to work correctly in the Scaleway environment. - - Installing the [scaleway-ecosystem](https://github.com/scaleway/scaleway-packages/releases) package is also highly recommeneded. + - Installing the [scaleway-ecosystem](https://github.com/scaleway/scaleway-packages/releases) package is also highly recommended. 2. Unmount the file: ```bash