Re: KVM Agent

[Andrija Panic]

No. VirtIO drives for NIC/SCSI if you chose OS type that will have VirtIO
"HW" fo the VM - that's all (that means manual install inside the Windows
OSes)

On Wed, 18 Aug 2021 at 10:44, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
> Does guest VMs needed some agent on KVM environment such as same as on
> Vmware or Xenserver/XCP-NG?
>
>
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as the
> intended recipient (recipients). If you are not the intended recipient of
> this email, do not copy or disclose its contents and delete the message and
> any attachments to it from your e-mail system. Any unauthorized use,
> dissemination, disclosure, printing or copying of this e-mail and files
> attached to it, except by the intended recipient, is illegal and is
> prohibited. Taking into account that data transmission via Internet is not
> secure, we assume no responsibility for any potential damage caused by data
> transmission errors or this message and the files attached to it.
>


-- 

Andrija Panić

KVM Agent

[Дикевич Евгений Александрович]

Hi all!
Does guest VMs needed some agent on KVM environment such as same as on Vmware 
or Xenserver/XCP-NG?


Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Re: KVM Agent Error: Incorrect details for private Nic

[Dag Sonstebo]

Excellent, glad you got it up and running.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 11/01/2019, 16:13, "Daniel Farrar"  wrote:

This set me straight, much appreciated!  Was over-complicating my demo 
setup, got rid of all vlans for Public and Management networks while leaving 
Guest networks with a VLAN range.  No issues now. 

Daniel Farrar

-Original Message-
From: Dag Sonstebo  
Sent: Thursday, January 10, 2019 11:42 AM
To: users@cloudstack.apache.org
Subject: Re: KVM Agent Error: Incorrect details for private Nic

Hi Daniel,

Yes makes sense and this is your simplest setup. Just remembered I updated 
this blog post a couple of months back - it should see you right 
https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/
 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 10/01/2019, 16:37, "Daniel Farrar"  
wrote:

Thank you Dag, this looks very likely to be the case.  I was able to 
find a scenario yesterday that brought the service up by setting eno1.8 type to 
Ethernet, disabling eno1.8, restarting the agent service, then re-enabling 
eno1.8 as type Vlan.  My intended design was to create a 2 NIC bond (for now 
just single NIC eno1 for troubleshooting), create subinterfaces (ex eno1.8 for 
vlan8), and assign each subinterface to a cloudstack service.  I will try 
letting Cloudstack take care of all vlans and remove the subinterface, pointing 
cloudbr0 directly to eno1 or bond.

​Daniel Farrar

-Original Message-
From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Sent: Wednesday, January 9, 2019 10:38 AM
To: users@cloudstack.apache.org
        Subject: Re: KVM Agent Error: Incorrect details for private Nic

Hi Daniel,

My initial guess without deep diving into this is your NIC naming. The 
CloudStack agent looks for the interface (bond / NIC / team) which supports 
cloudbr0 - and I think maybe in your case it can't find it due to the dotted 
naming "eno1.8" when it probably expects some conventional like "eno16777984".

Is there a reason you've named it like this? This would normally point 
to a VLAN setup (whereas cloudbr0 needs to be trunked in an advanced zone). 
If not can you rename it?

Code for this is somewhere around here I think:

https://github.com/apache/cloudstack/blob/c565db2cf2ab5fdbd2fba65409928dfa7c5f2d25/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L1312

Developers - please correct me if I'm wrong.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 09/01/2019, 14:08, "Daniel Farrar"  
wrote:

Hello!  Wanted to see if anyone else has ran into this issue or if 
you can point me in the right direction...

I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that 
are not able to start the cloudstack-agent service if the agent.propreties file 
specifies the variable "private.network.device=cloudbr0".  This is 
automatically added to the config file when the agent connects to the server, 
if the private network is commented out the service is able to start up but any 
system VMs are unable to connect to the network.  This environment was working 
with my original 2 KVM agents, but after deleting the hosts and rebuilding with 
identical network config I've ran into this issue.  I have logs and configs 
below, any ideas what is wrong?  This is a dev proof of concept environment, so 
I can rebuild if needed.  Thank you for your time!


2019-01-07 15:36:10,257 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Agent started
2019-01-07 15:36:10,259 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Implementation Version is 4.11.2.0
2019-01-07 15:36:10,260 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
2019-01-07 15:36:10,271 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Defaulting to using properties file for storage
2019-01-07 15:36:10,272 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Defaulting to the constant time backoff algorithm
2019-01-07 15:36:10,282 INFO  [cloud.utils.LogUtils] (main:null) 
(logid:) log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2019-01-07 15:36:10,293 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Using default Java settings for IPv6 preference for agent connection
2019-01-07 15:36:10,384 INFO  [cloud.agent.Agent] (main:null) 
(logid:) id is 15
2019

RE: KVM Agent Error: Incorrect details for private Nic

[Daniel Farrar]

This set me straight, much appreciated!  Was over-complicating my demo setup, 
got rid of all vlans for Public and Management networks while leaving Guest 
networks with a VLAN range.  No issues now. 

Daniel Farrar

-Original Message-
From: Dag Sonstebo  
Sent: Thursday, January 10, 2019 11:42 AM
To: users@cloudstack.apache.org
Subject: Re: KVM Agent Error: Incorrect details for private Nic

Hi Daniel,

Yes makes sense and this is your simplest setup. Just remembered I updated this 
blog post a couple of months back - it should see you right 
https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/
 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 10/01/2019, 16:37, "Daniel Farrar"  wrote:

Thank you Dag, this looks very likely to be the case.  I was able to find a 
scenario yesterday that brought the service up by setting eno1.8 type to 
Ethernet, disabling eno1.8, restarting the agent service, then re-enabling 
eno1.8 as type Vlan.  My intended design was to create a 2 NIC bond (for now 
just single NIC eno1 for troubleshooting), create subinterfaces (ex eno1.8 for 
vlan8), and assign each subinterface to a cloudstack service.  I will try 
letting Cloudstack take care of all vlans and remove the subinterface, pointing 
cloudbr0 directly to eno1 or bond.

​Daniel Farrar

-Original Message-
From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Sent: Wednesday, January 9, 2019 10:38 AM
To: users@cloudstack.apache.org
Subject: Re: KVM Agent Error: Incorrect details for private Nic

Hi Daniel,

My initial guess without deep diving into this is your NIC naming. The 
CloudStack agent looks for the interface (bond / NIC / team) which supports 
cloudbr0 - and I think maybe in your case it can't find it due to the dotted 
naming "eno1.8" when it probably expects some conventional like "eno16777984".

Is there a reason you've named it like this? This would normally point to a 
VLAN setup (whereas cloudbr0 needs to be trunked in an advanced zone). 
If not can you rename it?

Code for this is somewhere around here I think:

https://github.com/apache/cloudstack/blob/c565db2cf2ab5fdbd2fba65409928dfa7c5f2d25/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L1312

Developers - please correct me if I'm wrong.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 09/01/2019, 14:08, "Daniel Farrar"  
wrote:

Hello!  Wanted to see if anyone else has ran into this issue or if you 
can point me in the right direction...

I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that are 
not able to start the cloudstack-agent service if the agent.propreties file 
specifies the variable "private.network.device=cloudbr0".  This is 
automatically added to the config file when the agent connects to the server, 
if the private network is commented out the service is able to start up but any 
system VMs are unable to connect to the network.  This environment was working 
with my original 2 KVM agents, but after deleting the hosts and rebuilding with 
identical network config I've ran into this issue.  I have logs and configs 
below, any ideas what is wrong?  This is a dev proof of concept environment, so 
I can rebuild if needed.  Thank you for your time!


2019-01-07 15:36:10,257 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Agent started
2019-01-07 15:36:10,259 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Implementation Version is 4.11.2.0
2019-01-07 15:36:10,260 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
2019-01-07 15:36:10,271 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Defaulting to using properties file for storage
2019-01-07 15:36:10,272 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Defaulting to the constant time backoff algorithm
2019-01-07 15:36:10,282 INFO  [cloud.utils.LogUtils] (main:null) 
(logid:) log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2019-01-07 15:36:10,293 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Using default Java settings for IPv6 preference for agent connection
2019-01-07 15:36:10,384 INFO  [cloud.agent.Agent] (main:null) (logid:) 
id is 15
2019-01-07 15:36:10,387 WARN  [cloud.resource.ServerResourceBase] 
(main:null) (logid:) Incorrect details for private Nic during initialization of 
ServerResourceBase
2019-01-07 15:36:10,387 ERROR [cloud.agent.AgentShell] (main:null) 
(logid:) Unable to start agent: Unable to configure LibvirtComputingResource


This occurs on version 4.11.1 and 4.11.2, and I've seen other threads 
with this i

Re: KVM Agent Error: Incorrect details for private Nic

[Dag Sonstebo]

Hi Daniel,

Yes makes sense and this is your simplest setup. Just remembered I updated this 
blog post a couple of months back - it should see you right 
https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/
 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 10/01/2019, 16:37, "Daniel Farrar"  wrote:

Thank you Dag, this looks very likely to be the case.  I was able to find a 
scenario yesterday that brought the service up by setting eno1.8 type to 
Ethernet, disabling eno1.8, restarting the agent service, then re-enabling 
eno1.8 as type Vlan.  My intended design was to create a 2 NIC bond (for now 
just single NIC eno1 for troubleshooting), create subinterfaces (ex eno1.8 for 
vlan8), and assign each subinterface to a cloudstack service.  I will try 
letting Cloudstack take care of all vlans and remove the subinterface, pointing 
cloudbr0 directly to eno1 or bond.

