cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8443) Support CentOS7 as KVM host
Date Tue, 05 May 2015 23:36:59 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529553#comment-14529553
] 

Marcus Sorensen commented on CLOUDSTACK-8443:
---------------------------------------------

My testing indicates we need to avoid this line from serviceConfig.py when setting up EL7
hypervisors :

            cfo.addEntry("cgroup_controllers", "[\"cpu\"]")



The cgroups are added automatically by systemd-machined, regardless of whether /etc/libvirt/qemu.conf
has this line or not. 

There's a seemingly separate bug in systemd-machined(or perhaps libvirt's interaction with
it) you may also notice that causes the cgroup cpu share setting to be reset on existing vms
when new vms start, but this setting has no effect on that. The issue is in the distro.

> 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
>            Priority: Critical
>
> 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)

Mime
View raw message