Re: Cannot start stopped VMs

[Harikrishna Patnala]

Hi,

At first glance on the logs, I could see below reasons for the start VM failures

management server logs:
2021-04-19 18:31:13,539 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-46:ctx-7073f4ff job-28887/job-2 ctx-70a0c6b3) 
(logid:e613b60b) Unable to start VM on Host[-1-Routing] due to Connection is 
closed

agent logs:
2021-04-19 18:31:25,017 WARN  [kvm.resource.LibvirtKvmAgentHook] 
(agentRequest-Handler-1:null) (logid:92f2a447) Groovy scripting engine is not 
initialized. Data transformation skipped.
2021-04-19 18:31:25,686 WARN  [resource.wrapper.LibvirtStartCommandWrapper] 
(agentRequest-Handler-1:null) (logid:92f2a447) LibvirtException
org.libvirt.LibvirtException: Connection is closed
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.domainCreateXML(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1611)
at 
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:85)


Can you check if libvirtd service running on your KVM host? Also, you can do a 
quick KVM agent restart and see if it works "systemctl restart cloudstack-agent"

Regards,
Harikrishna

From: Fariborz Navidan 
Sent: Tuesday, April 20, 2021 12:22 AM
To: users@cloudstack.apache.org 
Subject: Cannot start stopped VMs

Hello,

Today, I just updated SSL certificate and it failed re-deploying system
VMs. Also, when I try to start a VM that is stopped, it fails with message:
Unable to create deployment due to insufficient capacity. I couldn't find
the reason from logs. I have uploaded  partial management server and agent
logs.

https://www.r9host.com/log/management-server.log
https://www.r9host.com/log/agent.log

It is a mission critical issue for us. I would appreciate if you guys check
the logs and let us know what we can do to fix this issue.

Thanks.

harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project

[Harikrishna Patnala]

+1

I agree with Rohit on this.

Regards,
Harikrishna

From: Rohit Yadav 
Sent: Monday, April 19, 2021 5:07 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org ; m...@renemoser.net 

Subject: Re: [VOTE] New life to Terraform Provider CloudStack with Apache 
CloudStack project

Hi René,

>From the discussion thread on the terraform provider, you can see some 
>interest and commitment (https://markmail.org/message/xultlpdihdrrg4gq) and 
>quite recently Peter/Fraunhofer and I/ShapeBlue had a meeting with 
>Chris/Hashicorp to discuss and understand the handover/fork of the archived 
>provider repository that Hashicorp is unable to maintain it and we agreed on 
>the next steps; following which I started this voting thread.

I think from a project point of view when integrations are not being maintained 
by external projects, we should have a home within the Apache CloudStack 
community to keep them alive and it makes it easy for ACS contributors to work 
on it. There is nothing wrong with other providers/plugins being brought in by 
contributors if there is interest and demand in the community. We've done this 
before already, when the Kubernetes project removed providers from their 
codebase we created a new home for it within ACS project to be maintained and 
used by the ACS community: 
https://github.com/apache/cloudstack-kubernetes-provider

Can you reconsider your vote? Or, is that a -1 binding vote (i.e. a veto)? 
Thanks.


Regards.


From: Rene Moser 
Sent: Thursday, April 15, 2021 15:05
To: users@cloudstack.apache.org 
Subject: Re: [VOTE] New life to Terraform Provider CloudStack with Apache 
CloudStack project

-1

First, I didn't see much commitment in actively supporting and
maintaining this integration.

Second, there are many integrations, is terraform the one to pick for
using cloudstack from the view of the ASF?
A "plugin" for a software developed outside of ASF? What about puppet,
ansible, chef? The imbalance of this view results to a -1 from me.

Regards
René

On 15.04.21 11:05, Rohit Yadav wrote:
> Hi All,
>
> Following the discussion thread on Terraform [1], I would like to start a 
> vote to gather consensus on the following actions:
>
>1.  Create a new "cloudstack-terraform-provider" repository based on 
> Apache Licence v2.0 using re-licensed codebase of the archived/former 
> terraform cloudstack provider repository: 
> https://github.com/hashicorp/terraform-provider-cloudstack (note: 
> re-licensing from MPL to AL will be done by Hashicorp)
>2.  Request ASF infra to enable issues, PR, and wiki features on the 
> repository
>3.  Work with the community towards any further maintenance, development, 
> and releases of the provider
>4.  Publish official releases on the official registry [2] if/after Apache 
> CloudStack project gets a verified account (published by PMC members with 
> access to the registry, or following guidelines from ASF infra if they've any)
>
> The vote will be open for 120 hours, until Wed 21 April 2021.
> 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)
>
> [1] https://markmail.org/message/iuggxin7kj6ri4hb
> [2] https://registry.terraform.io/browse/providers
>
>
> Regards.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project

[Abhishek Kumar]

+1

From: Rohit Yadav 
Sent: 15 April 2021 14:35
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [VOTE] New life to Terraform Provider CloudStack with Apache 
CloudStack project

Hi All,

