Re: Official event location - CloudStack European Users Group 2023

[Ivet Petrova]

Awesome Jamie! As we have a location now people can start booking their 
accommodation in advance.
Look forward to meet everyone!

Kind regards,


 

On 18 Jan 2023, at 9:01, Jamie Pell 
mailto:jamie.p...@shapeblue.com>> wrote:

Hi everyone,

I am pleased to share that the community has come together and decided on the 
location for this year’s CloudStack European Users Group 2023 on 4th May.

The event will be taking place in: Gandhi Room at Cifas, Tavistock Square, 7-12 
Lynton House, London, WC1H 9LT.

A gentle reminder that you can register for the event on the Eventbrite event 
page.

Kind regards,

Re: Unable to launch VM dur to InsufficientNetworkCapacityException

[Leandro Ramos]

Thank you, Vivek.

It works now.


Em 17/01/2023 17:36, Vivek Kumar escreveu:

Hello,

Please check your guest VLAN Range, looks like it’s not there, so when 
you create any isolate network or VPC style network, It configure a 
public NIC and a guest NIC and guest Nic is configured on a random 
VLAN  (The VLAN which you assign while creating the zone ).


From the logs you provided -


1.
eleased for network id 206 as a part of network implement
2.
com.cloud.exception.InsufficientVirtualNetworkCapacityException:
*Unable to allocate vnet as a part of network Network *{"id": 206,
"name": "MyIsolatedNe
3.
twork", "uuid": "298ddc5f-bb2a-498e-a15f-7011dfa2e4dc",
"networkofferingid": 9} implement Scope=interface
com.cloud.dc.DataCenter; id=1



Click on Zone, and then -> click on physical network —> then click on 
the network where you have defined - traffic type guest , and then —> 
traffic type —> select guest —> then edit the setting where you will 
have option to define VLAN Range,


Note - These VLAN should be allowed on the physical switch port where 
your host is connected, if you have multiple hosts


i.e





  Vivek Kumar

Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies





vivek.ku...@indiqus.com

www.indiqus.com 






On 18-Jan-2023, at 1:18 AM, Leandro Ramos  wrote:

Hi :)

I'm trying to launch an instance on Cloudstack, but I got some 
errors. There's a pastebin with a "grep -i network 
/var/log/cloudstack/management/management-server.log" result here: 
https://pastebin.com/KY6FWm3t


Anyone can help me?

In fact I didn't understand very well how to create an isolated 
network (even after seeing some tutorials and videos), so I have 
created one with default values:





Thank you.




/This message is intended only for the use of the individual or entity 
to which it is addressed and may contain confidential and/or 
privileged information. If you are not the intended recipient, please 
delete the original message and any copy of it from your computer 
system. You are hereby notified that any dissemination, distribution 
or copying of this communication is strictly prohibited unless proper 
authorization has been obtained for such action. If you have received 
this communication in error, please notify the sender immediately. 
Although IndiQus attempts to sweep e-mail and attachments for viruses, 
it does not guarantee that both are virus-free and accepts no 
liability for any damage sustained as a result of viruses./

Re: Unable to launch VM dur to InsufficientNetworkCapacityException

[Vivek Kumar]

Hello, 

Please check your guest VLAN Range, looks like it’s not there, so when you 
create any isolate network or VPC style network, It configure a public NIC and 
a guest NIC and guest Nic is configured on a random VLAN  (The VLAN which you 
assign while creating the zone ).  

>From the logs you provided - 


eleased for network id 206 as a part of network implement
com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to 
allocate vnet as a part of network Network {"id": 206, "name": "MyIsolatedNe
twork", "uuid": "298ddc5f-bb2a-498e-a15f-7011dfa2e4dc", "networkofferingid": 9} 
implement Scope=interface com.cloud.dc.DataCenter; id=1


Click on Zone, and then -> click on physical network —> then click on the 
network where you have defined - traffic type guest , and then —> traffic type 
—> select guest —> then edit the setting where you will have option to define 
VLAN Range,  

Note - These VLAN should be allowed on the physical switch port where your host 
is connected, if you have multiple hosts 

i.e 






Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 18-Jan-2023, at 1:18 AM, Leandro Ramos  wrote:
> 
> Hi :)
> 
> I'm trying to launch an instance on Cloudstack, but I got some errors. 
> There's a pastebin with a "grep -i network 
> /var/log/cloudstack/management/management-server.log" result here: 
> https://pastebin.com/KY6FWm3t 
> Anyone can help me?
> 
> In fact I didn't understand very well how to create an isolated network (even 
> after seeing some tutorials and videos), so I have created one with default 
> values:
> 
> 
> 
> 
> 
> Thank you.
> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Unable to launch VM dur to InsufficientNetworkCapacityException

[Leandro Ramos]

Hi :)

I'm trying to launch an instance on Cloudstack, but I got some errors. 
There's a pastebin with a "grep -i network 
/var/log/cloudstack/management/management-server.log" result here: 
https://pastebin.com/KY6FWm3t


Anyone can help me?

In fact I didn't understand very well how to create an isolated network 
(even after seeing some tutorials and videos), so I have created one 
with default values:



Thank you.

RE: sysvm live migration 4.17.2

[Piotr Pisz]

Hey,

That's right, recreating systemvm fixed the problem.

Regards,
Piotr

-Original Message-
From: Rohit Yadav  
Sent: Tuesday, January 17, 2023 8:59 AM
To: users@cloudstack.apache.org
Subject: Re: sysvm live migration 4.17.2

Hi Piotr,

You've hit a bug, wherein somehow the systemvm.iso wasn't ejected for the 
4.17.0.0 systemvm. You can either do it manually on the KVM host (virsh 
change-media   --eject) or you can restart the 
network with cleanup=true or in case of systemvms just destroy them.


Regards.


From: Wei ZHOU 
Sent: Sunday, January 15, 2023 04:09
To: users@cloudstack.apache.org 
Subject: Re: sysvm live migration 4.17.2

Looks like a bug.
systemvm.iso does not exist on 4.17+,  it should be ejected when you patched 
the system vms.
Can you retry after ejecting iso by "virsh change-media" ?

-Wei


 

On Saturday, 14 January 2023, Piotr Pisz  wrote:

> Hi,
>
> After upgrading CS from 4.17.0 to 4.17.2 I have a strange symptom, 
> live migration system vm is not working. It ends with the message:
>
> Exception during migrate: org.libvirt.LibvirtException: Cannot access 
> storage file '/usr/share/cloudstack-common/vms/systemvm.iso': No such 
> file or directory
>
> In the directory it looks like this:
>
> [root@psc1 vms]# ls -l
> razem 281080
> -rw-r--r-- 1 root root 98871867 12-14 06:55 agent.zip
> -rw-r--r-- 1 root root   136442 12-14 06:55 cloud-scripts.tgz
> -rw-r--r-- 1 root root 4452 12-14 06:55 patch-sysvms.sh
> -rw-r--r-- 1 root root 94400512 2021-11-24  systemvm.iso.bak
> -rw-r--r-- 1 root root 94404608 2021-11-21  systemvm.iso.bak~
>
> Other than that, everything works as expected, I managed to path the 
> system vm version from 4.16 to 4.17 without any problems.
>
> Any suggestions? 😊
>
> Best regards,
> Piotr
>
>