-
Notifications
You must be signed in to change notification settings - Fork 124
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.
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
base: 4.20
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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: | ||||||
shwstppr marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| - 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: | ||||||
shwstppr marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| ``skip.force.disk.controller = true`` | ||||||
|
|
||||||
| When set, disk controller enforcement is skipped and the controllers defined by template/instance details are used. | ||||||
|
||||||
| 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?
There was a problem hiding this comment.
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.'"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.