[
https://issues.apache.org/jira/browse/CLOUDSTACK-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav updated CLOUDSTACK-8424:
------------------------------------
Description:
Right now, if we want to enable CPU features such as "vmx" on KVM guest vms,
there is no way to do that. The improvement is to add a flag in
agent.properties per host that is specific for a host using the property
"guest.cpu.features=vmx vme" where features are space separated. This will lead
to adding <feature policy='require' name='vmx'/> in the <cpu> section of the
created XML. This can be useful to start guest VMs that need vmx, the primary
purpose is to provision nested virtualized kvm hosts on a kvm host to test
CloudStack :)
was:
Right now, if we want to enable CPU features such as "vmx" on KVM guest vms,
there is no way to do that. The improvement is to add a flag in
agent.properties per host that is specific for a host;
> KVM: allow a way to add CPU flags/features specific to a host
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-8424
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8424
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.6.0, 4.5.1
>
>
> Right now, if we want to enable CPU features such as "vmx" on KVM guest vms,
> there is no way to do that. The improvement is to add a flag in
> agent.properties per host that is specific for a host using the property
> "guest.cpu.features=vmx vme" where features are space separated. This will
> lead to adding <feature policy='require' name='vmx'/> in the <cpu> section of
> the created XML. This can be useful to start guest VMs that need vmx, the
> primary purpose is to provision nested virtualized kvm hosts on a kvm host to
> test CloudStack :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
