[
https://issues.apache.org/jira/browse/CLOUDSTACK-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707936#comment-14707936
]
Remi Bergsma commented on CLOUDSTACK-8443:
------------------------------------------
Work-in-progress here:
https://github.com/remibergsma/cloudstack/commits/centos7-kvm
The cgroup stuff seems fixes. Will do more testing to be sure.
Remaining problem now:
{noformat}
2015-08-22 07:40:19,778 ERROR [cloud.agent.AgentShell] (main:null) Unable to
start agent:
com.cloud.utils.exception.CloudRuntimeException: Failed to connect socket to
'/var/run/libvirt/libvirt-sock': No such file or directory
{noformat}
While before adding the host to CloudStack this is available:
{noformat}
[root@kvm2 ~]# ls -la /var/run/libvirt/libvirt-sock
srwxrwxrwx. 1 root root 0 Aug 22 07:03 /var/run/libvirt/libvirt-sock
{noformat}
After adding:
{noformat}
[root@kvm2 ~]# ls -la /var/run/libvirt/libvirt-sock
ls: cannot access /var/run/libvirt/libvirt-sock: No such file or directory
{noformat}
Can be fixed by restarting libvirtd and then restarting agent:
{noformat}
[root@kvm2 ~]# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
{noformat}
It's back:
{noformat}
[root@kvm2 ~]# ls -la /var/run/libvirt/libvirt-sock
srwxrwxrwx. 1 root root 0 Aug 22 07:41 /var/run/libvirt/libvirt-sock
{noformat}
I restarted agent while Marvin was still waiting for the Agent to report back:
{noformat}
[root@kvm2 ~]# /etc/init.d/cloudstack-agent restart
Restarting cloudstack-agent (via systemctl): [ OK ]
[root@kvm2 ~]# less /var/log/cloudstack/agent/
{noformat}
After this it worked fine and the deployment succeeded.
Will digg into this deeper on Monday and make a solution.
> 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.6.0, 4.5.1
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> 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)
