[
https://issues.apache.org/jira/browse/CLOUDSTACK-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709978#comment-14709978
]
ASF GitHub Bot commented on CLOUDSTACK-8443:
--------------------------------------------
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/731#issuecomment-134363088
@bhaisaab No worries, took me some time as well to understand how it is
supposed to work and I'm also still learning.
In the Jira issue you mention two issues. The first:
```
org.libvirt.LibvirtException: Controller 'cpuacct' is not wanted, but 'cpu'
is co-mounted: Invalid argument
```
This is due to the co-mount: both 'cpu' and 'cpuacct' are on one mount
point, and our previous config instructs it to use only 'cpu'. So, the
'cpuacct' is `not wanted` by our config. This was solved in my PR by relying on
the default.
The second issue:
```
unsupported configuration: CPU tuning is not available on this host
```
This issue also went away by updating the `libvirtd` config. When I look at
the Libvirt source
(https://github.com/virtualopensystems/libvirt/blob/master/src/qemu/qemu_cgroup.c#L635)
I see this error is thrown in qemu_cgroup.c I assume the
VIR_ERR_CONFIG_UNSUPPORTED aka `unsupported configuration` also has to do with
the rather weird cgroup config that we put there before but I don't know for
sure.
If you have some time, please give it a go. I'll also ask @wilderrodrigues
to review it.
> Support CentOS7 as KVM host
> ---------------------------
>
> Key: CLOUDSTACK-8443
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8443
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0, 4.5.1, 4.6.0
> Reporter: Rohit Yadav
> Assignee: Remi Bergsma
> Priority: Critical
> Fix For: 4.6.0
>
>
> CentOS7 as KVM host fails with exception:
> 2015-05-05 21:39:45,395{GMT} WARN [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-5:) LibvirtException
> org.libvirt.LibvirtException: Controller 'cpuacct' is not wanted, but 'cpu'
> is co-mounted: Invalid argument
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.domainCreateXML(Unknown Source)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1267)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3828)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1361)
> After umounting cpuacct (umount /sys/fs/cgroup/cpuacct), and restarting host,
> the exception seen is: (also seen after upgrading linux kernel to 4.0.1)
> 2015-05-05 21:40:15,875{GMT} WARN [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-5:) LibvirtException
> org.libvirt.LibvirtException: unsupported configuration: CPU tuning is not
> available on this host
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.domainCreateXML(Unknown Source)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1267)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
