Feature #3510
Allow to override EMULATOR attribute in VM template
| Status: | Closed | Start date: | 01/19/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0%  | |
| Category: | Core & System | |||
| Target version: | Release 5.2 | |||
| Resolution: | fixed | Pull request: | 
Description
This patch is allow to override EMULATOR attribute in VM template.
Associated revisions
Feature #3510: authorize “EMULATOR” in VM TEMPLATE (#112)
- 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
F #3510: Add EMULATOR to restricted attributes as default
History
#1
    
    Updated by Vladislav Gorbunov over 6 years ago
    Patch did not work. EMULATOR attribute in vm template ignored.
#2
    
    Updated by Vladislav Gorbunov over 6 years ago
    - File emulator_in_template.diff
 added 
Corrected patch uploaded here.
#3
    
    Updated by Ruben S. Montero over 6 years ago
    - Tracker changed from Feature to Request
 
Moving this to request, now being discussed in the dev mailing list
#4
    
    Updated by Daniel Dehennin almost 5 years ago
    +1
As requested on the forum.
I could run VMs for other architectures on my AMD64 hypervisor, which is a “must have” to port packages ;-)
Regards.
#5
    
    Updated by Daniel Dehennin almost 5 years ago
    I opened a pull request based on Vladislav patch with proper subject to be referenced by redmine.
Regards.
#6
    
    Updated by Ruben S. Montero almost 5 years ago
    - Tracker changed from Request to Feature
 - Category set to Core & System
 - Target version set to Release 5.2
 
#7
    
    Updated by Ruben S. Montero almost 5 years ago
    - Status changed from Pending to Closed
 - Resolution set to fixed