Skip to content
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

Feature #3510: authorize “EMULATOR” in VM TEMPLATE #112

Merged

Conversation

baby-gnu
Copy link
Contributor

  • src/vm/VirtualMachine.cc (insert): Add “EMULATOR” to the list of
    VM attributes understood by opennebula.
  • src/vmm/LibVirtDriverKVM.cc (deployment_description_kvm): Get
    “EMULATOR” from VM template first, then from default and finally from
    hardcoded path.

Thanks Vladislav Gorbunov for the patch

* src/vm/VirtualMachine.cc (insert): Add “EMULATOR” to the list of
  VM attributes understood by opennebula.

* src/vmm/LibVirtDriverKVM.cc (deployment_description_kvm): Get
  “EMULATOR” from VM template first, then from default and finally from
  hardcoded path.

Thanks Vladislav Gorbunov for the patch
@rsmontero rsmontero merged commit f362e64 into OpenNebula:master Sep 13, 2016
@rsmontero
Copy link
Member

Merged thanks! Maybe we can expose this in Sunstone

@baby-gnu baby-gnu deleted the feature/handle-emulator-in-vm-template branch September 13, 2016 12:59
@baby-gnu
Copy link
Contributor Author

Merged thanks! Maybe we can expose this in Sunstone

In which case we should manage the ARCH accordingly.

rsmontero pushed a commit that referenced this pull request Jul 23, 2020
rsmontero pushed a commit that referenced this pull request Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants