RE: [ACS4.1] cloudstack-agent

: dev@cloudstack.apache.org Subject: Re: [ACS4.1] cloudstack-agent On Mon, May 13, 2013 at 07:27:54AM +, Paul Angus wrote: > It's the same hardware as for the 4.0.2 build - it's scripted and only > difference is the repo used. > I've seen this happen when scripting my ins

Re: [ACS4.1] cloudstack-agent

On Mon, May 13, 2013 at 07:27:54AM +, Paul Angus wrote: > It's the same hardware as for the 4.0.2 build - it's scripted and > only difference is the repo used. > I've seen this happen when scripting my install on switching to 4.1. KVM modules are not detected even though virtualization is ena

RE: [ACS4.1] cloudstack-agent

43 To: dev@cloudstack.apache.org Subject: Re: [ACS4.1] cloudstack-agent Should also ask, is this new hardware? 4.0.2 will not work either if lsmod doesn't show a KVM module, so I would assume your 4.0.2 is on a different set of systems. On May 12, 2013 2:34 PM, "Paul Angus" w

Re: [ACS4.1] cloudstack-agent

Should also ask, is this new hardware? 4.0.2 will not work either if lsmod doesn't show a KVM module, so I would assume your 4.0.2 is on a different set of systems. On May 12, 2013 2:34 PM, "Paul Angus" wrote: > Hi. > > > > I’m having problems building an ACS 4.1 CentOS(6.3) KVM host > > > > It

Re: [ACS4.1] cloudstack-agent

No KVM module means the cloudstack agent won't even try to start or join cloudstack. Even aside from cloudstack you wouldn't be able to run KVM based virtual machines. Check that you have the virtualization extensions enabled for your CPU in your BIOS. Also, you can try to modprobe the kvm and kvm

[ACS4.1] cloudstack-agent

Hi. I'm having problems building an ACS 4.1 CentOS(6.3) KVM host It appears to install correctly but the only entries in libvirtd.log are: 2013-05-12 20:26:37.256+: 1399: info : libvirt version: 0.10.2, package: 18.el6_4.4 (CentOS BuildSystem , 2013-04-18-16:13:45,