Following the discussion thread on Terraform [1], I would like to start a vote 
to gather consensus on the following actions:

  1.  Create a new "cloudstack-terraform-provider" repository based on Apache 
Licence v2.0 using re-licensed codebase of the archived/former terraform 
cloudstack provider repository: 
https://github.com/hashicorp/terraform-provider-cloudstack (note: re-licensing 
from MPL to AL will be done by Hashicorp)
  2.  Request ASF infra to enable issues, PR, and wiki features on the 
repository
  3.  Work with the community towards any further maintenance, development, and 
releases of the provider
  4.  Publish official releases on the official registry [2] if/after Apache 
CloudStack project gets a verified account (published by PMC members with 
access to the registry, or following guidelines from ASF infra if they've any)

The vote will be open for 120 hours, until Wed 21 April 2021.
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)

[1] https://markmail.org/message/iuggxin7kj6ri4hb
[2] https://registry.terraform.io/browse/providers


Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




abhishek.ku...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Cannot start stopped VMs

[Fariborz Navidan]

Hello,

Today, I just updated SSL certificate and it failed re-deploying system
VMs. Also, when I try to start a VM that is stopped, it fails with message:
Unable to create deployment due to insufficient capacity. I couldn't find
the reason from logs. I have uploaded  partial management server and agent
logs.

https://www.r9host.com/log/management-server.log
https://www.r9host.com/log/agent.log

It is a mission critical issue for us. I would appreciate if you guys check
the logs and let us know what we can do to fix this issue.

Thanks.

