AlexanderKgr opened a new issue #5466:
URL: https://github.com/apache/cloudstack/issues/5466
<!--
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
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
CRITICAL
-->
~~~
CRITICAL - operation not possible
~~~
##### CLOUDSTACK VERSION
~~~
4.15.2.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Ubuntu server 18 with cloudstack 4.15.2.0
Hypervisor xcp-ng 8.2 with september security patch
Advanced networking
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Continuing from this issue
https://github.com/apache/cloudstack/issues/5204
Which is closed and this problem happening
After installation of 4.15.2.0, when creating a new instance there is an
option in advanced setting for bios or uefi - legacy, secure (btw - why there
is 2 options for uefi? on xen orchesra there are only bios and uefi)
When selecting bios everything is working perfect, even old vms from old
templates which had issues with 4.15.1.0. You can shutdown, boot again, reboot,
everything works as it should
When selectin uefi - both options (secure - legacy) the instance will boot
without issue on the 1st boot. But if you shutdown the instance and try to boot
it again there is issue. Without even touching something from settings. There
is an error that
"Unable to start a VM due to insufficient capacity"
and in the logs of cloudstack management there is something strange
I have selected uefi and secure and haven't touched the settings. I can
understand that it is trying to vm with bios boot option.
This happens even on old instances created with older versions of CS.
Instance will work the 1st time booting but if you shut it down cannot boot
anymore.
I think this is really critical.
##### 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 -->
~~~
1. Create new instance or boot an instance with option uefi.
2. shut it down.
3. Try to boot it and it won't boot anymore
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The instance to boot as the first time.
I underline that i haven't touched anything in instance settings.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Instance cannot boot
~~~
--
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]