​Daniel Farrar

-Original Message-
From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Sent: Wednesday, January 9, 2019 10:38 AM
To: users@cloudstack.apache.org
Subject: Re: KVM Agent Error: Incorrect details for private Nic

Hi Daniel,

My initial guess without deep diving into this is your NIC naming. The 
CloudStack agent looks for the interface (bond / NIC / team) which supports 
cloudbr0 - and I think maybe in your case it can't find it due to the dotted 
naming "eno1.8" when it probably expects some conventional like "eno16777984".

Is there a reason you've named it like this? This would normally point to a 
VLAN setup (whereas cloudbr0 needs to be trunked in an advanced zone). 
If not can you rename it?

Code for this is somewhere around here I think:

https://github.com/apache/cloudstack/blob/c565db2cf2ab5fdbd2fba65409928dfa7c5f2d25/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L1312

Developers - please correct me if I'm wrong.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 09/01/2019, 14:08, "Daniel Farrar"  
wrote:

Hello!  Wanted to see if anyone else has ran into this issue or if you 
can point me in the right direction...

I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that are 
not able to start the cloudstack-agent service if the agent.propreties file 
specifies the variable "private.network.device=cloudbr0".  This is 
automatically added to the config file when the agent connects to the server, 
if the private network is commented out the service is able to start up but any 
system VMs are unable to connect to the network.  This environment was working 
with my original 2 KVM agents, but after deleting the hosts and rebuilding with 
identical network config I've ran into this issue.  I have logs and configs 
below, any ideas what is wrong?  This is a dev proof of concept environment, so 
I can rebuild if needed.  Thank you for your time!


2019-01-07 15:36:10,257 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Agent started
2019-01-07 15:36:10,259 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Implementation Version is 4.11.2.0
2019-01-07 15:36:10,260 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
2019-01-07 15:36:10,271 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Defaulting to using properties file for storage
2019-01-07 15:36:10,272 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Defaulting to the constant time backoff algorithm
2019-01-07 15:36:10,282 INFO  [cloud.utils.LogUtils] (main:null) 
(logid:) log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2019-01-07 15:36:10,293 INFO  [cloud.agent.AgentShell] (main:null) 
(logid:) Using default Java settings for IPv6 preference for agent connection
2019-01-07 15:36:10,384 INFO  [cloud.agent.Agent] (main:null) (logid:) 
id is 15
2019-01-07 15:36:10,387 WARN  [cloud.resource.ServerResourceBase] 
(main:null) (logid:) Incorrect details for private Nic during initialization of 
ServerResourceBase
2019-01-07 15:36:10,387 ERROR [cloud.agent.AgentShell] (main:null) 
(logid:) Unable to start agent: Unable to configure LibvirtComputingResource


This occurs on version 4.11.1 and 4.11.2, and I've seen other threads 
with this issue on earlier versions that reported downgrading the agent fixed 
this issue.



NIC CONFIGURATION:

ifcfg-cloudbr0
DEVICE=cloudbr0
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=none
IPV6INIT=no
IPV6_AUTOCONF=no
DELAY=5
STP=yes

Ifcfg-eno1.8
HWADDR=XX:XX:XX:XX:XX:XX
  

RE: KVM Agent Error: Incorrect details for private Nic

[Daniel Farrar]

Thank you Dag, this looks very likely to be the case.  I was able to find a 
scenario yesterday that brought the service up by setting eno1.8 type to 
Ethernet, disabling eno1.8, restarting the agent service, then re-enabling 
eno1.8 as type Vlan.  My intended design was to create a 2 NIC bond (for now 
just single NIC eno1 for troubleshooting), create subinterfaces (ex eno1.8 for 
vlan8), and assign each subinterface to a cloudstack service.  I will try 
letting Cloudstack take care of all vlans and remove the subinterface, pointing 
cloudbr0 directly to eno1 or bond.

​Daniel Farrar

-Original Message-
From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Sent: Wednesday, January 9, 2019 10:38 AM
To: users@cloudstack.apache.org
Subject: Re: KVM Agent Error: Incorrect details for private Nic

Hi Daniel,

My initial guess without deep diving into this is your NIC naming. The 
CloudStack agent looks for the interface (bond / NIC / team) which supports 
cloudbr0 - and I think maybe in your case it can't find it due to the dotted 
naming "eno1.8" when it probably expects some conventional like "eno16777984".

