-
Notifications
You must be signed in to change notification settings - Fork 993
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
Fixes #37009 - Implement EFI for libvirt #9965
base: develop
Are you sure you want to change the base?
Conversation
By default this derives the firmware type from the PXE loader, just like VMware does. It does not yet implement secure boot.
@stejskalleos @nofaralfasi could you have a look at this and fog/fog-libvirt#134? |
<%= field(f, :firmware, :disabled => !new_vm, :label => _('Firmware'), :label_size => "col-md-2") do | ||
compute_resource.firmware_types.collect do |type, name| | ||
radio_button_f f, :firmware, {:disabled => !new_vm, :value => type, :text => _(name)} |
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.
Shouldn't it be:
<%= field(f, :firmware, :disabled => !new_vm, :label => _('Firmware'), :label_size => "col-md-2") do | |
compute_resource.firmware_types.collect do |type, name| | |
radio_button_f f, :firmware, {:disabled => !new_vm, :value => type, :text => _(name)} | |
<%= field(f, :os_firmware, :disabled => !new_vm, :label => _('Firmware'), :label_size => "col-md-2") do | |
compute_resource.firmware_types.collect do |type, name| | |
radio_button_f f, :os_firmware, {:disabled => !new_vm, :value => type, :text => _(name)} |
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.
No, the controller accepts firmware (just like the VMware side). The libvirt model then converts the option to what fog-libvirt accepts.
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.
Why do we need to consider VMware here? I don't see the necessity for VMware and Libvirt forms to have the same naming convention.
If we keep it as it is, we encounter the following error: Failure: undefined method firmware for <Fog::Libvirt::Compute::Server
...
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.
The checkbox only works when creating the VM. Once the VM is created, the checkbox remains unchecked.
I'm using OVMF, so I couldn't test the entire workflow.
This is a good point. I'm not sure if we actually support changing it, so perhaps we should hide the element on edit. During the review we also noticed that the VMware compute resource card shows the firmware type, which this should also implement. |
By default this derives the firmware type from the PXE loader, just like VMware does.
It does not yet implement secure boot.
Depends on fog/fog-libvirt#134 to be released.
Currently only tested via the API, not the UI.