[
https://issues.apache.org/jira/browse/CLOUDSTACK-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516832#comment-14516832
]
ASF subversion and git services commented on CLOUDSTACK-8424:
-------------------------------------------------------------
Commit ea7fd37783cbc7ec78de5a5e84395381b1800a3e in cloudstack's branch
refs/heads/4.5 from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ea7fd37 ]
CLOUDSTACK-8424: Add cpu features if guest.cpu.features is set
This improvements checks for "guest.cpu.features" property which is a space
separated list of cpu features that is specific for a host. When added, it
will add <feature policy='require' name='{{feature-you-listed}}'/> in the
<cpu> section of the generated vm spec xml.
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> 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)
