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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