Is there a reason you've named it like this? This would normally point to a 
VLAN setup (whereas cloudbr0 needs to be trunked in an advanced zone). 
If not can you rename it?

Code for this is somewhere around here I think:
https://github.com/apache/cloudstack/blob/c565db2cf2ab5fdbd2fba65409928dfa7c5f2d25/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L1312

Developers - please correct me if I'm wrong.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 09/01/2019, 14:08, "Daniel Farrar"  wrote:

Hello!  Wanted to see if anyone else has ran into this issue or if you can 
point me in the right direction...

I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that are not 
able to start the cloudstack-agent service if the agent.propreties file 
specifies the variable "private.network.device=cloudbr0".  This is 
automatically added to the config file when the agent connects to the server, 
if the private network is commented out the service is able to start up but any 
system VMs are unable to connect to the network.  This environment was working 
with my original 2 KVM agents, but after deleting the hosts and rebuilding with 
identical network config I've ran into this issue.  I have logs and configs 
below, any ideas what is wrong?  This is a dev proof of concept environment, so 
I can rebuild if needed.  Thank you for your time!


2019-01-07 15:36:10,257 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Agent started
2019-01-07 15:36:10,259 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Implementation Version is 4.11.2.0
2019-01-07 15:36:10,260 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2019-01-07 15:36:10,271 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to using properties file for storage
2019-01-07 15:36:10,272 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to the constant time backoff algorithm
2019-01-07 15:36:10,282 INFO  [cloud.utils.LogUtils] (main:null) (logid:) 
log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2019-01-07 15:36:10,293 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Using default Java settings for IPv6 preference for agent connection
2019-01-07 15:36:10,384 INFO  [cloud.agent.Agent] (main:null) (logid:) id 
is 15
2019-01-07 15:36:10,387 WARN  [cloud.resource.ServerResourceBase] 
(main:null) (logid:) Incorrect details for private Nic during initialization of 
ServerResourceBase
2019-01-07 15:36:10,387 ERROR [cloud.agent.AgentShell] (main:null) (logid:) 
Unable to start agent: Unable to configure LibvirtComputingResource


This occurs on version 4.11.1 and 4.11.2, and I've seen other threads with 
this issue on earlier versions that reported downgrading the agent fixed this 
issue.



NIC CONFIGURATION:

ifcfg-cloudbr0
DEVICE=cloudbr0
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=none
IPV6INIT=no
IPV6_AUTOCONF=no
DELAY=5
STP=yes

Ifcfg-eno1.8
HWADDR=XX:XX:XX:XX:XX:XX
DEVICE=eno1.8
ONBOOT=yes
HOTPLUG=no
BOOTPROTO=none
TYPE=Vlan
VLAN=yes
BRIDGE=cloudbr0

