diff --git a/static/img/v1.2/vm-hv/access-to-vm.png b/static/img/v1.2/vm-hv/access-to-vm.png new file mode 100644 index 0000000..a8aa190 Binary files /dev/null and b/static/img/v1.2/vm-hv/access-to-vm.png differ diff --git a/static/img/v1.2/vm-hv/add-volume-button.png b/static/img/v1.2/vm-hv/add-volume-button.png new file mode 100644 index 0000000..2eb5698 Binary files /dev/null and b/static/img/v1.2/vm-hv/add-volume-button.png differ diff --git a/static/img/v1.2/vm-hv/add-volume-panel.png b/static/img/v1.2/vm-hv/add-volume-panel.png new file mode 100644 index 0000000..12fa242 Binary files /dev/null and b/static/img/v1.2/vm-hv/add-volume-panel.png differ diff --git a/static/img/v1.2/vm-hv/backuptarget-nfs.png b/static/img/v1.2/vm-hv/backuptarget-nfs.png new file mode 100644 index 0000000..e2afbaf Binary files /dev/null and b/static/img/v1.2/vm-hv/backuptarget-nfs.png differ diff --git a/static/img/v1.2/vm-hv/backuptarget-s3.png b/static/img/v1.2/vm-hv/backuptarget-s3.png new file mode 100644 index 0000000..cfe63ee Binary files /dev/null and b/static/img/v1.2/vm-hv/backuptarget-s3.png differ diff --git a/static/img/v1.2/vm-hv/check-schadule-backups.png b/static/img/v1.2/vm-hv/check-schadule-backups.png new file mode 100644 index 0000000..6f804ff Binary files /dev/null and b/static/img/v1.2/vm-hv/check-schadule-backups.png differ diff --git a/static/img/v1.2/vm-hv/check-schadule-basic.png b/static/img/v1.2/vm-hv/check-schadule-basic.png new file mode 100644 index 0000000..b9e8ca4 Binary files /dev/null and b/static/img/v1.2/vm-hv/check-schadule-basic.png differ diff --git a/static/img/v1.2/vm-hv/clone-vm-with-data.png b/static/img/v1.2/vm-hv/clone-vm-with-data.png new file mode 100644 index 0000000..62600b9 Binary files /dev/null and b/static/img/v1.2/vm-hv/clone-vm-with-data.png differ diff --git a/static/img/v1.2/vm-hv/clone-vm-without-data.png b/static/img/v1.2/vm-hv/clone-vm-without-data.png new file mode 100644 index 0000000..7cd6252 Binary files /dev/null and b/static/img/v1.2/vm-hv/clone-vm-without-data.png differ diff --git a/static/img/v1.2/vm-hv/configure-schedule.png b/static/img/v1.2/vm-hv/configure-schedule.png new file mode 100644 index 0000000..c4ba122 Binary files /dev/null and b/static/img/v1.2/vm-hv/configure-schedule.png differ diff --git a/static/img/v1.2/vm-hv/create-backup.png b/static/img/v1.2/vm-hv/create-backup.png new file mode 100644 index 0000000..759eab6 Binary files /dev/null and b/static/img/v1.2/vm-hv/create-backup.png differ diff --git a/static/img/v1.2/vm-hv/create-schadule.png b/static/img/v1.2/vm-hv/create-schadule.png new file mode 100644 index 0000000..9fdbbdd Binary files /dev/null and b/static/img/v1.2/vm-hv/create-schadule.png differ diff --git a/static/img/v1.2/vm-hv/create-snapshot.png b/static/img/v1.2/vm-hv/create-snapshot.png new file mode 100644 index 0000000..a1c7e5b Binary files /dev/null and b/static/img/v1.2/vm-hv/create-snapshot.png differ diff --git a/static/img/v1.2/vm-hv/download-vm-image.png b/static/img/v1.2/vm-hv/download-vm-image.png new file mode 100644 index 0000000..aff93e9 Binary files /dev/null and b/static/img/v1.2/vm-hv/download-vm-image.png differ diff --git a/static/img/v1.2/vm-hv/edit-quota-namespace-read.png b/static/img/v1.2/vm-hv/edit-quota-namespace-read.png new file mode 100644 index 0000000..96eac6c Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-quota-namespace-read.png differ diff --git a/static/img/v1.2/vm-hv/edit-quota-namespace-save.png b/static/img/v1.2/vm-hv/edit-quota-namespace-save.png new file mode 100644 index 0000000..789664c Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-quota-namespace-save.png differ diff --git a/static/img/v1.2/vm-hv/edit-quota-namespace.png b/static/img/v1.2/vm-hv/edit-quota-namespace.png new file mode 100644 index 0000000..30a0875 Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-quota-namespace.png differ diff --git a/static/img/v1.2/vm-hv/edit-quota-vm-read.png b/static/img/v1.2/vm-hv/edit-quota-vm-read.png new file mode 100644 index 0000000..197f21a Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-quota-vm-read.png differ diff --git a/static/img/v1.2/vm-hv/edit-quota-vm-save.png b/static/img/v1.2/vm-hv/edit-quota-vm-save.png new file mode 100644 index 0000000..e38d974 Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-quota-vm-save.png differ diff --git a/static/img/v1.2/vm-hv/edit-quota-vm.png b/static/img/v1.2/vm-hv/edit-quota-vm.png new file mode 100644 index 0000000..1be1ecd Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-quota-vm.png differ diff --git a/static/img/v1.2/vm-hv/edit-schedule-config.png b/static/img/v1.2/vm-hv/edit-schedule-config.png new file mode 100644 index 0000000..4a1ec07 Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-schedule-config.png differ diff --git a/static/img/v1.2/vm-hv/edit-schedule-parameters.png b/static/img/v1.2/vm-hv/edit-schedule-parameters.png new file mode 100644 index 0000000..5d77d89 Binary files /dev/null and b/static/img/v1.2/vm-hv/edit-schedule-parameters.png differ diff --git a/static/img/v1.2/vm-hv/fs-freeze-fail.png b/static/img/v1.2/vm-hv/fs-freeze-fail.png new file mode 100644 index 0000000..35488a7 Binary files /dev/null and b/static/img/v1.2/vm-hv/fs-freeze-fail.png differ diff --git a/static/img/v1.2/vm-hv/overcommit-page.png b/static/img/v1.2/vm-hv/overcommit-page.png new file mode 100644 index 0000000..714d243 Binary files /dev/null and b/static/img/v1.2/vm-hv/overcommit-page.png differ diff --git a/static/img/v1.2/vm-hv/overcommit-panel.png b/static/img/v1.2/vm-hv/overcommit-panel.png new file mode 100644 index 0000000..2651b0c Binary files /dev/null and b/static/img/v1.2/vm-hv/overcommit-panel.png differ diff --git a/static/img/v1.2/vm-hv/restore-snapshot-existing.png b/static/img/v1.2/vm-hv/restore-snapshot-existing.png new file mode 100644 index 0000000..7f1f866 Binary files /dev/null and b/static/img/v1.2/vm-hv/restore-snapshot-existing.png differ diff --git a/static/img/v1.2/vm-hv/restore-vm-snapshot.png b/static/img/v1.2/vm-hv/restore-vm-snapshot.png new file mode 100644 index 0000000..3213ce9 Binary files /dev/null and b/static/img/v1.2/vm-hv/restore-vm-snapshot.png differ diff --git a/static/img/v1.2/vm-hv/restore-vm.png b/static/img/v1.2/vm-hv/restore-vm.png new file mode 100644 index 0000000..0be8e47 Binary files /dev/null and b/static/img/v1.2/vm-hv/restore-vm.png differ diff --git a/static/img/v1.2/vm-hv/suspend-resume-schedule.png b/static/img/v1.2/vm-hv/suspend-resume-schedule.png new file mode 100644 index 0000000..86149b5 Binary files /dev/null and b/static/img/v1.2/vm-hv/suspend-resume-schedule.png differ diff --git a/static/img/v1.2/vm-hv/vm-add-access-credentails.png b/static/img/v1.2/vm-hv/vm-add-access-credentails.png new file mode 100644 index 0000000..56d9525 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-add-access-credentails.png differ diff --git a/static/img/v1.2/vm-hv/vm-backup-results.png b/static/img/v1.2/vm-hv/vm-backup-results.png new file mode 100644 index 0000000..fb90f58 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-backup-results.png differ diff --git a/static/img/v1.2/vm-hv/vm-backup.png b/static/img/v1.2/vm-hv/vm-backup.png new file mode 100644 index 0000000..7c822fc Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-backup.png differ diff --git a/static/img/v1.2/vm-hv/vm-overcommit-config.png b/static/img/v1.2/vm-hv/vm-overcommit-config.png new file mode 100644 index 0000000..49bd686 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-overcommit-config.png differ diff --git a/static/img/v1.2/vm-hv/vm-restore-existing.png b/static/img/v1.2/vm-hv/vm-restore-existing.png new file mode 100644 index 0000000..1968334 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-restore-existing.png differ diff --git a/static/img/v1.2/vm-hv/vm-snapshot-results.png b/static/img/v1.2/vm-hv/vm-snapshot-results.png new file mode 100644 index 0000000..f7228b7 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-snapshot-results.png differ diff --git a/static/img/v1.2/vm-hv/vm-snapshot.png b/static/img/v1.2/vm-hv/vm-snapshot.png new file mode 100644 index 0000000..f043da0 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-snapshot.png differ diff --git a/static/img/v1.2/vm-hv/vm-ssh-keys.png b/static/img/v1.2/vm-hv/vm-ssh-keys.png new file mode 100644 index 0000000..75a8f03 Binary files /dev/null and b/static/img/v1.2/vm-hv/vm-ssh-keys.png differ diff --git a/static/img/v1.4/cpu-pinning-hv/create-vm.png b/static/img/v1.4/cpu-pinning-hv/create-vm.png new file mode 100644 index 0000000..0df9ec3 Binary files /dev/null and b/static/img/v1.4/cpu-pinning-hv/create-vm.png differ diff --git a/static/img/v1.4/cpu-pinning-hv/disable-cpu-manager.png b/static/img/v1.4/cpu-pinning-hv/disable-cpu-manager.png new file mode 100644 index 0000000..d367fcb Binary files /dev/null and b/static/img/v1.4/cpu-pinning-hv/disable-cpu-manager.png differ diff --git a/static/img/v1.4/cpu-pinning-hv/enable-cpu-manager.png b/static/img/v1.4/cpu-pinning-hv/enable-cpu-manager.png new file mode 100644 index 0000000..f90f134 Binary files /dev/null and b/static/img/v1.4/cpu-pinning-hv/enable-cpu-manager.png differ diff --git a/static/img/v1.4/cpu-pinning-hv/vm-advanced-options.png b/static/img/v1.4/cpu-pinning-hv/vm-advanced-options.png new file mode 100644 index 0000000..ab8e7ac Binary files /dev/null and b/static/img/v1.4/cpu-pinning-hv/vm-advanced-options.png differ diff --git a/static/img/v1.6/cpu-memory-hotplug-hv/edit-cpu-and-memory.png b/static/img/v1.6/cpu-memory-hotplug-hv/edit-cpu-and-memory.png new file mode 100644 index 0000000..82c7432 Binary files /dev/null and b/static/img/v1.6/cpu-memory-hotplug-hv/edit-cpu-and-memory.png differ diff --git a/static/img/v1.6/cpu-memory-hotplug-hv/edit-max-hotplug-ratio.png b/static/img/v1.6/cpu-memory-hotplug-hv/edit-max-hotplug-ratio.png new file mode 100644 index 0000000..1fc53ef Binary files /dev/null and b/static/img/v1.6/cpu-memory-hotplug-hv/edit-max-hotplug-ratio.png differ diff --git a/static/img/v1.6/cpu-memory-hotplug-hv/enable-cpu-and-memory-hotplug.png b/static/img/v1.6/cpu-memory-hotplug-hv/enable-cpu-and-memory-hotplug.png new file mode 100644 index 0000000..8919a5c Binary files /dev/null and b/static/img/v1.6/cpu-memory-hotplug-hv/enable-cpu-and-memory-hotplug.png differ diff --git a/versioned_docs/version-v1.6/vm/access-to-the-vm.md b/versioned_docs/version-v1.6/vm/access-to-the-vm.md index 22763a3..9d61970 100644 --- a/versioned_docs/version-v1.6/vm/access-to-the-vm.md +++ b/versioned_docs/version-v1.6/vm/access-to-the-vm.md @@ -3,39 +3,39 @@ sidebar_position: 5 sidebar_label: Access to the Virtual Machine title: "Access to the Virtual Machine" keywords: - - Harvester + - Hypervisor - harvester - Rancher - rancher - Access to the VM -description: Once the VM is up and running, it can be accessed using either VNC or the serial console from the Harvester UI. +description: Once the VM is up and running, it can be accessed using either VNC or the serial console from the Hypervisor UI. --- -Once the VM is up and running, you can access it using either the Virtual Network Computing (VNC) client or the serial console from the Harvester UI. +Once the VM is up and running, you can access it using either the Virtual Network Computing (VNC) client or the serial console from the Hypervisor UI. Additionally, you can connect directly from your computer's SSH client. -## Access with the Harvester UI +## Access with the Hypervisor UI VMs can be accessed from the UI directly using either VNC or the serial console. If the VGA display is not enabled on the VM, e.g., the `Ubuntu-Minimal-Cloud` image, the VM can only be accessed with the serial console. -![](/img/v1.2/vm/access-to-vm.png) +![](/img/v1.2/vm-hv/access-to-vm.png) ## SSH Access -Harvester provides two ways to inject SSH public keys into virtual machines. Generally, these methods fall into two categories. [Static key injection](#static-ssh-key-injection-via-cloud-init), which places keys in the cloud-init script when the virtual machine is first powered on; [dynamic injection](#dynamic-ssh-key-injection-via-qemu-guest-agent), which allows keys or basic auth to be updated dynamically at runtime. +Hypervisor provides two ways to inject SSH public keys into virtual machines. Generally, these methods fall into two categories. [Static key injection](#static-ssh-key-injection-via-cloud-init), which places keys in the cloud-init script when the virtual machine is first powered on; [dynamic injection](#dynamic-ssh-key-injection-via-qemu-guest-agent), which allows keys or basic auth to be updated dynamically at runtime. ### Static SSH Key Injection via cloud-init You can provide ssh keys to your virtual machines during the creation time on the `Basics` tab. Additionally, you can place the public ssh keys into your cloud-init script to allow it to take place. -![](/img/v1.2/vm/vm-ssh-keys.png) +![](/img/v1.2/vm-hv/vm-ssh-keys.png) #### Example of SSH key cloud-init configuration: ```yaml @@ -49,7 +49,7 @@ ssh_authorized_keys: _Available as of v1.0.1_ -Harvester supports dynamically injecting public ssh keys at run time through the use of the [qemu guest agent](https://wiki.qemu.org/Features/GuestAgent). This is achieved through the `qemuGuestAgent` propagation method. +Hypervisor supports dynamically injecting public ssh keys at run time through the use of the [qemu guest agent](https://wiki.qemu.org/Features/GuestAgent). This is achieved through the `qemuGuestAgent` propagation method. :::note @@ -59,7 +59,7 @@ When using `qemuGuestAgent` propagation, the `/home/$USER/.ssh/authorized_keys` ::: -You can inject your access credentials via the Harvester dashboard as below: +You can inject your access credentials via the Hypervisor dashboard as below: 1. Select the VM and click `⋮` button. 2. Click the `Edit Config` button and go to the `Access Credentials` tab. @@ -73,7 +73,7 @@ You need to enter the VM to edit password or remove SSH-Key after deleting the c ::: -![](/img/v1.2/vm/vm-add-access-credentails.png) +![](/img/v1.2/vm-hv/vm-add-access-credentails.png) diff --git a/versioned_docs/version-v1.6/vm/backup-restore.md b/versioned_docs/version-v1.6/vm/backup-restore.md index 13164ea..09e8daf 100644 --- a/versioned_docs/version-v1.6/vm/backup-restore.md +++ b/versioned_docs/version-v1.6/vm/backup-restore.md @@ -3,7 +3,7 @@ sidebar_position: 6 sidebar_label: VM Backup, Snapshot & Restore title: "VM Backup, Snapshot & Restore" keywords: - - Harvester + - Hypervisor - harvester - Rancher - rancher @@ -20,26 +20,26 @@ description: VM backups are created from the Virtual Machines page. The VM backu _Available as of v0.3.0_ VM backups are created from the **Virtual Machines** page. The VM backup volumes will be stored in the **Backup Target** (an NFS or S3 server), and they can be used to either restore a new VM or replace an existing VM. -![vm-backup.png](/img/v1.2/vm/vm-backup.png) +![vm-backup.png](/img/v1.2/vm-hv/vm-backup.png) :::note A backup target must be set up. For more information, see [Configure Backup Target](#configure-backup-target). If the backup target has not been set, you’ll be prompted with a message to do so. -Backup support is currently limited to Longhorn V1 Data Engine volumes. Harvester is unable to create backups of volumes in external storage. +Backup support is currently limited to Longhorn V1 Data Engine volumes. Hypervisor is unable to create backups of volumes in external storage. ::: ### Configure Backup Target -A backup target is an endpoint used to access a backup store in Harvester. A backup store is an NFS server or S3 compatible server that stores the backups of VM volumes. The backup target can be set at `Settings > backup-target`. +A backup target is an endpoint used to access a backup store in Hypervisor. A backup store is an NFS server or S3 compatible server that stores the backups of VM volumes. The backup target can be set at `Settings > backup-target`. The following table outlines the parameters that are common to all backup targets. | Parameter | Type | Description | | :--------------- | :------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | string | Type of server that stores the backups of volumes used by virtual machines. You can select either `NFS` or `S3`. | -| Refresh Interval | integer | Number of seconds that Harvester waits before syncing backups with the backupstore. When the value is `0`, backups are synced only if all backup volumes are in the `Ready` state. | +| Refresh Interval | integer | Number of seconds that Hypervisor waits before syncing backups with the backupstore. When the value is `0`, backups are synced only if all backup volumes are in the `Ready` state. | @@ -54,7 +54,7 @@ The following table outlines the parameters that are common to all backup target | Certificate | string | Self-signed SSL certificate of the S3 server | | VirtualHostedStyle | boolean | Option to use virtual-hosted–style URLs, wherein the bucket name is part of the domain name in the URL (`bucket.example.com`) | -![backuptarget-s3.png](/img/backuptarget-s3.png) +![backuptarget-s3.png](/img/v1.2/vm-hv/backuptarget-s3.png) @@ -63,7 +63,7 @@ The following table outlines the parameters that are common to all backup target | :----------------- | :----- | :----------------------------------------------------------------------------------------------------------------------------------------- | | Endpoint | string | URL of the [NFS server](https://longhorn.io/docs/1.8.0/snapshots-and-backups/backup-and-restore/set-backup-target/#set-up-nfs-backupstore) | -![backuptarget-nfs.png](/img/backuptarget-nfs.png) +![backuptarget-nfs.png](/img/v1.2/vm-hv/backuptarget-nfs.png) @@ -73,13 +73,13 @@ The following table outlines the parameters that are common to all backup target 1. Once the backup target is set, go to the `Virtual Machines` page. 1. Click `Take Backup` of the VM actions to create a new VM backup. 1. Set a custom backup name and click `Create` to create a new VM backup. -![create-backup.png](/img/v1.2/vm/create-backup.png) +![create-backup.png](/img/v1.2/vm-hv/create-backup.png) **Result:** The backup is created. You will receive a notification message, and you can also go to the `Backup & Snapshot > VM Backups` page to view all VM backups. The `State` will be set to `Ready` once the backup is complete. -![vm-backup-results.png](/img/v1.2/vm/vm-backup-results.png) +![vm-backup-results.png](/img/v1.2/vm-hv/vm-backup-results.png) Users can either restore a new VM or replace an existing VM using this backup. @@ -109,7 +109,7 @@ To restore a new VM from a backup, follow these steps: 1. Click the `Restore Backup` button at the top right. 1. Specify the new VM name and click `Create`. 1. A new VM will be restored using the backup volumes and metadata, and you can access it from the `Virtual Machines` page. -![restore-vm.png](/img/v1.2/vm/restore-vm.png) +![restore-vm.png](/img/v1.2/vm-hv/restore-vm.png) ### Replace an existing VM using a backup @@ -123,9 +123,9 @@ You can choose to either delete or retain the previous volumes. By default, all 1. Click the `Restore Backup` button at the top right. 1. Click `Replace Existing`. 1. You can view the restore process from the `Virtual Machines` page. -![vm-restore-existing.png](/img/v1.2/vm/vm-restore-existing.png) +![vm-restore-existing.png](/img/v1.2/vm-hv/vm-restore-existing.png) -### Restore a new VM on another Harvester cluster +### Restore a new VM on another Hypervisor cluster _Available as of v1.0.0_ @@ -141,7 +141,7 @@ Users can now restore a new VM on another cluster by leveraging the VM metadata 1. Download the virtual machine image from the existing cluster. - ![vm-snapshot.png](/img/v1.5/vm/download-vm-image.png) + ![vm-snapshot.png](/img/v1.2/vm-hv/download-vm-image.png) 1. Decompress the downloaded image. ``` @@ -184,7 +184,7 @@ Users can now restore a new VM on another cluster by leveraging the VM metadata ``` :::info important - Harvester can restore virtual machines only if the image name and configuration on both old and new clusters are identical. + Hypervisor can restore virtual machines only if the image name and configuration on both old and new clusters are identical. ::: @@ -200,20 +200,20 @@ Users can now restore a new VM on another cluster by leveraging the VM metadata _Available as of v1.1.0_ VM snapshots are created from the **Virtual Machines** page. The VM snapshot volumes will be stored in the cluster, and they can be used to either restore a new VM or replace an existing VM. -![vm-snapshot.png](/img/v1.2/vm/vm-snapshot.png) +![vm-snapshot.png](/img/v1.2/vm-hv/vm-snapshot.png) ### Create a VM snapshot 1. Go to the `Virtual Machines` page. 1. Click `Take VM Snapshot` of the VM actions to create a new VM snapshot. 1. Set a custom snapshot name and click `Create` to create a new VM snapshot. -![create-snapshot.png](/img/v1.2/vm/create-snapshot.png) +![create-snapshot.png](/img/v1.2/vm-hv/create-snapshot.png) **Result:** The snapshot is created. You can also go to the `Backup & Snapshot > VM Snapshots` page to view all VM snapshots. The `State` will be set to `Ready` once the snapshot is complete. -![vm-snapshot-results.png](/img/v1.2/vm/vm-snapshot-results.png) +![vm-snapshot-results.png](/img/v1.2/vm-hv/vm-snapshot-results.png) Users can either restore a new VM or replace an existing VM using this snapshot. @@ -249,7 +249,7 @@ To restore a new VM from a snapshot, follow these steps: 1. Click the `Restore Snapshot` button at the top right. 1. Specify the new VM name and click `Create`. 1. A new VM will be restored using the snapshot volumes and metadata, and you can access it from the `Virtual Machines` page. -![restore-vm-snapshot.png](/img/v1.2/vm/restore-vm-snapshot.png) +![restore-vm-snapshot.png](/img/v1.2/vm-hv/restore-vm-snapshot.png) ### Replace an existing VM using a snapshot @@ -279,15 +279,15 @@ Volumes consume extra disk space in the cluster whenever you create a new virtua 1. Locate the target namespace, and then select **⋮ > Edit Quota**. - ![edit-quota-namespace.png](/img/v1.4/vm/edit-quota-namespace.png) + ![edit-quota-namespace.png](/img/v1.2/vm-hv/edit-quota-namespace.png) 1. Specify the maximum amount of disk space that can be consumed by all snapshots in the namespace, and then and click **Save**. - ![edit-quota-namespace-save.png](/img/v1.4/vm/edit-quota-namespace-save.png) + ![edit-quota-namespace-save.png](/img/v1.2/vm-hv/edit-quota-namespace-save.png) 1. Verify that the configured value is displayed on the **Namespaces** screen. - ![edit-quota-namespace-read.png](/img/v1.4/vm/edit-quota-namespace-read.png) + ![edit-quota-namespace-read.png](/img/v1.2/vm-hv/edit-quota-namespace-read.png) ### Configure the Snapshot Space Usage Limit at the Virtual Machine Level @@ -295,25 +295,25 @@ Volumes consume extra disk space in the cluster whenever you create a new virtua 1. Locate the target virtual machine, and then select **⋮ > Edit VM Quota**. - ![edit-quota-vm.png](/img/v1.4/vm/edit-quota-vm.png) + ![edit-quota-vm.png](/img/v1.2/vm-hv/edit-quota-vm.png) 1. Specify the maximum total amount of disk space that can be consumed by all snapshots for the virtual machine, and then and click **Save**. - ![edit-quota-vm-save.png](/img/v1.4/vm/edit-quota-vm-save.png) + ![edit-quota-vm-save.png](/img/v1.2/vm-hv/edit-quota-vm-save.png) 1. Verify that the configured value is displayed on the **Quotas** tab of the virtual machine details screen. - ![edit-quota-vm-read.png](/img/v1.4/vm/edit-quota-vm-read.png) + ![edit-quota-vm-read.png](/img/v1.2/vm-hv/edit-quota-vm-read.png) ## Filesystem Freeze for Virtual Machine Backups and Snapshots -When a guest virtual machine is connected with the **QEMU Guest Agent**, the Harvester controller performs filesystem freeze operations through Kubevirt's [virt-freezer](https://github.com/kubevirt/kubevirt/blob/main/docs/freeze.md#virt-freezer) application to ensure filesystem consistency during virtual machine backups and snapshots. +When a guest virtual machine is connected with the **QEMU Guest Agent**, the Hypervisor controller performs filesystem freeze operations through Kubevirt's [virt-freezer](https://github.com/kubevirt/kubevirt/blob/main/docs/freeze.md#virt-freezer) application to ensure filesystem consistency during virtual machine backups and snapshots. This feature is particularly valuable for virtual machines with high I/O activity or critical data that requires point-in-time consistency guarantees. ### Prerequisites -Filesystem freeze and thaw functionality depends on virtual machine configuration, which is _not controlled by Harvester_. You must ensure that virtual machines are configured correctly and support the required libvirt commands. +Filesystem freeze and thaw functionality depends on virtual machine configuration, which is _not controlled by Hypervisor_. You must ensure that virtual machines are configured correctly and support the required libvirt commands. - **Red Hat Enterprise Linux (RHEL)** and **SUSE Linux Enterprise (SLE) Micro**: These systems may lack sufficient permissions for filesystem freeze operations by default. You may be required to create custom SELinux policies. - **Windows**: Filesystem freeze operations are available on these systems only when the Volume Shadow Copy Service (VSS) service is enabled. @@ -357,7 +357,7 @@ To verify that your virtual machine supports filesystem freeze operations, perfo A `Failed to freeze filesystem` error may cause backup or snapshot failures on some Linux distributions. -![fs-freeze-fail.png](/img/fs-freeze-fail.png) +![fs-freeze-fail.png](/img/v1.2/vm-hv/fs-freeze-fail.png) This issue typically occurs when SELinux denies read access to the QEMU Guest Agent (`qemu-ga`). You can verify the cause using the following steps: @@ -407,17 +407,17 @@ virt-freezer --unfreeze --namespace --name _Available as of v1.4.0_ -Harvester supports the creation of virtual machine backups and snapshots on a scheduled basis, with the option to retain a specific number of backups and snapshots. You can suspend, resume, and update the schedule at runtime. +Hypervisor supports the creation of virtual machine backups and snapshots on a scheduled basis, with the option to retain a specific number of backups and snapshots. You can suspend, resume, and update the schedule at runtime. ### Create the Virtual Machine Schedule 1. Go to the **Virtual Machine Schedules** screen, and then click **Create Schedule**. - ![create-schedule.png](/img/v1.4/vm/create-schedule.png) + ![create-schedule.png](/img/v1.2/vm-hv/create-schadule.png) 2. Configure the following settings: - ![configure-schedule.png](/img/v1.4/vm/configure-schedule.png) + ![configure-schedule.png](/img/v1.2/vm-hv/configure-schedule.png) - **Type**: Select either **Backup** or **Snapshot**. @@ -435,11 +435,11 @@ Harvester supports the creation of virtual machine backups and snapshots on a sc - **Retain**: Specify the number of up-to-date backups or snapshots to be retained. - When this value is exceeded, the Harvester controller deletes the oldest backups or snapshots, and Longhorn starts the snapshot purge. + When this value is exceeded, the Hypervisor controller deletes the oldest backups or snapshots, and Longhorn starts the snapshot purge. - **Max Failure**: Specify the maximum number of consecutive failed backup or snapshot creation attempts to be allowed. - When this value is exceeded, the Harvester controller suspends the schedule. + When this value is exceeded, the Hypervisor controller suspends the schedule. 3. Click **Create**. @@ -451,11 +451,11 @@ Harvester supports the creation of virtual machine backups and snapshots on a sc 1. On the **Basics** tab, verify that the settings are correct. - ![check-schedule-basic.png](/img/v1.4/vm/check-schedule-basic.png) + ![check-schedule-basic.png](/img/v1.2/vm-hv/check-schadule-basic.png) 1. On the **Backups** tab, check the status of the backups or snapshots that were created according to the schedule. - ![check-schedule-backups.png](/img/v1.4/vm/check-schedule-backups.png) + ![check-schedule-backups.png](/img/v1.2/vm-hv/check-schadule-backups.png) Backups and snapshots that are marked **Ready** can be used to restore the source virtual machine. For more information, see [VM Backup & Restore](#vm-backup--restore) and [VM Snapshot & Restore](#vm-snapshot--restore). @@ -467,11 +467,11 @@ Harvester supports the creation of virtual machine backups and snapshots on a sc 1. Locate the target schedule, and then select **⋮ > Edit Config**. - ![edit-schedule-config.png](/img/v1.4/vm/edit-schedule-config.png) + ![edit-schedule-config.png](/img/v1.2/vm-hv/edit-schedule-config.png) 1. Edit the **Cron Schedule**, **Retain**, or **Max Failure** values. - ![edit-schedule-parameters.png](/img/v1.4/vm/edit-schedule-parameters.png) + ![edit-schedule-parameters.png](/img/v1.2/vm-hv/edit-schedule-parameters.png) 1. Click **Save** to apply the changes. @@ -483,11 +483,11 @@ You can suspend active schedules and resume suspended schedules. 1. Locate the target schedule, and then select **⋮ > Suspend or Resume**. - ![suspend-resume-schedule.png](/img/v1.4/vm/suspend-resume-schedule.png) + ![suspend-resume-schedule.png](/img/v1.2/vm-hv/suspend-resume-schedule.png) The schedule is automatically suspended when the number of consecutive failed backup or snapshot creation attempts exceeds the **Max Failure** value. - Harvester does not allow you to resume a suspended schedule for backup creation if the backup target is not reachable. + Hypervisor does not allow you to resume a suspended schedule for backup creation if the backup target is not reachable. :::note @@ -495,9 +495,9 @@ You can suspend active schedules and resume suspended schedules. ::: -### Virtual Machine Operations and Harvester Upgrades + diff --git a/versioned_docs/version-v1.6/vm/clone-vm.md b/versioned_docs/version-v1.6/vm/clone-vm.md index d4b353c..02b4742 100644 --- a/versioned_docs/version-v1.6/vm/clone-vm.md +++ b/versioned_docs/version-v1.6/vm/clone-vm.md @@ -3,7 +3,7 @@ sidebar_position: 10 sidebar_label: Clone VM title: "Clone VM" keywords: - - Harvester + - Hypervisor - harvester - Rancher - rancher @@ -23,7 +23,7 @@ VM can be cloned with/without data. This function doesn't need to take a VM snap 1. On the `Virtual Machines` page, click `Clone` of the VM actions. 1. Set a new VM name and click `Create` to create a new VM. -![clone-vm-with-data.png](/img/v1.2/vm/clone-vm-with-data.png) +![clone-vm-with-data.png](/img/v1.2/vm-hv/clone-vm-with-data.png) ## Clone VM without volume data @@ -32,4 +32,4 @@ Cloning a VM without volume data creates a new VM with the same configuration as 1. On the `Virtual Machines` page, click `Clone` of the VM actions. 1. Unclick the `clone volume data` checkbox. 1. Set a new VM name and click `Create` to create a new VM. -![clone-vm-without-data.png](/img/v1.2/vm/clone-vm-without-data.png) +![clone-vm-without-data.png](/img/v1.2/vm-hv/clone-vm-without-data.png) diff --git a/versioned_docs/version-v1.6/vm/cpu-memory-hotplug.md b/versioned_docs/version-v1.6/vm/cpu-memory-hotplug.md index c7a6b70..ff9098c 100644 --- a/versioned_docs/version-v1.6/vm/cpu-memory-hotplug.md +++ b/versioned_docs/version-v1.6/vm/cpu-memory-hotplug.md @@ -3,7 +3,7 @@ sidebar_position: 12 sidebar_label: CPU and Memory Hotplug title: "CPU and Memory Hotplug" keywords: - - Harvester + - Hypervisor - harvester - Virtual Machine - virtual machine @@ -30,17 +30,17 @@ ARM64 architecture only supports memory hotplug. CPU hotplug operations require ::: -Harvester supports CPU and memory hotplug for virtual machines. This feature allows you to increase the CPU and memory resources of a running virtual machine without requiring a reboot. +Hypervisor supports CPU and memory hotplug for virtual machines. This feature allows you to increase the CPU and memory resources of a running virtual machine without requiring a reboot. ## Enable CPU and Memory Hotplug During Virtual Machine Creation 1. On the **Virtual Machine:Create** screen, specify the number of CPU cores and memory to be allocated. - ![Enable CPU and Memory Hotplug](/img/v1.6/cpu-memory-hotplug/enable-cpu-and-memory-hotplug.png) + ![Enable CPU and Memory Hotplug](/img/v1.6/cpu-memory-hotplug-hv/enable-cpu-and-memory-hotplug.png) 1. Select **Enable CPU and memory hotplug**. - Harvester automatically populates the **Maximum CPU** and **Maximum Memory** fields based on the `max-hotplug-ratio` setting. These values represent the maximum amount of CPU and memory resources that are available to the virtual machine during runtime. You can change these values, if necessary. + Hypervisor automatically populates the **Maximum CPU** and **Maximum Memory** fields based on the `max-hotplug-ratio` setting. These values represent the maximum amount of CPU and memory resources that are available to the virtual machine during runtime. You can change these values, if necessary. 1. Complete the rest of the virtual machine creation steps. @@ -48,9 +48,9 @@ Harvester supports CPU and memory hotplug for virtual machines. This feature all After the virtual machine is created, you can dynamically add CPU and memory resources using the **Edit CPU and Memory** button. -![Edit CPU and Memory](/img/v1.6/cpu-memory-hotplug/edit-cpu-and-memory.png) +![Edit CPU and Memory](/img/v1.6/cpu-memory-hotplug-hv/edit-cpu-and-memory.png) -Once you click **Apply**, Harvester [migrates the virtual machine](./live-migration.md#prerequisites) to a node with the configured CPU and memory amounts. +Once you click **Apply**, Hypervisor [migrates the virtual machine](./live-migration.md#prerequisites) to a node with the configured CPU and memory amounts. :::note @@ -75,4 +75,4 @@ The `max-hotplug-ratio` is set to `4`. | CPU cores | `1` | `4` | | Memory (Gi) | `2` | `8` | -![Edit max-hotplug-ratio](/img/v1.6/cpu-memory-hotplug/edit-max-hotplug-ratio.png) +![Edit max-hotplug-ratio](/img/v1.6/cpu-memory-hotplug-hv/edit-max-hotplug-ratio.png) diff --git a/versioned_docs/version-v1.6/vm/cpu-pinning.md b/versioned_docs/version-v1.6/vm/cpu-pinning.md index 53c9763..c102ce0 100644 --- a/versioned_docs/version-v1.6/vm/cpu-pinning.md +++ b/versioned_docs/version-v1.6/vm/cpu-pinning.md @@ -3,7 +3,7 @@ sidebar_position: 11 sidebar_label: CPU Pinning title: "CPU Pinning" keywords: - - Harvester + - Hypervisor - harvester - Virtual Machine - virtual machine @@ -24,20 +24,20 @@ description: Create VM with CPU pinning _Available as of v1.4.0_ -Harvester supports VM CPU pinning. To use this feature, you must first enable the CPU Manager on the nodes, and then enable CPU pinning when you create the VM. +Hypervisor supports VM CPU pinning. To use this feature, you must first enable the CPU Manager on the nodes, and then enable CPU pinning when you create the VM. ## Kubernetes CPU Manager The [CPU Manager](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/) feature improves CPU resource allocation in Kubernetes clusters, ensuring that workloads with strict performance needs receive stable and predictable CPU resources. This is especially important for high-performance and latency-sensitive applications. -Harvester uses the `static` CPU Manager policy when the CPU Manager is enabled. This policy manages a shared pool of CPUs that initially includes all CPUs on nodes with the following configuration: +Hypervisor uses the `static` CPU Manager policy when the CPU Manager is enabled. This policy manages a shared pool of CPUs that initially includes all CPUs on nodes with the following configuration: - Pods in the [`Guaranteed`](https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#guaranteed) quality of service (QoS) class that request whole CPU cores (for example, CPU: "2") are assigned dedicated CPUs. These CPUs are "pinned" to the pod and are removed from the shared CPU pool. - Pods in the [`Burstable`](https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#burstable) and [`BestEffort`](https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#besteffort) QoS classes share the remaining CPUs in the shared pool. ### Calculation of Shared CPU Pool -Harvester reserves CPU resources for system-level operations based on the [GKE formula](https://cloud.google.com/kubernetes-engine/docs/concepts/plan-node-sizes#cpu_reservations), with the [`systemReserved`](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved) and [`kubeReserved`](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#kube-reserved) values allocated in a 2:3 ratio. +Hypervisor reserves CPU resources for system-level operations based on the [GKE formula](https://cloud.google.com/kubernetes-engine/docs/concepts/plan-node-sizes#cpu_reservations), with the [`systemReserved`](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved) and [`kubeReserved`](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#kube-reserved) values allocated in a 2:3 ratio. Example (node with 16 CPU cores): ``` @@ -50,18 +50,18 @@ When a VM (pod) in the Guaranteed QoS class requests 4 CPUs, 4 cores are dedicat ## Enable and Disable CPU Manager -When you enable the CPU Manager, Harvester sets the CPU Manager policy to `static`. When you disable the feature, Harvester switches the CPU Manager policy back to `none`. +When you enable the CPU Manager, Hypervisor sets the CPU Manager policy to `static`. When you disable the feature, Hypervisor switches the CPU Manager policy back to `none`. You must enable or disable the CPU Manager on each node separately. -1. On the Harvester UI, go to **Hosts**. +1. On the Hypervisor UI, go to **Hosts**. 1. Locate the node in the list, and then select **⋮** > **Enable CPU Manager** or **Disable CPU Manager**. -Allow some time for Harvester to apply the corresponding CPU Manager policy. +Allow some time for Hypervisor to apply the corresponding CPU Manager policy. -![enable-cpu-manager](/img/v1.4/cpu-pinning/enable-cpu-manager.png) -![disable-cpu-manager](/img/v1.4/cpu-pinning/disable-cpu-manager.png) +![enable-cpu-manager](/img/v1.4/cpu-pinning-hv/enable-cpu-manager.png) +![disable-cpu-manager](/img/v1.4/cpu-pinning-hv/disable-cpu-manager.png) ### Limitations @@ -85,11 +85,11 @@ Allow some time for Harvester to apply the corresponding CPU Manager policy. 1. Click **Create**. - ![create-vm](/img/v1.4/cpu-pinning/create-vm.png) + ![create-vm](/img/v1.4/cpu-pinning-hv/create-vm.png) 1. On the **Advanced Options** tab, select **Enable CPU Pinning**. - ![vm-advanced-options](/img/v1.4/cpu-pinning/vm-advanced-options.png) + ![vm-advanced-options](/img/v1.4/cpu-pinning-hv/vm-advanced-options.png) 1. Click **Save**. @@ -109,4 +109,4 @@ VMs with CPU pinning enabled can be migrated only if the CPU Manager is enabled ## Upgrades -When upgrading a node, Harvester drains all pods and live migrates VMs to another node. To avoid interruptions to the upgrade process, ensure that the CPU Manager is enabled on other nodes and sufficient resources are available whenever you use VMs with CPU pinning enabled. +When upgrading a node, Hypervisor drains all pods and live migrates VMs to another node. To avoid interruptions to the upgrade process, ensure that the CPU Manager is enabled on other nodes and sufficient resources are available whenever you use VMs with CPU pinning enabled. diff --git a/versioned_docs/version-v1.6/vm/create-vm.md b/versioned_docs/version-v1.6/vm/create-vm.md index b9c2ee7..167c9c8 100644 --- a/versioned_docs/version-v1.6/vm/create-vm.md +++ b/versioned_docs/version-v1.6/vm/create-vm.md @@ -4,7 +4,7 @@ sidebar_position: 2 sidebar_label: Create a Virtual Machine title: "Create a Virtual Machine" keywords: - - Harvester + - Hypervisor - harvester - Rancher - rancher @@ -93,7 +93,7 @@ For more information, see the [API reference](../api/create-namespaced-virtual-m -To create a virtual machine using the [Harvester Terraform Provider](https://registry.terraform.io/providers/harvester/harvester/latest), +To create a virtual machine using the [Hypervisor Terraform Provider](https://registry.terraform.io/providers/harvester/harvester/latest), define a `harvester_virtualmachine` resource block: ```hcl diff --git a/versioned_docs/version-v1.6/vm/create-windows-vm.md b/versioned_docs/version-v1.6/vm/create-windows-vm.md index 7ccb365..603ff20 100644 --- a/versioned_docs/version-v1.6/vm/create-windows-vm.md +++ b/versioned_docs/version-v1.6/vm/create-windows-vm.md @@ -3,7 +3,7 @@ sidebar_position: 3 sidebar_label: Create a Windows Virtual Machine title: "Create a Windows Virtual Machine" keywords: - - Harvester + - Hypervisor - harvester - Rancher - rancher @@ -83,7 +83,7 @@ The `bootOrder` values need to be set with the installation image first. If you 1. The **Management Network** is added by default with the following values: 1. `Name`: The value `default` is set by default. You can keep it or change it. 2. `Model`: The value `e1000` is set by default. You can keep it or change it to the other available options from the dropdown. - 3. `Network`: The value `management Network` is set by default. You can't change this option if no other network has been created. See [Harvester Network](../networking/harvester-network.md) for the full description on how to create new networks. + 3. `Network`: The value `management Network` is set by default. You can't change this option if no other network has been created. See [Hypervisor Network](../networking/harvester-network.md) for the full description on how to create new networks. 4. `Type`: The value `masquerade` is set by default. You can keep it or change it to the other available option, `bridge`. 2. You can add additional networks by clicking `Add Network`. @@ -202,7 +202,7 @@ There is a known issue with Windows VM using Windows Server 2016 and above, a BS As a workaround, you can create or modify the file `/etc/modprobe.d/kvm.conf` within the installation of Hypervisor by updating `/oem/99_custom.yaml` like below: ```YAML -name: Harvester Configuration +name: Hypervisor Configuration stages: initramfs: - commands: # ... diff --git a/versioned_docs/version-v1.6/vm/edit-vm.md b/versioned_docs/version-v1.6/vm/edit-vm.md index 513544b..ccfee01 100644 --- a/versioned_docs/version-v1.6/vm/edit-vm.md +++ b/versioned_docs/version-v1.6/vm/edit-vm.md @@ -3,14 +3,14 @@ sidebar_position: 4 sidebar_label: Edit a Virtual Machine title: "Edit a Virtual Machine" keywords: - - Harvester + - Hypervisor - harvester - Rancher - rancher - Virtual Machine - virtual machine - Edit a VM -description: Edit Virtual Machines from the Harvester VM page. +description: Edit Virtual Machines from the Hypervisor VM page. --- diff --git a/versioned_docs/version-v1.6/vm/hotplug-volume.md b/versioned_docs/version-v1.6/vm/hotplug-volume.md index 6ad7daf..5f82a79 100644 --- a/versioned_docs/version-v1.6/vm/hotplug-volume.md +++ b/versioned_docs/version-v1.6/vm/hotplug-volume.md @@ -3,7 +3,7 @@ sidebar_position: 8 sidebar_label: Hot-Plug Volumes title: "Hot-Plug Volumes" keywords: - - Harvester + - Hypervisor - Hot-plug - Volume description: Adding hot-plug volumes to a running VM. @@ -13,7 +13,7 @@ description: Adding hot-plug volumes to a running VM. -Harvester supports adding hot-plug volumes to a running VM. +Hypervisor supports adding hot-plug volumes to a running VM. :::info @@ -28,9 +28,9 @@ The following steps assume that you have a running VM and a ready volume: 1. Go to the **Virtual Machines** page. 1. Find the VM that you want to add a volume to and select **⋮ > Add Volume**. - ![Add Volume Button](/img/v1.2/vm/add-volume-button.png) + ![Add Volume Button](/img/v1.2/vm-hv/add-volume-button.png) 1. Enter the **Name** and select the **Volume**. 1. Click **Apply**. - ![Add Volume Panel](/img/v1.2/vm/add-volume-panel.png) + ![Add Volume Panel](/img/v1.2/vm-hv/add-volume-panel.png) diff --git a/versioned_docs/version-v1.6/vm/resource-overcommit.md b/versioned_docs/version-v1.6/vm/resource-overcommit.md index 8cefd64..d273aa7 100644 --- a/versioned_docs/version-v1.6/vm/resource-overcommit.md +++ b/versioned_docs/version-v1.6/vm/resource-overcommit.md @@ -3,7 +3,7 @@ sidebar_position: 9 sidebar_label: Resource Overcommit title: "Resource Overcommit" keywords: - - Harvester + - Hypervisor - Overcommit - Overprovision - ballooning @@ -14,9 +14,9 @@ description: Overcommit resources to a VM. -Harvester supports global configuration of resource overload percentages on CPU, memory, and storage. By setting [`overcommit-config`](../advanced/settings.md#overcommit-config), this will allow scheduling of additional virtual machines even when physical resources are fully utilized. +Hypervisor supports global configuration of resource overload percentages on CPU, memory, and storage. By setting [`overcommit-config`](../advanced/settings.md#overcommit-config), this will allow scheduling of additional virtual machines even when physical resources are fully utilized. -Harvester allows you to overcommit CPU and RAM on compute nodes. This allows you to increase the number of instances running on your cloud at the cost of reducing the performance of the instances. The Compute service uses the following ratios by default: +Hypervisor allows you to overcommit CPU and RAM on compute nodes. This allows you to increase the number of instances running on your cloud at the cost of reducing the performance of the instances. The Compute service uses the following ratios by default: - CPU allocation ratio: 1600% - RAM allocation ratio: 150% @@ -34,24 +34,24 @@ Users can modify the global `overcommit-config` by following the steps below, an 1. Go to the **Advanced > Settings** page. - ![overcommit page](/img/v1.2/vm/overcommit-page.png) + ![overcommit page](/img/v1.2/vm-hv/overcommit-page.png) 1. Find the `overcommit-config` setting. 1. Configure the desired CPU, Memory, and Storage ratio. - ![overcommit panel](/img/v1.2/vm/overcommit-panel.png) + ![overcommit panel](/img/v1.2/vm-hv/overcommit-panel.png) ## Configure overcommit for a single virtual machine In situations where you require specific configurations for individual virtual machines without affecting the global settings, you can easily achieve this by modifying the `spec.template.spec.domain.resources.limits.` value on the corresponding virtual machine spec directly. -![vm overcommit config](/img/v1.2/vm/vm-overcommit-config.png) +![vm overcommit config](/img/v1.2/vm-hv/vm-overcommit-config.png) ## Reserve more memory for the system overhead -By default, the Harvester reserves a certain amount of system management overhead memory from the memory allocated for the virtual machine. In most cases, this will not cause any problems. However, some operating systems, such as Windows 2022, will request more memory than is reserved. +By default, the Hypervisor reserves a certain amount of system management overhead memory from the memory allocated for the virtual machine. In most cases, this will not cause any problems. However, some operating systems, such as Windows 2022, will request more memory than is reserved. -To address the issue, Harvester provides an annotation `harvesterhci.io/reservedMemory` on VirtualMachine custom resource to let you specify the amount of memory to reserve. For instance, add `harvesterhci.io/reservedMemory: 200Mi` if you decide to reserve 200 MiB for the system overhead of the VM. +To address the issue, Hypervisor provides an annotation `harvesterhci.io/reservedMemory` on VirtualMachine custom resource to let you specify the amount of memory to reserve. For instance, add `harvesterhci.io/reservedMemory: 200Mi` if you decide to reserve 200 MiB for the system overhead of the VM. ```diff apiVersion: kubevirt.io/v1 @@ -68,4 +68,4 @@ To address the issue, Harvester provides an annotation `harvesterhci.io/reserved ## Why my virtual machines are scheduled unevenly? -The scheduling of virtual machines depends on the underlying behavior of the kube-scheduler. We have a dedicated article explaining the details. If you would like to learn more, check out: [Harvester Knowledge Base: VM Scheduling](https://harvesterhci.io/kb/vm-scheduling/). +The scheduling of virtual machines depends on the underlying behavior of the kube-scheduler. We have a dedicated article explaining the details. If you would like to learn more, check out: [Hypervisor Knowledge Base: VM Scheduling](https://harvesterhci.io/kb/vm-scheduling/). diff --git a/versioned_docs/version-v1.6/vm/virtual-machines.md b/versioned_docs/version-v1.6/vm/virtual-machines.md index 319bb2c..f9543fe 100644 --- a/versioned_docs/version-v1.6/vm/virtual-machines.md +++ b/versioned_docs/version-v1.6/vm/virtual-machines.md @@ -7,7 +7,7 @@ keywords: - VM - guest operating system - guest OS -description: Information concerning virtual machines that run on top of the Harvester cluster +description: Information concerning virtual machines that run on top of the Hypervisor cluster --- @@ -16,15 +16,15 @@ description: Information concerning virtual machines that run on top of the Harv You can create [Linux VMs](../vm/create-vm.md) using one of the following methods: -- Harvester UI: On the **Virtual Machines** screen, click **Create** and configure the settings on each tab. +- Hypervisor UI: On the **Virtual Machines** screen, click **Create** and configure the settings on each tab. - Kubernetes API: Create a `VirtualMachine` object. -- [Harvester Terraform Provider](../terraform/terraform-provider.md): Define a `harvester_virtualmachine` resource block. +- [Hypervisor Terraform Provider](../terraform/terraform-provider.md): Define a `harvester_virtualmachine` resource block. -Creating [Windows VMs](../vm/create-windows-vm.md) on the Harvester UI involves slightly different steps. Harvester provides a VM template named `windows-iso-image-base-template` that adds a volume with the Virtio drivers for Windows, which streamlines the VM configuration process. If you require Virtio devices but choose to not use the template, you must add your own Virtio drivers for Windows to enable correct hardware detection. +Creating [Windows VMs](../vm/create-windows-vm.md) on the Hypervisor UI involves slightly different steps. Hypervisor provides a VM template named `windows-iso-image-base-template` that adds a volume with the Virtio drivers for Windows, which streamlines the VM configuration process. If you require Virtio devices but choose to not use the template, you must add your own Virtio drivers for Windows to enable correct hardware detection. ## Validated Guest Operating Systems -The following operating systems have been validated to run in Harvester virtual machines: +The following operating systems have been validated to run in Hypervisor virtual machines: - SUSE Linux Enterprise Micro 6.0 and 6.1 - SUSE Linux Enterprise Server 15 SP6 and 15 SP7 @@ -33,9 +33,9 @@ The following operating systems have been validated to run in Harvester virtual :::note -The list includes only tested operating systems and is not intended to be exhaustive. Other operating systems may also run in Harvester virtual machines. However, guest operating systems must match the architecture of the Harvester cluster's hosts. x86 virtual machines can run only on x86 clusters, and ARM virtual machines can run only on ARM clusters. +The list includes only tested operating systems and is not intended to be exhaustive. Other operating systems may also run in Hypervisor virtual machines. However, guest operating systems must match the architecture of the Hypervisor cluster's hosts. x86 virtual machines can run only on x86 clusters, and ARM virtual machines can run only on ARM clusters. -You are responsible for obtaining, activating, and managing licenses for any commercial software that you decide to use. Harvester cannot be held responsible for damage or loss of data that may occur through the use of untested, unpatched, and outdated operating systems. +You are responsible for obtaining, activating, and managing licenses for any commercial software that you decide to use. Hypervisor cannot be held responsible for damage or loss of data that may occur through the use of untested, unpatched, and outdated operating systems. The contents of this document may not reflect the most current situation and may change at any time without notice.