rastopato opened a new issue, #8734:
URL: https://github.com/apache/cloudstack/issues/8734
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VR
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced Networking, multiple templates with UEFI settings
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
RHEL 9.3
##### SUMMARY
<!-- Explain the problem/feature briefly -->
If I start a first instance on new guest network, then VR is created before
instance itself, as expected.
But when I create such an instance from Template which is setup for UEFI (no
matter if legacy or secure), than VR VM is created with firmware EFI and it
obviously cannot boot with such a setting. If I shutdown VR, change firmware to
BIOS (recommended) and start again, it boots normally.
Also when I create first instance with Template without UEFI, everything is
working as expected
Tried with multiple domains/users/templates/networks.....looks like UEFI
setting in template is the problem.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
Create Template with UEFI setting (no matter if Legacy or Secure). Create
instance from this template on new network, so new VR must be created
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
VR VM is created with firmware BIOS (under VM Settings -> VM Options -> Boot
Options) and boot up normally
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
VR VM is created with firmware EFI (under VM Settings -> VM Options -> Boot
Options) and it stuck on booting process.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
