Skip to content

Commit 1da9a14

Browse files
committed
Add KVM support to VM Importer
Related to: harvester/harvester#9948 Signed-off-by: Volker Theile <vtheile@suse.com>
1 parent 5bd19e2 commit 1da9a14

1 file changed

Lines changed: 31 additions & 0 deletions

File tree

‎docs/advanced/addons/vmimport.md‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ Currently, the following source providers are supported:
2424
* VMware
2525
* OpenStack
2626
* Open Virtual Appliance (OVA)
27+
* KVM
2728

2829
## API
2930
The vm-import-controller introduces two CRDs.
@@ -150,6 +151,36 @@ NAME STATUS
150151
example clusterReady
151152
```
152153

154+
For KVM-based sources, an example definition is as follows:
155+
156+
```yaml
157+
apiVersion: migration.harvesterhci.io/v1beta1
158+
kind: KVMSource
159+
metadata:
160+
name: kvm
161+
namespace: default
162+
spec:
163+
libvirtURI: "qemu+ssh://192.168.0.1/system"
164+
credentials:
165+
name: example-kvm-credentials
166+
namespace: default
167+
```
168+
169+
Check out the libvirt documentation on how to configure the [libvirtURI](https://libvirt.org/uri.html) field.
170+
When configuring the secret, you can include the authentication credentials that are used to log into the source system via SSH.
171+
172+
```yaml
173+
apiVersion: v1
174+
kind: Secret
175+
metadata:
176+
name: example-kvm-credentials
177+
namespace: default
178+
stringData:
179+
"username": "user"
180+
"password": "password"
181+
"privateKey": "pem-encoded-private-key"
182+
```
183+
153184
### VirtualMachineImport
154185
The VirtualMachineImport CRD provides a way for users to define a source VM and map to the actual source cluster to perform VM export/import.
155186

0 commit comments

Comments
 (0)