Skip to content

vm: note on skip forced disk controllers uefi secure boot #616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shwstppr wants to merge 1 commit into
base: 4.20
Choose a base branch
from
Open

vm: note on skip forced disk controllers uefi secure boot #616

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions source/adminguide/virtual_machines.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,18 @@ To create an Instance from a Template:
specified at the Instance or Template level. For an existing Instance its settings can be updated while it is in
stopped state by admin.

**KVM**

Instances running on the KVM hypervisor with UEFI Secure Boot have disk controllers automatically enforced:
Copy link
Contributor

@sureshanaparti sureshanaparti Jan 8, 2026

Choose a reason for hiding this comment

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

Suggested change
Instances running on the KVM hypervisor with UEFI Secure Boot have disk controllers automatically enforced:
Instances running on the KVM hypervisor with UEFI Secure Boot have the following disk controllers automatically enforced:


- Windows OS instances use SATA
- Non-Windows OS instances use VirtIO

Starting with 4.20.3 and later, this behavior can be overridden by setting the following template or instance detail:
Copy link
Contributor

@sureshanaparti sureshanaparti Jan 8, 2026

Choose a reason for hiding this comment

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

Suggested change
Starting with 4.20.3 and later, this behavior can be overridden by setting the following template or instance detail:
Starting with 4.20.3 and later, this behavior can be overridden by setting the following template or instance detail to true:


``skip.force.disk.controller = true``

When set, disk controller enforcement is skipped and the controllers defined by template/instance details are used.
Copy link
Contributor

@sureshanaparti sureshanaparti Jan 8, 2026

Choose a reason for hiding this comment

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

Suggested change
When set, disk controller enforcement is skipped and the controllers defined by template/instance details are used.
When set to true, the disk controller enforcement is skipped and the controllers defined by template/instance details are used.

need to mention which detail takes priority?

Copy link

@RosiKyu RosiKyu Jan 9, 2026

Choose a reason for hiding this comment

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

@sureshanaparti ,@shwstppr - based on the test results so far, instance-level detail takes priority over template-level (standard CloudStack behavior). We can add: 'If set on both template and instance, the instance setting takes precedence.'"


Install Required Tools and Drivers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down