Re: [VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project

[Rene Moser]

Hi Rohit

On 19.04.21 13:37, Rohit Yadav wrote:

Hi René,

 From the discussion thread on the terraform provider, you can see some 
interest and commitment (https://markmail.org/message/xultlpdihdrrg4gq) and 
quite recently Peter/Fraunhofer and I/ShapeBlue had a meeting with 
Chris/Hashicorp to discuss and understand the handover/fork of the archived 
provider repository that Hashicorp is unable to maintain it and we agreed on 
the next steps; following which I started this voting thread.

I think from a project point of view when integrations are not being maintained 
by external projects, we should have a home within the Apache CloudStack 
community to keep them alive and it makes it easy for ACS contributors to work 
on it. There is nothing wrong with other providers/plugins being brought in by 
contributors if there is interest and demand in the community. We've done this 
before already, when the Kubernetes project removed providers from their 
codebase we created a new home for it within ACS project to be maintained and 
used by the ACS community: 
https://github.com/apache/cloudstack-kubernetes-provider

Can you reconsider your vote? Or, is that a -1 binding vote (i.e. a veto)? 
Thanks.


I am still -1 but non-binding,

My point is "we give it a home" is not the same as "we as members of ASF 
care, develop and maintain it".


I would't like it when the ASF becomes a graveyard of unmaintained 
Cloudstack integrations. Looking at 
https://github.com/apache/cloudstack-kubernetes-provider, it doesn't 
look like it gets much care either, there's not even be a release yet.


Regards
René

Re: Enabling nested virtualization

[Pearl d'Silva]

Hi Fariborz,

To enable nested virtualization on the KVM hypervisor hosts:

  1.  shutoff the running VMs on the respective host.
  2.  Create the following file: /etc/modprobe.d/kvm-nested.conf and add the 
following details to the file: options kvm-intel nested=1
  3.  Remove and re-add the kvm kernel module,
modprobe -r kvm_intel
modprobe -a kvm_intel
  4.  Verify the content of /sys/module/kvm_intel/parameters/nested file to 
validate if nested virtualization has been enabled

Add required details in the agent.properties file as stated in the earlier 
emails and restart the cloudstack-agent service.
Start the VM(s) - you should now see the vmx flag in your guest VM(s).

Thanks,
Pearl

From: Nicolas Vazquez 
Sent: Monday, April 19, 2021 9:33 AM
To: users@cloudstack.apache.org 
Subject: Re: Enabling nested virtualization

Hi Fariborz,

Can you explore if it can be enabled by explicitly sending metada to that VM. I 
would suggest passing '' by:

  *   Set the configuration 'enable.additional.vm.configuration' to true
  *   Set the configuration 'allow.additional.vm.configuration.list.kvm' to 
'cpu'
  *   Encode the text to be passed, as: 
'%3Ccpu%20mode%3D%27host-model%27%20check%3D%27partial%27%2F%3E'
  *   Stop and update the virtual machine, passing the encoded text as the 
extraconfig parameter: update virtualmachine 
extraconfig="%3Ccpu%20mode%3D%27host-model%27%20check%3D%27partial%27%2F%3E" 
id=

More information about this feature: 
https://www.shapeblue.com/cloudstack-feature-first-look-enable-sending-of-arbitrary-configuration-data-to-vms/


Regards,

Nicolas Vazquez


From: Fariborz Navidan 
Sent: Sunday, April 18, 2021 7:50 PM
To: users@cloudstack.apache.org 
Subject: Re: Enabling nested virtualization

Hello,

I just added the following lines to agent.properties file:

guest.cpu.mode=host-model
guest.cpu.features=vmx

And stopped/started the VM. The CPU model name inside /proc/cpuinfo on the
VM reads exac;y as the CPU model of the physical host but it still does not
expose the vmx feature to the VM. The output of command "cat /proc/cpuinfo
| grep vmx" is empty.

Please advise.

Regards.

On Sun, Apr 18, 2021 at 6:13 PM Andrija Panic 
wrote:

> I would use imagination and imagine that in order to apply a specific CPU
> model (and expose flags) to the needed VMs (ps aux | grep i-2-XXX-VM)  -
> you will need to stop/start just the wanted VMs.
>
> Otherwise, after agent.properties change, it is required to restart the
> agent, for obvious reasons.
>
> Best,
>
> On Sun, 18 Apr 2021 at 13:22, Fariborz Navidan 
> wrote:
>
> > Hi,
> >
> > Should I stop/start all VMs or just the one I want to be deployed with
> VTX
> > flag?
> >
> > Regards.
> >
> > On Sun, Apr 18, 2021 at 1:49 AM Andrija Panic 
> > wrote:
> >
> > > Try with the custom CPU model inside the agents.properties, making sure
> > you
> > > pass the VTX and other CPU flags. (you can defined CPU model, or use
> some
> > > CPU model + some more CPU flags (i.e. VTX)
> > > Never tested, but is supposed to work that way.
> > >
> > > Best,
> > >
> > > On Sat, 17 Apr 2021 at 21:58, Fariborz Navidan 
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > How can I enable nested virtualization on KVM hypervisor so that a
> > guest
> > > VM
> > > > supports nested Intel-VTX?
> > > >
> > > > TIA
> > > >
> > >
> > >
> > > --
> > >
> > > Andrija Panić
> > >
> >
>
>
> --
>
> Andrija Panić
>

nicolas.vazq...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




pearl.dsi...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: [VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project

[Rohit Yadav]

Hi René,

>From the discussion thread on the terraform provider, you can see some 
>interest and commitment (https://markmail.org/message/xultlpdihdrrg4gq) and 
>quite recently Peter/Fraunhofer and I/ShapeBlue had a meeting with 
>Chris/Hashicorp to discuss and understand the handover/fork of the archived 
>provider repository that Hashicorp is unable to maintain it and we agreed on 
>the next steps; following which I started this voting thread.

I think from a project point of view when integrations are not being maintained 
by external projects, we should have a home within the Apache CloudStack 
community to keep them alive and it makes it easy for ACS contributors to work 
on it. There is nothing wrong with other providers/plugins being brought in by 
contributors if there is interest and demand in the community. We've done this 
before already, when the Kubernetes project removed providers from their 
codebase we created a new home for it within ACS project to be maintained and 
used by the ACS community: 
https://github.com/apache/cloudstack-kubernetes-provider

Can you reconsider your vote? Or, is that a -1 binding vote (i.e. a veto)? 
Thanks.


Regards.


From: Rene Moser 
Sent: Thursday, April 15, 2021 15:05
To: users@cloudstack.apache.org 
Subject: Re: [VOTE] New life to Terraform Provider CloudStack with Apache 
CloudStack project

-1

First, I didn't see much commitment in actively supporting and
maintaining this integration.

Second, there are many integrations, is terraform the one to pick for
using cloudstack from the view of the ASF?
A "plugin" for a software developed outside of ASF? What about puppet,
ansible, chef? The imbalance of this view results to a -1 from me.

Regards
René

On 15.04.21 11:05, Rohit Yadav wrote:
> Hi All,
>
> Following the discussion thread on Terraform [1], I would like to start a 
> vote to gather consensus on the following actions:
>
>1.  Create a new "cloudstack-terraform-provider" repository based on 
> Apache Licence v2.0 using re-licensed codebase of the archived/former 
> terraform cloudstack provider repository: 
> https://github.com/hashicorp/terraform-provider-cloudstack (note: 
> re-licensing from MPL to AL will be done by Hashicorp)
>2.  Request ASF infra to enable issues, PR, and wiki features on the 
> repository
>3.  Work with the community towards any further maintenance, development, 
> and releases of the provider
>4.  Publish official releases on the official registry [2] if/after Apache 
> CloudStack project gets a verified account (published by PMC members with 
> access to the registry, or following guidelines from ASF infra if they've any)
>
> The vote will be open for 120 hours, until Wed 21 April 2021.
> 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)
>
> [1] https://markmail.org/message/iuggxin7kj6ri4hb
> [2] https://registry.terraform.io/browse/providers
>
>
> Regards.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: Uploading Blog Post

[Ivet Petrova]

Hello again and Happy Monday Everyone,

Once again - can somebody give me some guidance on this?

Kind regards,


ivet.petr...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

On 9 Apr 2021, at 12:48, Ivet Petrova 
mailto:ivet.petr...@shapeblue.com>> wrote:

Hi,

Can somebody help me on how a new blog posts can be uploaded on the CloudStack 
blog?
Is there any backend which is used, or only code?

Thanks a lot on advance!

Kind regards,


ivet.petr...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue