We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
as noble now supports the efi bootloader we should make the following property configurable 'hyperVGeneration' => 'V1' or made default to V2
'hyperVGeneration' => 'V1'
https://github.com/cloudfoundry/bosh-azure-cpi-release/blob/master/src/bosh_azure_cpi/lib/cloud/azure/restapi/azure_client.rb#L1154
The text was updated successfully, but these errors were encountered:
Hi @ramonskie,
Yes to enable an efi boot on azure you have to generate an gen2 / hypervGeneration v2 image
efi
azure
gen2 / hypervGeneration v2 image
Docs: Azure generation-2 Hypervisor
Overall I think the efi / image generationshould be part of the Stemcell -> stemcell.MF - cloud_properties.
efi / image generation
Stemcell
stemcell.MF
cloud_properties
The image cloud_properties section is uploaded as meta data to the storage account where cpi can get all image information.
meta data
storage account
cpi
So we should first think of a new property that is part of the cloud_properties that could be used later by the cpi implementation.
Sorry, something went wrong.
No branches or pull requests
as noble now supports the efi bootloader
we should make the following property configurable
'hyperVGeneration' => 'V1'
or made default to V2https://github.com/cloudfoundry/bosh-azure-cpi-release/blob/master/src/bosh_azure_cpi/lib/cloud/azure/restapi/azure_client.rb#L1154
The text was updated successfully, but these errors were encountered: