Skip to content

doc: add new section for EFI/vTPM cloning, fix the out of date page in 1.8#1061

Open
pohanhuang wants to merge 1 commit into
harvester:mainfrom
pohanhuang:HARV-9182
Open

doc: add new section for EFI/vTPM cloning, fix the out of date page in 1.8#1061
pohanhuang wants to merge 1 commit into
harvester:mainfrom
pohanhuang:HARV-9182

Conversation

@pohanhuang

@pohanhuang pohanhuang commented Jun 17, 2026

Copy link
Copy Markdown

Problem:

  • vm clone page is out of date in v1.8
  • miss the EFI/vTPM cloning feature

Solution:

  • fix vm clone page is out of date in v1.8
  • add the EFI/vTPM cloning feature

Related Issue(s):

harvester/harvester#9182

Test plan:

Additional documentation or context

v1.8

v1 8

v1.9

v1 9 efi-cloning

Copilot AI review requested due to automatic review settings June 17, 2026 04:33
…n 1.8

Signed-off-by: pohanhuang <pohan.huang@suse.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the VM cloning documentation to reflect current UI behavior and documents EFI/vTPM persistent-state cloning behavior for the dev (v1.9) docs, while refreshing the v1.8 versioned page to remove outdated steps/screenshots.

Changes:

  • Refresh cloning steps to include run strategy selection and updated screenshots/wording.
  • Update v1.8 versioned clone doc screenshots from older /img/v1.2/... assets to /img/v1.8/....
  • Add a new “EFI and vTPM Persistent State” section to the current (v1.9 Dev) clone documentation.

Reviewed changes

Copilot reviewed 2 out of 5 changed files in this pull request and generated 5 comments.

File Description
versioned_docs/version-v1.8/vm/clone-vm.md Updates v1.8 clone steps and screenshots to match current v1.8 UI.
docs/vm/clone-vm.md Updates current (v1.9 Dev) clone steps and adds EFI/vTPM persistent-state cloning guidance.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/vm/clone-vm.md
Comment on lines 26 to +29
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)
2. Select a [run strategy](./create-vm.md#run-strategy). The cloned VM uses the source VM's run strategy by default.
3. Set a new VM name and click `Create` to create a new VM.
![clone-vm-with-data.png](/img/v1.8/vm/clone-vm-with-data.png)
Comment thread docs/vm/clone-vm.md
Comment on lines 35 to +39
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)
2. Clear the `clone volume data` checkbox.
3. Select a [run strategy](./create-vm.md#run-strategy). The cloned VM uses the source VM's run strategy by default.
4. Set a new VM name and click `Create` to create a new VM.
![clone-vm-without-data.png](/img/v1.8/vm/clone-vm-without-data.png)
Comment thread docs/vm/clone-vm.md

:::note

EFI and vTPM persistent state is stored separately from the volumes listed in `vm.Spec.Template.Spec.Volumes`. Harvester creates this storage only after the source VM has been started at least once. If the source VM has never been started, cloning a VM with EFI or vTPM persistent state can fail because the required source storage does not exist.
Comment on lines 26 to +29
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)
2. Select a [run strategy](./create-vm.md#run-strategy). The cloned VM uses the source VM's run strategy by default.
3. Set a new VM name and click `Create` to create a new VM.
![clone-vm-with-data.png](/img/v1.8/vm/clone-vm-with-data.png)
Comment on lines 35 to +39
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)
2. Clear the `clone volume data` checkbox.
3. Select a [run strategy](./create-vm.md#run-strategy). The cloned VM uses the source VM's run strategy by default.
4. Set a new VM name and click `Create` to create a new VM.
![clone-vm-without-data.png](/img/v1.8/vm/clone-vm-without-data.png)
@github-actions

Copy link
Copy Markdown
Name Link
🔨 Latest commit 362df8e
😎 Deploy Preview https://6a3225023594f0787c98a5a9--harvester-preview.netlify.app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants