Skip to content

Commit 7514d50

Browse files
committed
docs(instances): add vmware migration docs
1 parent 53a1f80 commit 7514d50

File tree

2 files changed

+14
-24
lines changed

2 files changed

+14
-24
lines changed

menu/navigation.json

+4
Original file line numberDiff line numberDiff line change
@@ -1698,6 +1698,10 @@
16981698
"label": "Identifying devices of an Instance",
16991699
"slug": "identify-devices"
17001700
},
1701+
{
1702+
"label": "Migrating VMware virtual machines to Scaleway Instances",
1703+
"slug": "migrating-vms-vmware-scaleway"
1704+
},
17011705
{
17021706
"label": "Preventing outgoing DDOS",
17031707
"slug": "preventing-outgoing-ddos"

pages/instances/reference-content/migrating-vms-vmware-scaleway.mdx

+10-24
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ meta:
55
h1: Migrating VMware virtual machines to Scaleway Instances
66
paragraph: Find out how to migrate virtual VMware machines to Scaleway Instances.
77
dates:
8-
validation: 2025-03-03
9-
posted: 2023-02-22
8+
validation: 2025-04-29
9+
posted: 2024-04-29
1010
categories:
1111
- compute
12-
tags: instance type production production-optimized range POP2 ENT1
12+
tags: instance type production vmware esxi migratio
1313
---
1414

1515
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 <vm_name> /path/to/image
7474
Adjust this based on your `govmomi`/`govc` setup and environment.
7575
</Message>
7676

77-
## Converting the VMDK file to QCOW2**
77+
## Converting the VMDK file to QCOW2
7878

7979
Convert the downloaded VMDK file to QCOW2 using `qemu-img`:
8080

@@ -91,7 +91,6 @@ qemu-img convert -O qcow2 <vm_name>.vmdk <vm_name>.qcow2
9191
```
9292
Make any changes (e.g., install cloud-init, remove VMware tools).
9393

94-
9594
2. Unmount the file:
9695

9796
```bash
@@ -108,31 +107,18 @@ aws s3 cp <vm_name>.qcow2 s3://<bucket_name>/
108107

109108
## Importing the QCOW2 image from Object Storage into Scaleway as a SBS snaphot
110109

111-
Import into a new snapshot:
110+
1. Import the image into a new snapshot:
112111

113112
```bash
114-
scw instance snapshot create zone=fr-par-1 name=<my-imported-snapshot> volume-type=b_ssd bucket=<my-bucket> key=<my-qcow2-file-name.qcow2>
113+
scw block snapshot import-from-object-storage bucket=<my_bucket> key=<my-qcow2-file-name.qcow2> name=<my-imported-snapshot> size=<size-in-GB>
115114
```
116-
117-
118-
## (Optional) Create Private Networks if needed
119-
120-
121-
122-
## Booting an instance with the image and attaching the PN
123-
124-
Create a new server:
115+
2 . Create a volume from the snapshot:
125116

126117
```bash
127-
scw instance server create \
128-
name=<instance_name> \
129-
image-id=<image_id> \
130-
commercial-type=<type> \
131-
zone=<zone>
118+
scw instance image create snapshot-id=<snapshot-id> arch=x86_64
132119
```
133120

134-
Start the server:
121+
3. Create the server from the image:
135122

136123
```bash
137-
scw instance server start server-id=<server_id> zone=<zone>
138-
```
124+
scw instance server create image=<image-id> type=<commercial-type>

0 commit comments

Comments
 (0)