cloudbr0: flags=4163  mtu 1500
ether txqueuelen 1000  (Ethernet)
RX packets 2368  bytes 116316 (113.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 3  bytes 270 (270.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno1.8: flags=4163  mtu 1500
ether txqueuelen 1000  (Ethernet)
RX packets 3159  bytes 163465 (159.6 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
  

Re: KVM Agent Error: Incorrect details for private Nic

[Dag Sonstebo]

Hi Daniel,

My initial guess without deep diving into this is your NIC naming. The 
CloudStack agent looks for the interface (bond / NIC / team) which supports 
cloudbr0 - and I think maybe in your case it can't find it due to the dotted 
naming "eno1.8" when it probably expects some conventional like "eno16777984".

Is there a reason you've named it like this? This would normally point to a 
VLAN setup (whereas cloudbr0 needs to be trunked in an advanced zone). 
If not can you rename it?

Code for this is somewhere around here I think:
https://github.com/apache/cloudstack/blob/c565db2cf2ab5fdbd2fba65409928dfa7c5f2d25/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L1312

Developers - please correct me if I'm wrong.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 09/01/2019, 14:08, "Daniel Farrar"  wrote:

Hello!  Wanted to see if anyone else has ran into this issue or if you can 
point me in the right direction...

I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that are not 
able to start the cloudstack-agent service if the agent.propreties file 
specifies the variable "private.network.device=cloudbr0".  This is 
automatically added to the config file when the agent connects to the server, 
if the private network is commented out the service is able to start up but any 
system VMs are unable to connect to the network.  This environment was working 
with my original 2 KVM agents, but after deleting the hosts and rebuilding with 
identical network config I've ran into this issue.  I have logs and configs 
below, any ideas what is wrong?  This is a dev proof of concept environment, so 
I can rebuild if needed.  Thank you for your time!


2019-01-07 15:36:10,257 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Agent started
2019-01-07 15:36:10,259 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Implementation Version is 4.11.2.0
2019-01-07 15:36:10,260 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2019-01-07 15:36:10,271 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to using properties file for storage
2019-01-07 15:36:10,272 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to the constant time backoff algorithm
2019-01-07 15:36:10,282 INFO  [cloud.utils.LogUtils] (main:null) (logid:) 
log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2019-01-07 15:36:10,293 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Using default Java settings for IPv6 preference for agent connection
2019-01-07 15:36:10,384 INFO  [cloud.agent.Agent] (main:null) (logid:) id 
is 15
2019-01-07 15:36:10,387 WARN  [cloud.resource.ServerResourceBase] 
(main:null) (logid:) Incorrect details for private Nic during initialization of 
ServerResourceBase
2019-01-07 15:36:10,387 ERROR [cloud.agent.AgentShell] (main:null) (logid:) 
Unable to start agent: Unable to configure LibvirtComputingResource


This occurs on version 4.11.1 and 4.11.2, and I've seen other threads with 
this issue on earlier versions that reported downgrading the agent fixed this 
issue.



NIC CONFIGURATION:

ifcfg-cloudbr0
DEVICE=cloudbr0
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=none
IPV6INIT=no
IPV6_AUTOCONF=no
DELAY=5
STP=yes

Ifcfg-eno1.8
HWADDR=XX:XX:XX:XX:XX:XX
DEVICE=eno1.8
ONBOOT=yes
HOTPLUG=no
BOOTPROTO=none
TYPE=Vlan
VLAN=yes
BRIDGE=cloudbr0

cloudbr0: flags=4163  mtu 1500
ether txqueuelen 1000  (Ethernet)
RX packets 2368  bytes 116316 (113.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 3  bytes 270 (270.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno1.8: flags=4163  mtu 1500
ether txqueuelen 1000  (Ethernet)
RX packets 3159  bytes 163465 (159.6 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1752  bytes 91924 (89.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


brctl show
bridge name bridge id   STP enabled interfaces
cloud0  8000.fe00a9fe00fc   no  vnet0
vnet3
cloudbr08000.64510630b869   yes eno1.8
vnet2
vnet5
cloudbr18000.64510630b869   yes eno1.7
vnet1
vnet4
virbr0  8000.525400b79d7d   yes virbr0-nic


Agent.properties file networks:

KVM Agent Error: Incorrect details for private Nic

[Daniel Farrar]

Hello!  Wanted to see if anyone else has ran into this issue or if you can 
point me in the right direction...

I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that are not able 
to start the cloudstack-agent service if the agent.propreties file specifies 
the variable "private.network.device=cloudbr0".  This is automatically added to 
the config file when the agent connects to the server, if the private network 
is commented out the service is able to start up but any system VMs are unable 
to connect to the network.  This environment was working with my original 2 KVM 
agents, but after deleting the hosts and rebuilding with identical network 
config I've ran into this issue.  I have logs and configs below, any ideas what 
is wrong?  This is a dev proof of concept environment, so I can rebuild if 
needed.  Thank you for your time!


2019-01-07 15:36:10,257 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Agent started
2019-01-07 15:36:10,259 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Implementation Version is 4.11.2.0
2019-01-07 15:36:10,260 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2019-01-07 15:36:10,271 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to using properties file for storage
2019-01-07 15:36:10,272 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to the constant time backoff algorithm
2019-01-07 15:36:10,282 INFO  [cloud.utils.LogUtils] (main:null) (logid:) log4j 
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2019-01-07 15:36:10,293 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Using default Java settings for IPv6 preference for agent connection
2019-01-07 15:36:10,384 INFO  [cloud.agent.Agent] (main:null) (logid:) id is 15
2019-01-07 15:36:10,387 WARN  [cloud.resource.ServerResourceBase] (main:null) 
(logid:) Incorrect details for private Nic during initialization of 
ServerResourceBase
2019-01-07 15:36:10,387 ERROR [cloud.agent.AgentShell] (main:null) (logid:) 
Unable to start agent: Unable to configure LibvirtComputingResource


This occurs on version 4.11.1 and 4.11.2, and I've seen other threads with this 
issue on earlier versions that reported downgrading the agent fixed this issue.



NIC CONFIGURATION:

ifcfg-cloudbr0
DEVICE=cloudbr0
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=none
IPV6INIT=no
IPV6_AUTOCONF=no
DELAY=5
STP=yes

Ifcfg-eno1.8
HWADDR=XX:XX:XX:XX:XX:XX
DEVICE=eno1.8
ONBOOT=yes
HOTPLUG=no
BOOTPROTO=none
TYPE=Vlan
VLAN=yes
BRIDGE=cloudbr0

cloudbr0: flags=4163  mtu 1500
ether txqueuelen 1000  (Ethernet)
RX packets 2368  bytes 116316 (113.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 3  bytes 270 (270.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno1.8: flags=4163  mtu 1500
ether txqueuelen 1000  (Ethernet)
RX packets 3159  bytes 163465 (159.6 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1752  bytes 91924 (89.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


brctl show
bridge name bridge id   STP enabled interfaces
cloud0  8000.fe00a9fe00fc   no  vnet0
vnet3
cloudbr08000.64510630b869   yes eno1.8
vnet2
vnet5
cloudbr18000.64510630b869   yes eno1.7
vnet1
vnet4
virbr0  8000.525400b79d7d   yes virbr0-nic


Agent.properties file networks:
public.network.device=cloudbr0
private.network.device=cloudbr0
guest.network.device=cloudbr1


Cloudstack Zone network config:

Zone > Physical Network 1 > Public
Traffic Type

Public



Broadcast Domain Type

Vlan



KVM traffic label

cloudbr0



10.x.y1

255.255.255.0

vlan://untagged

10.x.y.100

10.x.y.199

[ROOT] system


**Note: The public network works fine, virtual routers have network access.

Zone > Physical Network 1 > Management
Traffic Type

Management



Broadcast Domain Type

Native



KVM traffic label

cloudbr0



Pod1

10.x.y.1

255.255.255.0

vlan://8

10.x.y.30

10.x.y.49

system VMs



Pod1

10.x.y.1

255.255.255.0

vlan://8

10.x.y.50

10.x.y.99



**NOTE: Tried above Mangement IP ranges with and without vlan tags, can't get 
any system VMs to have network connectivity


Zone > Physical Network 1 > Guest
State

Enabled

VLAN/VNI Range(s)

800-850

KVM traffic label

cloudbr1




Daniel Farrar




Confidentiality Notice: This message, including any attachment(s), may contain 
confidential information protected by law. The information contained herein is 
for the sole use of the intended recipient(s). If you 

RE: 请教：如何在无互联网的环境下在计算主机上安装KVM agent，小白问题，万分感激！！！

[胡爱丽]

您好，

 

希望下面这个链接你能用到：

http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Installation_Guide/configure-package-repository.html
 

 From: cat...@qq.com
 To: users-cn@cloudstack.apache.org
 Subject: 请教：如何在无互联网的环境下在计算主机上安装KVM agent，小白问题，万分感激！！！
 Date: Thu, 29 Aug 2013 21:51:24 +0800
 
 我是首次尝试部署cloudstack，用了两台服务器安装，一台做管理主机、一台做计算主机（计算节点），管理主机用社区里的一键安装盘装好了（cloudstack4.1一键安装盘），计算主机上安装了CentOS6.4系统，安装时选择“Virtual
  HOST”，勾上了KVM组件，安装完毕后在终端中运行“service libvirtd status”，显示服务正在运行。但是cloudstack 
 agent装不上，直接上传社区网盘里的“/4.1-nonoss/dist/RPMS/cloudstack-agent-4.1.0-0.el6.x86_64.rpm”，在主机上执行“rpm
  -i cloudstack-agent-4.1.0-0.el6.x86_64.rpm”,报错说缺少文件。
 
 
 然后我在网上查了，网上都是cloudstack 
 3.0的离线安装教程，我下载了“apache-cloudstack-4.1.0-src.tar.bz2”文件，解压后发现没有“install.sh”文件，不知如何安装。
 
 
 
 
 
 
 
 
 本人初次尝试安装cloudstack，对Linux系统也只会基本命令，问出来的问题很傻，但是我对cloudstack抱着满腔热诚，请邮件组里的同志们帮我一把，带我入门，万分感激！！！
  

Re: 请教：如何在无互联网的环境下在计算主机上安装KVM agent，小白问题，万分感激！！！

[ma y]

简而言之，你可以这么做
搭建本地源，做两个，一个本地Base软件包源（用一张完整版的安装光盘），一个Cloudstack源（文件从社区网盘可下载）
然后yum


在 2013年8月29日下午9:51，catbig cat...@qq.com写道：

 我是首次尝试部署cloudstack，用了两台服务器安装，一台做管理主机、一台做计算主机（计算节点），管理主机用社区里的一键安装盘装好了（cloudstack4.1一键安装盘），计算主机上安装了CentOS6.4系统，安装时选择“Virtual
 HOST”，勾上了KVM组件，安装完毕后在终端中运行“service libvirtd status”，显示服务正在运行。但是cloudstack
 agent装不上，直接上传社区网盘里的“/4.1-nonoss/dist/RPMS/cloudstack-agent-4.1.0-0.el6.x86_64.rpm”，在主机上执行“rpm
 -i cloudstack-agent-4.1.0-0.el6.x86_64.rpm”,报错说缺少文件。


 然后我在网上查了，网上都是cloudstack
 3.0的离线安装教程，我下载了“apache-cloudstack-4.1.0-src.tar.bz2”文件，解压后发现没有“install.sh”文件，不知如何安装。









 本人初次尝试安装cloudstack，对Linux系统也只会基本命令，问出来的问题很傻，但是我对cloudstack抱着满腔热诚，请邮件组里的同志们帮我一把，带我入门，万分感激！！！

Re: kvm agent端日志报错

[linux...@gmail.com]

建议你检查下cgroup的配置是否做过修改，仔细看看网上关于KVM模式的配置文档，另外检查下防火墙的配置，看看是不是防火墙的原因


2013/7/3 求职者 gaoyaqingcar...@163.com

agent 端报错
 2013-07-03 23:36:05,675 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:10,676 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:10,677 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:15,678 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:15,679 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:20,680 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:20,681 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:25,683 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:25,684 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:30,685 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:30,685 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:35,687 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:35,687 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:40,689 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:40,689 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:45,690 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:45,691 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:50,692 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:50,693 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:36:55,694 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:36:55,694 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:00,695 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:00,696 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:05,697 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:05,698 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:10,700 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:10,700 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:15,702 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:15,702 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:20,703 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:20,704 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:25,715 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:25,718 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:30,719 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:30,719 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:35,721 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:35,722 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:40,781 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:40,782 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:45,783 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:45,783 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:50,785 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:50,785 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:55,787 INFO  [utils.nio.NioClient] (Agent-Selector:null)
 Connecting to localhost:8250
 2013-07-03 23:37:55,789 ERROR [utils.nio.NioConnection]
 (Agent-Selector:null) Unable to connect to remote
 2013-07-03 23:37:57,547 INFO  [cloud.agent.Agent]
 

kvm agent端日志报错

[求职者]

   agent 端报错
2013-07-03 23:36:05,675 ERROR [utils.nio.NioConnection] 
(Agent-Selector:null) Unable to connect to remote
2013-07-03 23:36:10,676 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:10,677 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:15,678 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:15,679 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:20,680 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:20,681 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:25,683 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:25,684 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:30,685 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:30,685 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:35,687 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:35,687 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:40,689 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:40,689 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:45,690 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:45,691 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:50,692 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:50,693 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:36:55,694 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:36:55,694 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:00,695 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:00,696 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:05,697 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:05,698 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:10,700 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:10,700 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:15,702 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:15,702 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:20,703 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:20,704 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:25,715 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:25,718 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:30,719 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:30,719 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:35,721 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:35,722 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:40,781 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:40,782 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:45,783 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:45,783 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:50,785 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:50,785 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:55,787 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2013-07-03 23:37:55,789 ERROR [utils.nio.NioConnection] (Agent-Selector:null) 
Unable to connect to remote
2013-07-03 23:37:57,547 INFO  [cloud.agent.Agent] (AgentShutdownThread:null) 
Stopping the agent: Reason = sig.kill

RE: CS KVM agent 4.1.0 install

[COCHE Sébastien]

Thank you very much.
It's working...

-Message d'origine-
De : Chip Childers [mailto:chip.child...@sungard.com] 
Envoyé : mercredi 29 mai 2013 21:46
À : COCHE Sébastien
Cc : users@cloudstack.apache.org
Objet : Re: CS KVM agent 4.1.0 install

On Wed, May 29, 2013 at 11:26:20AM +0200, COCHE Sébastien wrote:
 I wait for a long time that the 4.1 version is officially released.
 In order to not slow my project, I would like to test CS 4.1 version without 
 waiting the official release.
 I installed the core successfully, but I don't know how to install KVM 
 agent. So my platform is unusable :-( The release note you told me to check 
 do not say how to install/upgrade agent from source.

What platform are your hosts?

If CENTOS/RHEL, build the RPMs with the packaging/centos63/package.sh script.

If Ubuntu, then follow the packaging instructions to create the deb packages.

From there, if you installed via packages previously, follow the appropriate 
upgrade steps for that specific platform.

Hope that helps!

 
 
 -Message d'origine-
 De : Chip Childers [mailto:chip.child...@sungard.com]
 Envoyé : mardi 28 mai 2013 19:10
 À : users@cloudstack.apache.org
 Objet : Re: CS KVM agent 4.1.0 install
 
 On Tue, May 28, 2013 at 09:45:40AM +0200, COCHE Sébastien wrote:
  Hi all,
  
  I successfully install CS 4.1, using the procedure bellow.
  But I don't know, how to install/upgrade KVM's CS Agent.
  Can you help me ?
 
 When we officially release 4.1, the release notes includes a section on 
 upgrades.  Feel free to check it out in the source 
 (docs/en-US/Release_Notes.xml).
 
  
  Another question
  Some time ago, i could download CS artifacts from Jenkins website.
  Those ones are no longer available. Do you know why ?
 
 We aren't keeping those build artifacts around anymore, due to resource 
 consumption issues.
 
 

RE: CS KVM agent 4.1.0 install

[COCHE Sébastien]

I wait for a long time that the 4.1 version is officially released.
In order to not slow my project, I would like to test CS 4.1 version without 
waiting the official release.
I installed the core successfully, but I don't know how to install KVM agent. 
So my platform is unusable :-(
The release note you told me to check do not say how to install/upgrade agent 
from source.


-Message d'origine-
De : Chip Childers [mailto:chip.child...@sungard.com] 
Envoyé : mardi 28 mai 2013 19:10
À : users@cloudstack.apache.org
Objet : Re: CS KVM agent 4.1.0 install

On Tue, May 28, 2013 at 09:45:40AM +0200, COCHE Sébastien wrote:
 Hi all,
 
 I successfully install CS 4.1, using the procedure bellow.
 But I don't know, how to install/upgrade KVM's CS Agent.
 Can you help me ?

When we officially release 4.1, the release notes includes a section on 
upgrades.  Feel free to check it out in the source 
(docs/en-US/Release_Notes.xml).

 
 Another question
 Some time ago, i could download CS artifacts from Jenkins website.
 Those ones are no longer available. Do you know why ?

We aren't keeping those build artifacts around anymore, due to resource 
consumption issues.

Re: CS KVM agent 4.1.0 install

[Chip Childers]

On Wed, May 29, 2013 at 11:26:20AM +0200, COCHE Sébastien wrote:
 I wait for a long time that the 4.1 version is officially released.
 In order to not slow my project, I would like to test CS 4.1 version without 
 waiting the official release.
 I installed the core successfully, but I don't know how to install KVM agent. 
 So my platform is unusable :-(
 The release note you told me to check do not say how to install/upgrade agent 
 from source.

What platform are your hosts?

If CENTOS/RHEL, build the RPMs with the packaging/centos63/package.sh
script.

If Ubuntu, then follow the packaging instructions to create the deb
packages.

From there, if you installed via packages previously, follow the
appropriate upgrade steps for that specific platform.

Hope that helps!

 
 
 -Message d'origine-
 De : Chip Childers [mailto:chip.child...@sungard.com] 
 Envoyé : mardi 28 mai 2013 19:10
 À : users@cloudstack.apache.org
 Objet : Re: CS KVM agent 4.1.0 install
 
 On Tue, May 28, 2013 at 09:45:40AM +0200, COCHE Sébastien wrote:
  Hi all,
  
  I successfully install CS 4.1, using the procedure bellow.
  But I don't know, how to install/upgrade KVM's CS Agent.
  Can you help me ?
 
 When we officially release 4.1, the release notes includes a section on 
 upgrades.  Feel free to check it out in the source 
 (docs/en-US/Release_Notes.xml).
 
  
  Another question
  Some time ago, i could download CS artifacts from Jenkins website.
  Those ones are no longer available. Do you know why ?
 
 We aren't keeping those build artifacts around anymore, due to resource 
 consumption issues.
 
 

CS KVM agent 4.1.0 install

[COCHE Sébastien]

Hi all,

I successfully install CS 4.1, using the procedure bellow.
But I don't know, how to install/upgrade KVM's CS Agent.
Can you help me ?

Another question
Some time ago, i could download CS artifacts from Jenkins website.
Those ones are no longer available. Do you know why ?

Thank you 

Regards

-Message d'origine-
De : Chip Childers [mailto:chip.child...@sungard.com] 
Envoyé : dimanche 26 mai 2013 16:57
À : users@cloudstack.apache.org
Objet : Fwd: [VOTE] Release Apache CloudStack 4.1.0 (fourth round)

Hi user@ folks!  We have started our fourth round of voting on 4.1.0.
Your feedback is welcome!

-chip

- Forwarded message from Chip Childers chip.child...@sungard.com -

Date: Sun, 26 May 2013 10:54:02 -0400
From: Chip Childers chip.child...@sungard.com
To: d...@cloudstack.apache.org
Subject: [VOTE] Release Apache CloudStack 4.1.0 (fourth round)
Message-ID: 20130526145402.gq90...@uslt-205755.sungardas.corp

Hi All,

I've created a 4.1.0 release, with the following artifacts up for a vote.

The changes from round 3 are two commits related to DEB packaging.

Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
Commit:  db007da15290970c842c3229a11051c20b512a65

List of changes:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.1

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/

PGP release keys (signed using A99A5D58):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

Testing instructions are here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure

Vote will be open for 72 hours.

For sanity in tallying the vote, can PMC members please be sure to indicate 
(binding) with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

- End forwarded message -