vm: note on skip forced disk controllers uefi secure boot#616
vm: note on skip forced disk controllers uefi secure boot#616shwstppr wants to merge 1 commit intoapache:4.20from
Conversation
Related apache/cloudstack#11750 Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
|
@blueorangutan docbuild |
|
@shwstppr a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/616. (QA-JID 478) |
|
|
||
| **KVM** | ||
|
|
||
| Instances running on the KVM hypervisor with UEFI Secure Boot have disk controllers automatically enforced: |
There was a problem hiding this comment.
| 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: |
There was a problem hiding this comment.
| 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. |
There was a problem hiding this comment.
| 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.
@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.'"
|
|
||
| ``skip.force.disk.controller = true`` | ||
|
|
||
| When set, disk controller enforcement is skipped and the controllers defined by template/instance details are used. |
There was a problem hiding this comment.
@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.'"
4 participants
Related apache/cloudstack#11750
📚 Documentation preview 📚: https://cloudstack-documentation--616.org.readthedocs.build/en/616/