Re: New PMC member: Suresh Anaparti

[Slavka Peleva]

Congratulations Suresh!

Best Regards,
Slavka

On Wed, 18 Sep 2024 at 22:31, Nicolas Vazquez 
wrote:

> Congratulations Suresh!
>
> Regards,
> Nicolas Vazquez
>
>
> From: Rohit Yadav 
> Date: Wednesday, 18 September 2024 at 07:52
> To: dev , users 
> Subject: New PMC member: Suresh Anaparti
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Suresh Anaparti to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Suresh has contributed in the past and has shown effort to make the
> project run smoothly. He also has served as the release manager for
> CloudStack releases 4.16.1.0 and 4.19.1.0.
>
> Please join me in congratulating Suresh
>
> Regards,
> Rohit Yadav
>
>
>
>

Re: Deleting compute offering

[Slavka Peleva]

Hi Jimmy,

Disabling disk/service offerings invokes the delete API call and sets the
offering as "Inactive. Before 4.19 those offerings weren't visible when
listing service/disk offerings. There is an enhancement that allows the
user to activate the deleted (Inactive) offerings - PR #8821


Best regards,
Slavka

On Thu, Sep 5, 2024 at 1:48 PM  wrote:

> Me again, I just did a test an this api call deactivates the offering. It
> looks like deleting a service offering is not possible.
> Why is putting a service offering inactive not working for you? It will not
> show up in the UI.
>
> -Ursprüngliche Nachricht-
> Von: m...@swen.io 
> Gesendet: Donnerstag, 5. September 2024 12:42
> An: users@cloudstack.apache.org
> Betreff: AW: Deleting compute offering
>
> Hi Jimmy,
>
> there is an api call deleteServiceOffering
>
>
> https://cloudstack.apache.org/api/apidocs-4.19/apis/deleteServiceOffering.ht
> ml
> 
>
> regards,
> Swen
>
> -Ursprüngliche Nachricht-
> Von: Jimmy Huybrechts 
> Gesendet: Donnerstag, 5. September 2024 12:11
> An: users@cloudstack.apache.org
> Betreff: Deleting compute offering
>
> Hi,
>
> Using 4.19.1, but seems I cannot delete a compute offering I made, only
> disable it.
>
> I checked with show instances that it’s not in use, and also tried to do it
> with one I created like 30 sec ago.
>
> I assume you can delete them on the gui in some way? As otherwise this will
> be a mess if you can only disable one you don’t need anymore.
>
> --
> Jimmy
>
>
>
>
>

Re: add additional KVM primary storage through CloudMonkey

[Slavka Peleva]

Hi Jordan,

I was able to add local storage via Cloudmonkey. There is no need to
provide the scope, it will be set depending on the URL scheme (it has to be
"file")

(admin) 🐵 > create storagepool zoneid=07d64765-3123-4fc2-b947-25d2c36f5bb4
> name=test provider=DefaultPrimary
> podid=0af34b96-e88d-440e-a6bd-c4e8aab4aa4a
> clusterid=49db6a16-2f6c-4583-9d07-37ccceb248ae  url=file://
> 10.2.32.244/var/lib/libvirt/images
> {
>   "storagepool": {
> "clusterid": "49db6a16-2f6c-4583-9d07-37ccceb248ae",
> "clustername": "Cluster-A-1",
> "created": "2024-08-12T14:59:53+0300",
> "disksizeallocated": 0,
> "disksizetotal": 41001418752,
> "hasannotations": false,
> "hypervisor": "KVM",
> "id": "3714d38e-1842-4689-a162-0c14df06934d",
> "ipaddress": "10.2.32.244",
> "istagarule": false,
> "name": "test",
> "overprovisionfactor": "2.0",
> "path": "/var/lib/libvirt/images",
> "podid": "0af34b96-e88d-440e-a6bd-c4e8aab4aa4a",
> "podname": "Pod-A",
> "provider": "DefaultPrimary",
> "scope": "HOST",
> "state": "Up",
> "type": "Filesystem",
> "zoneid": "07d64765-3123-4fc2-b947-25d2c36f5bb4",
> "zonename": "Zone-A"
>   }
> }


Via UI - probably you're right that there is a bug. When the data is
fetched it shows only the host from the first cluster in the list.

Best regards,
Slavka

On Mon, Aug 12, 2024 at 12:37 PM jordan j  wrote:

> Hello everyone,
>
> The docs claim that this can be done from UI and from manually modifying
> the agent on the KVM host but I wonder if it can be done from CLI? Here is
> my experience so far (CS 4.19.1.0, one pod with mixed XCP and KVM
> clusters).
>
> - Manually modifying the agent: It works
> - From Primary storage UI: the KVM host cannot be selected even though a
> KVM cluster is selected above. Actually the host UI field can only select
> one of all the hosts in the zone and that host is not part of the selected
> cluster. I wonder if that is a bug?
> - Cloudmonkey Create StoragePool command:
> https://cloudstack.apache.org/api/apidocs-4.19/apis/createStoragePool.html
> .
> When selecting a scope argument there is no HOST value to select (that is
> the requirement for local disk) but only Zone and Cluster. Also the api
> command is poorly documented, for example I have no clue what the "details"
> argument is used for.
>
> Has anyone had more success with UI and/or CLI?
>
> Best regards,
> Jordan
>

Re: Unable to create new VMs or Console Proxy

[Slavka Peleva]

Hi Marty,

My guess here is that the template `13f86c22-a422-459b-90d2-450a145724b3`
from which you are creating a VM is missing on your primary storage, but
CloudStack has the information that it is there. To confirm this you can
check:
- if `13f86c22-a422-459b-90d2-450a145724b3` exist on your primary storage
- from the CloudStack DB check if the template was downloaded on your
primary storage - `select * from template_spool_ref where
local_path="13f86c22-a422-459b-90d2-450a145724b3";`
Best regards,
Slavka

On Tue, Jul 9, 2024 at 10:39 AM Wei ZHOU  wrote:

> Hi Marty,
>
> It looks like the issue is not caused by server capacity, but storage.
>
> 2024-07-09 06:57:20,304 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> (Work-Job-Executor-4:ctx-61e43dea job-7483/job-7492 ctx-440bf369)
> (logid:c56ddd5b) ClusterScopeStoragePoolAllocator is returning [0]
> suitable storage pools [[]].
> 2024-07-09 06:57:20,306 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
> (Work-Job-Executor-4:ctx-61e43dea job-7483/job-7492 ctx-440bf369)
> (logid:c56ddd5b) Could not find any zone wide storage pool that
> matched with any of the following tags [[]].
> 2024-07-09 06:57:20,308 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> (Work-Job-Executor-4:ctx-61e43dea job-7483/job-7492 ctx-440bf369)
> (logid:c56ddd5b) ZoneWideStoragePoolAllocator is returning [0]
> suitable storage pools [[]].
> 2024-07-09 06:57:20,308 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-4:ctx-61e43dea job-7483/job-7492 ctx-440bf369)
> (logid:c56ddd5b) No suitable pools found for volume:
> Vol[1000|name=ROOT-598|vm=598|ROOT] under cluster: 3
> 2024-07-09 06:57:20,308 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-4:ctx-61e43dea job-7483/job-7492 ctx-440bf369)
> (logid:c56ddd5b) No suitable pools found
> 2024-07-09 06:57:20,308 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-4:ctx-61e43dea job-7483/job-7492 ctx-440bf369)
> (logid:c56ddd5b) No suitable storagePools found under this Cluster: 3
>
>
>
> On Tue, Jul 9, 2024 at 9:27 AM Marty Godsey  wrote:
> >
> > I am also getting this which is strange: Whey does it say there is not
> enough capacity.
> >
> > 2024-07-09 01:08:22,201 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) VM instance
> {"id":466,"instanceName":"v-466-VM","type":"ConsoleProxy","uuid":"94f2f2cc-15c9-41a7-a678-a9d1cd65d14a"}
> state transited from [Starting] to [Starting] with event [OperationRetry].
> VM's original host: null, new host: Host
> {"id":5,"name":"csc-n1","type":"Routing","uuid":"52950eed-9931-410e-a482-7df361b14a50"},
> host before state transition: null
> > 2024-07-09 01:08:22,214 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) Hosts's actual total CPU: 193600 and CPU after applying
> overprovisioning: 387200
> > 2024-07-09 01:08:22,214 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) We are allocating VM, increasing the used capacity of this
> host:5
> > 2024-07-09 01:08:22,214 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) Current Used CPU: 41400 , Free CPU:345800 ,Requested CPU:
> 500
> > 2024-07-09 01:08:22,214 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) Current Used RAM: (49.00 GB) 52613349376 , Free
> RAM:(687.04 GB) 737701920768 ,Requested RAM: (1.00 GB) 1073741824
> > 2024-07-09 01:08:22,214 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) CPU STATS after allocation: for host: 5, old used: 41400,
> old reserved: 0, actual total: 193600, total with overprovisioning: 387200;
> new used:41900, reserved:0; requested cpu:500,alloc_from_last:false
> > 2024-07-09 01:08:22,214 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) RAM STATS after allocation: for host: 5, old used: (49.00
> GB) 52613349376, old reserved: (0 bytes) 0, total: (736.04 GB)
> 790315270144; new used: (50.00 GB) 53687091200, reserved: (0 bytes) 0;
> requested mem: (1.00 GB) 1073741824,alloc_from_last:false
> > 2024-07-09 01:08:22,217 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) Host: 5 has cpu capability (cpu:88, speed:2200) to support
> requested CPU: 1 and requested speed: 500
> > 2024-07-09 01:08:22,217 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-81:ctx-db736df7 job-6013/job-6205 ctx-fa9daf4b)
> (logid:7fa21822) Checking if host: 5 has enough capacity for requested CPU:
> 500 and requested RAM: (1.00 GB) 1073741824 , cpuOverprovisioningFactor: 2.0
> > 2024-07-09 01:08:22,218 DEBUG [c.c.c.CapacityManagerImpl]

Re: CreateBackupCmd not starting due to "Cannot find login credentials for HYPERVISOR"

[Slavka Peleva]

Hi Andreas,

I'm not sure why your host details are missing the username for both hosts.
Here are mine:

- the first one is of a host added with ssh key
| 917056 |  31 | Host.OS.Kernel.Version |
4.18.0-305.3.1.el8_4.x86_64  |
| 917057 |  31 | com.cloud.network.Networks.RouterPrivateIpStrategy |
HostLocal|
| 917058 |  31 | Host.OS.Version|
8.7  |
| 917059 |  31 | host.volume.encryption |
true |
| 917060 |  31 | secured|
true |
| 917061 |  31 | Host.OS|
Rocky Linux  |
| 917063 |  31 | password   |
   |
| 917069 |  31 | username   |
root |

- and this one with username and password
|125 |   9 | Host.OS.Kernel.Version |
4.18.0-305.3.1.el8_4.x86_64  |
|126 |   9 | com.cloud.network.Networks.RouterPrivateIpStrategy |
HostLocal|
|127 |   9 | Host.OS.Version|
8.7  |
|128 |   9 | secured|
true |
|129 |   9 | Host.OS|
Rocky Linux  |
|133 |   9 | host.uefi.enable   |
true |
|137 |   9 | password   |
p7swLiGnxUq0gg1ZwVqZgPeZrqIdWPUj |
|143 |   9 | username   |
root

According to the code, the username or password is needed (but I guess it
won't work without both) for the operations - take a backup, restore a VM
from a backup and restore a volume.

Best regards,
Slavka

On Thu, Apr 11, 2024 at 7:04 PM Andreas S. Kerber 
wrote:

> Hi Slavka,
>
> thanks for your answer! Indeed the hosts where not added with
> username/password and host_details has no credentials.
> Can you share the name of the required attributes? This is my current
> host_details table:
>
>
> mysql> select * from  host_details;
>
> +-+-++--+
> | id  | host_id | name   |
> value|
>
> +-+-++--+
> | 171 |  10 | Host.OS.Kernel.Version |
> 5.15.0-204.147.6.3.el9uek.x86_64 |
> | 172 |  10 | com.cloud.network.Networks.RouterPrivateIpStrategy |
> HostLocal|
> | 173 |  10 | Host.OS.Version|
> 9.3  |
> | 174 |  10 | host.volume.encryption |
> true |
> | 175 |  10 | secured|
> true |
> | 176 |  10 | Host.OS| Red
> Hat Enterprise Linux |
> | 201 |  15 | Host.OS.Kernel.Version |
> 5.15.0-204.147.6.3.el9uek.x86_64 |
> | 202 |  15 | com.cloud.network.Networks.RouterPrivateIpStrategy |
> HostLocal|
> | 203 |  15 | Host.OS.Version|
> 9.3  |
> | 204 |  15 | host.volume.encryption |
> true |
> | 205 |  15 | secured|
> true |
> | 206 |  15 | Host.OS| Red
> Hat Enterprise Linux |
>
> +-+-+--------+--+
> 12 rows in set (0.01 sec)
>
>
> Am Thu, Apr 11, 2024 at 04:20:22PM +0300 schrieb Slavka Peleva:
> > Hi Andreas,
> >
> > The Networker plugin is trying to get the credentials for the host from
> the
> > DB table `host_details` and if one is missing - username/password - you
> > will get this error message. If only the password is missing from the
> table
> > for that host, maybe you have added the host with the ssh key.
> >
> > Best regards,
> > Slavka
> >
> > On Wed, Apr 10, 2024 at 9:02 PM Andreas S. Kerber  >
> > wrote:
> >
> > &

Re: CreateBackupCmd not starting due to "Cannot find login credentials for HYPERVISOR"

[Slavka Peleva]

Hi Andreas,

The Networker plugin is trying to get the credentials for the host from the
DB table `host_details` and if one is missing - username/password - you
will get this error message. If only the password is missing from the table
for that host, maybe you have added the host with the ssh key.

Best regards,
Slavka

On Wed, Apr 10, 2024 at 9:02 PM Andreas S. Kerber 
wrote:

> Hi,
>
> I'm trying to get VM backups of 2 node KVM cluster working (using
> networker). Wwhen trying to start a backup I'm immediatly getting a error
> message about missing hypervisor login credentials. Maybe I overlooked
> someting in the documentation but I can't figure out where these login
> credentials are configured. Can anybody give me a hint?
>
>
> Here's the log of one of my CreateBackupCmd Jobs:
>
> 2024-04-10 17:41:10,476 INFO  [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-30:ctx-c3bb37fe job-1549) (logid:b1913df8) Add job-1549
> into job monitoring
>
> 2024-04-10 17:41:10,482 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (qtp1278254413-402:ctx-dddc56ad ctx-33b958e5) (logid:1dda45c8) submit async
> job-1549, details: AsyncJobVO: {id:1549, userId: 4, accountId: 4,
> instanceType: Backup, instanceId: 81, cmd:
> org.apache.cloudstack.api.command.user.backup.CreateBackupCmd, cmdInfo:
> {"virtualmachineid":"e338c774-6693-485f-9746-e3d172665af5","response":"json","ctxUserId":"4","httpmethod":"GET","ctxStartEventId":"3293","id":"81","ctxDetails":"{\"interface
> com.cloud.vm.VirtualMachine\":\"e338c774-6693-485f-9746-e3d172665af5\"}","ctxAccountId":"4","cmdEventType":"BACKUP.CREATE"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 345049358837, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: null, removed: null}
>
> 2024-04-10 17:41:10,485 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-30:ctx-c3bb37fe job-1549) (logid:e4d20d53) Executing
> AsyncJobVO: {id:1549, userId: 4, accountId: 4, instanceType: Backup,
> instanceId: 81, cmd:
> org.apache.cloudstack.api.command.user.backup.CreateBackupCmd, cmdInfo:
> {"virtualmachineid":"e338c774-6693-485f-9746-e3d172665af5","response":"json","ctxUserId":"4","httpmethod":"GET","ctxStartEventId":"3293","id":"81","ctxDetails":"{\"interface
> com.cloud.vm.VirtualMachine\":\"e338c774-6693-485f-9746-e3d172665af5\"}","ctxAccountId":"4","cmdEventType":"BACKUP.CREATE"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 345049358837, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: null, removed: null}
>
> 2024-04-10 17:41:10,519 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-30:ctx-c3bb37fe job-1549) (logid:e4d20d53) Complete async
> job-1549, jobStatus: FAILED, resultCode: 530, result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Cannot
> find login credentials for HYPERVISOR df99ba84-7814-47b8-aa99-dd9553c56b4c"}
>
> {...}
> 2024-04-10 17:41:10,528 INFO  [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-30:ctx-c3bb37fe job-1549) (logid:e4d20d53) Remove
> job-1549 from job monitoring
>
>
> (local)  > list backupofferings
> {
>   "backupoffering": [
> {
>   "allowuserdrivenbackups": true,
>   "created": "2024-04-10T17:08:37+0200",
>   "description": "Networker Instance Backup - 30 days retention",
>   "externalid": "57.0.53.26.0.0.0.0.0.130.19.102.213.182.20.91",
>   "id": "8373b357-6b3f-41d9-8054-873914e95476",
>   "name": "Networker Instance Backup",
>   "zoneid": "c65618bc-0dcf-4f8a-b365-6b0c11750091",
>   "zonename": "RZKE1"
> }
>   ],
>   "count": 1
> }
>
>
> (local)  > list hosts id=df99ba84-7814-47b8-aa99-dd9553c56b4c
> {
>   "count": 1,
>   "host": [
> {
>   "capabilities": "hvm,snapshot",
>   "clusterid": "19939e9e-7588-47e0-82f5-3cd6a634723a",
>   "clustername": "RZKE1_Cluster03",
>   "clustertype": "CloudManaged",
>   "cpuallocated": "4.51%",
>   "cpuallocatedpercentage": "4.51%",
>   "cpuallocatedvalue": 13000,
>   "cpuallocatedwithoverprovisioning": "4.51%",
>   "cpuloadaverage": 0.73,
>   "cpunumber": 96,
>   "cpusockets": 2,
>   "cpuspeed": 3000,
>   "cpuused": "0.6%",
>   "cpuwithoverprovisioning": "288000",
>   "created": "2024-03-05T17:16:05+0100",
>   "details": {
> "Host.OS": "Red Hat Enterprise Linux",
> "Host.OS.Kernel.Version": "5.15.0-204.147.6.3.el9uek.x86_64",
> "Host.OS.Version": "9.3",
> "com.cloud.network.Networks.RouterPrivateIpStrategy": "HostLocal",
> "secured": "true"
>   },
>   "encryptionsupported": true,
>   "events": "PingTimeout; AgentDisconnected; AgentConnected; HostDown;
> Ping; Remove; ShutdownRequested; ManagementServerDown; StartAgentRebalance",
>   "hahost": false,
>   "hasannotations": false,
>   "hostha": {
> "haenable": false,
> "haprovider": "kv

Re: Storage in avoid set

[Slavka Peleva]

Forgot to mention that it fails to deploy the Vritaul router that's why the
deployment of guest VMs fails

2024-02-27 11:24:04,410 DEBUG [c.c.a.m.ClusteredAgentAttache]
(Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
(logid:97976fdd) Seq 1-7417428586279207196: Forwarding Seq
1-7417428586279207196: { Cmd , MgmtId: 187740248600989, via:
1(CLDXEN1XCP3), Ver: v1, Flags: 100111,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"44b911df-3138-414b-9604-e7254372ad9b","origUrl":"
http://download.cloudstack.org/systemvm/4.18/systemvmtemplate-4.18.1-xen.vhd.bz2","uuid":"7752b709-1324-45ed-9132-56994506ad10","id":"328","format":"VHD","accountId":"2","checksum":"{SHA-512}2c9b9d65568ebd144c44b1bc6ad7f9f7671bd096a722e8c2838809706ae508af4ae6cbb2e10bb9db5c7afd00104db5b48ded63c8aea974bf28b1927be02952a1","hvm":"false","displayText":"systemvm-xenserver-4.18.1","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"CLOUDSTACKVOL1","name":"CLOUDSTACKVOL1","id":"1","poolType":"PreSetup","host":"localhost","path":"/CLOUDSTACKVOL1","port":"0","url":"PreSetup://localhost/CLOUDSTACKVOL1/?ROLE=Primary&STOREUUID=CLOUDSTACKVOL1","isManaged":"false"}},"name":"328-2-cd9c893a-f0af-3ac6-8c64-de9ec6723e0a","size":";(4.88
GB)
524288","hypervisorType":"XenServer","bootable":"false","uniqueName":"328-2-cd9c893a-f0af-3ac6-8c64-de9ec6723e0a","directDownload":"false","deployAsIs":"false"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"506d9923-039b-46f1-870c-a0c465fbf714","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"CLOUDSTACKVOL1","name":"CLOUDSTACKVOL1","id":"1","poolType":"PreSetup","host":"localhost","path":"/CLOUDSTACKVOL1","port":"0","url":"PreSetup://localhost/CLOUDSTACKVOL1/?ROLE=Primary&STOREUUID=CLOUDSTACKVOL1","isManaged":"false"}},"name":"ROOT-1133","size":"(4.88
GB) 524288","volumeId":"1182","vmName":"*r-1133-VM*",
"accountId":"49","format":"VHD","provisioningType":"THIN","poolId":"1","id":"1182","deviceId":"0","cacheMode":"NONE","hypervisorType":"XenServer","directDownload":"false","deployAsIs":"false"}},"executeInSequence":"true","options":{},"options2":{},"wait":"0","bypassHostMaintenance":"false"}}]
} to 33622688187677 2024-02-27 11:24:04,451 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-3:null) (logid:) Seq 1-7417428586279207196:
Processing: { Ans: , MgmtId: 187740248600989, via: 1, Ver: v1, Flags: 110,
[{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":"false","details":"com.cloud.utils.exception.CloudRuntimeException:
*Catch Exception com.xensource.xenapi.Types$UuidInvalid :VDI getByUuid for
uuid: 44b911df-3138-414b-9604-e7254372ad9b failed due to The uuid you
supplied was invalid."*,"wait":"0","bypassHostMaintenance":"false"}}] }


On Thu, Feb 29, 2024 at 10:16 AM Slavka Peleva  wrote:

> Hi Alex,
>
> I'm unfamiliar with Xen, but can you check if the template 
> `44b911df-3138-414b-9604-e7254372ad9b`
> exists in your primary storage?  On every first deployment of a VM with a
> new template, CS copies the template from secondary storage to the primary.
> The template may be missing on primary (for some reason) but CloudStack
> keeps the info for the record in the database and tries to create a volume
> from it.
>
> Best regards,
> Slavka
>
> On Thu, Feb 29, 2024 at 8:49 AM Joan g  wrote:
>
>> Hi Wei,
>>
>> Storage also does not have any tags. Attaching logs
>>
>> Alex
>>
>> On Thu, Feb 29, 2024 at 12:09 AM Wei ZHOU  wrote:
>>
>>> Hi Alex,
&g

Re: Storage in avoid set

[Slavka Peleva]

Hi Alex,

I'm unfamiliar with Xen, but can you check if the template
`44b911df-3138-414b-9604-e7254372ad9b`
exists in your primary storage?  On every first deployment of a VM with a
new template, CS copies the template from secondary storage to the primary.
The template may be missing on primary (for some reason) but CloudStack
keeps the info for the record in the database and tries to create a volume
from it.

Best regards,
Slavka

On Thu, Feb 29, 2024 at 8:49 AM Joan g  wrote:

> Hi Wei,
>
> Storage also does not have any tags. Attaching logs
>
> Alex
>
> On Thu, Feb 29, 2024 at 12:09 AM Wei ZHOU  wrote:
>
>> Hi Alex,
>>
>> The tags are the disk offering tags.
>>
>> Anyway , can you share the full log of the job ?
>>
>> -Wei
>>
>> On Wed, Feb 28, 2024 at 6:47 PM Alex Paul 
>> wrote:
>>
>> > Hi Wei,
>> >
>> > No tags are there. I think in logs also its not printing  to any tags:
>> >
>> >
>> > Found pools [[Pool[1|PreSetup]]] that match with tags [[]].
>> >
>> > The VM deployments were fine 2 days before. All in a sudden it started
>> > failing.
>> >
>> >
>> > Alex
>> >
>> > On Wednesday, February 28, 2024, Wei ZHOU 
>> wrote:
>> >
>> > > Agree.
>> > >
>> > > Please also check if the pool has any tags.
>> > >
>> > > -Wei
>> > >
>> > > On Wed, Feb 28, 2024 at 5:31 PM Slavka Peleva
>> > > > > >
>> > > wrote:
>> > >
>> > > > Hi Alex,
>> > > >
>> > > > Sorry for the question but is it possible that the cluster is
>> > disabled? I
>> > > > have faced a similar problem before while testing.
>> > > >
>> > > > Best regards,
>> > > > Slavka
>> > > >
>> > > > On Wed, Feb 28, 2024 at 5:15 PM Alex Paul <
>> alex.chris.jun...@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > > > Hi Swen,
>> > > > >
>> > > > > Yes, only 3TB used out of 15TB and double checked the threshold
>> is at
>> > > > 85%.
>> > > > > :(
>> > > > >
>> > > > > Alex
>> > > > >
>> > > > > On Wed, Feb 28, 2024 at 7:32 PM  wrote:
>> > > > >
>> > > > > > Hi Alex,
>> > > > > >
>> > > > > > is there enough free space on the storage? Check your
>> thresholds in
>> > > > > global
>> > > > > > settings.
>> > > > > >
>> > > > > > Regards,
>> > > > > > Swen
>> > > > > >
>> > > > > > -Ursprüngliche Nachricht-
>> > > > > > Von: Alex Paul 
>> > > > > > Gesendet: Mittwoch, 28. Februar 2024 14:24
>> > > > > > An: users@cloudstack.apache.org
>> > > > > > Betreff: Storage in avoid set
>> > > > > >
>> > > > > > Hello Team,
>> > > > > >
>> > > > > > We've encountered an issue with our cloudstack setup on 3 XCP-ng
>> > > hosts.
>> > > > > > Suddenly, VM deployments are failing.
>> > > > > >
>> > > > > > Our configuration includes a primary storage of type 'presetup'
>> > using
>> > > > > HBA.
>> > > > > > Interestingly, the storage functions properly in the XEN
>> cluster,
>> > > > > allowing
>> > > > > > us to deploy VMs directly in xen.
>> > > > > >
>> > > > > > However, in cloudstack, deployments are failing with the
>> following
>> > > > logs:
>> > > > > > "StoragePool is in avoid set, skipping this pool."
>> > > > > >
>> > > > > > Could someone please provide guidance on why it's in the avoid
>> set
>> > > and
>> > > > > how
>> > > > > > we can remove it from there?
>> > > > > >
>> > > > > > Full logs are provided below for reference.
>> > > > > >
>> > > > > >
>> > > > > > 024-02-27 11:24:04,879 DEBUG
>> > > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
>>

Re: Storage in avoid set

[Slavka Peleva]

Hi Alex,

Sorry for the question but is it possible that the cluster is disabled? I
have faced a similar problem before while testing.

Best regards,
Slavka

On Wed, Feb 28, 2024 at 5:15 PM Alex Paul 
wrote:

> Hi Swen,
>
> Yes, only 3TB used out of 15TB and double checked the threshold is at 85%.
> :(
>
> Alex
>
> On Wed, Feb 28, 2024 at 7:32 PM  wrote:
>
> > Hi Alex,
> >
> > is there enough free space on the storage? Check your thresholds in
> global
> > settings.
> >
> > Regards,
> > Swen
> >
> > -Ursprüngliche Nachricht-
> > Von: Alex Paul 
> > Gesendet: Mittwoch, 28. Februar 2024 14:24
> > An: users@cloudstack.apache.org
> > Betreff: Storage in avoid set
> >
> > Hello Team,
> >
> > We've encountered an issue with our cloudstack setup on 3 XCP-ng hosts.
> > Suddenly, VM deployments are failing.
> >
> > Our configuration includes a primary storage of type 'presetup' using
> HBA.
> > Interestingly, the storage functions properly in the XEN cluster,
> allowing
> > us to deploy VMs directly in xen.
> >
> > However, in cloudstack, deployments are failing with the following logs:
> > "StoragePool is in avoid set, skipping this pool."
> >
> > Could someone please provide guidance on why it's in the avoid set and
> how
> > we can remove it from there?
> >
> > Full logs are provided below for reference.
> >
> >
> > 024-02-27 11:24:04,879 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671
> >  ctx-02929e21) (logid:97976fdd) Looking for pools in dc [1], pod [1] and
> > cluster [1]. Disabled pools will be ignored.
> > 2024-02-27 11:24:04,881 DEBUG
> [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671
> >  ctx-02929e21) (logid:97976fdd) Found pools [[Pool[1|PreSetup]]] that
> > match with tags [[]].
> > 2024-02-27 11:24:04,885 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx
> > -02929e21) (logid:97976fdd) Checking if storage pool is suitable, name:
> > CLOUDSTACKVOL1 ,poolId: 1
> > 2024-02-27 11:24:04,885 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) StoragePool is in avoid set, skipping this pool
> > 2024-02-27 11:24:04,885 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) ClusterScopeStoragePoolAllocator is returning [0]
> > suitable storage pools [[]].
> > 2024-02-27 11:24:04,891 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) ZoneWideStoragePoolAllocator is returning [0] suitable
> > storage pools [[]].
> > 2024-02-27 11:24:04,891 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) No suitable pools found for volume:
> > Vol[1182|name=ROOT-1133|vm=1133|ROOT] under cluster: 1
> > 2024-02-27 11:24:04,891 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) No suitable pools found
> > 2024-02-27 11:24:04,891 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) No suitable storagePools found under this Cluster: 1
> > 2024-02-27 11:24:04,898 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) Could not find suitable Deployment Destination for this
> > VM under any clusters, returning.
> > 2024-02-27 11:24:04,900 DEBUG [c.c.d.FirstFitPlanner]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) Searching all possible resources under this Zone: 1
> > 2024-02-27 11:24:04,903 DEBUG [c.c.d.FirstFitPlanner]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) Listing clusters in order of aggregate capacity, that
> > have (at least one host with) enough CPU and RAM capacity under this
> Zone: 1
> > 2024-02-27 11:24:04,910 DEBUG [c.c.d.FirstFitPlanner]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) Removing from the clusterId list these clusters from
> avoid
> > set: [1]
> > 2024-02-27 11:24:04,911 DEBUG [c.c.d.FirstFitPlanner]
> > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx-02929e21)
> > (logid:97976fdd) No clusters found after removing disabled clusters and
> > clusters in avoid list, returning.
> >
> >
> >
> > Alexi
> >
> >
> >
>

Re: ha checks on kvm hosts running even with ha disabled

[Slavka Peleva]

Unfortunately, there is no check if the HA is enabled/disabled in the
agent's code. The `reboot.host.and.alert.management.on.heartbeat.timeout`
property is enabled by default and only manually you can disable it.

Best regards,
Slavka

On Tue, Feb 20, 2024 at 10:14 AM  wrote:

> Hi Slavka,
>
> thx for your reply!
>
> Do you know the reason why KVMHAMonitor will be initialized even when host
> ha has been disabled by UI?
> From an admin point of view
> reboot.host.and.alert.management.on.heartbeat.timeout=false should be set
> automatically when you disable host ha. Is there a reason for not doing it?
>
> Regards,
> Swen
>
> -Ursprüngliche Nachricht-
> Von: Slavka Peleva 
> Gesendet: Dienstag, 20. Februar 2024 08:50
> An: users@cloudstack.apache.org
> Betreff: Re: ha checks on kvm hosts running even with ha disabled
>
> Hi Swen,
>
> The KVMHAMonitor is initialised here
> <
> https://github.com/apache/cloudstack/blob/8f6721ed4c4e1b31081a951c62ffbe5331cf16d4/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java#L1202
> >
> even
> if you didn't enable the HA.
> If I may advise you to disable in the `agent.properties` file the property
> `reboot.host.and.alert.management.on.heartbeat.timeout=false`. CloudStack
> will still execute the heartbeat check but won't restart the agent host on
> failure.
>
> Best regards,
> Slavka
>
> On Tue, Feb 20, 2024 at 12:41 AM Swen  wrote:
>
> > Hi all,
> >
> > we encountered a strange issue today in our lab installation. We are
> > running CS 4.19.0 upgraded from CS 4.18.1 with linstor as primary
> > storage. We are using a linstor jar file provided by Linbit which is
> > not the default one part of default 4.19.0!
> >
> > This updated plugin already includes a new feature to use linstor
> > storage for host ha. I provide this only for information reasons.
> >
> > The issue we encountered was that even we do not have HA enabled on
> > cluster and host level, cloudstack agent on our KVM hosts triggered HA
> > actions and rebooted our hosts. We found this on our agent.log:
> >
> > Feb 19 11:53:05 pc-kvm-2 java[6617]: WARN  [kvm.resource.KVMHAMonitor]
> > (Thread-1:) (logid:) Write heartbeat for pool
> > [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 2 of 5.
> >
> > Feb 19 11:58:58 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> > (Thread-1:) (logid:) Write heartbeat for pool
> > [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 3 of 5.
> >
> > Feb 19 12:00:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> > (Thread-1:) (logid:) Write heartbeat for pool
> > [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 4 of 5.
> >
> > Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> > (Thread-1:) (logid:) Write heartbeat for pool
> > [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 5 of 5.
> >
> > Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> > (Thread-1:) (logid:) Write heartbeat for pool
> > [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; stopping
> > cloudstack-agent.
> >
> > Feb 19 12:02:08 pc-kvm-2 heartbeat: kvmspheartbeat.sh will reboot
> > system because it was unable to write the heartbeat to the storage.
> >
> > We and Linbit did some debugging. We tried to understand why the
> > cloudstack agent is running those checks in the first place. We were
> > unable to find any code which checks if host HA is enabled or not and
> > will not perform HA tasks if HA is disabled. Can somebody please
> > double-check this?
> >
> > Thank you very much!
> >
> > Regards,
> > Swen
> >
> >
> >
>
>
>

Re: ha checks on kvm hosts running even with ha disabled

[Slavka Peleva]

Hi Swen,

The KVMHAMonitor is initialised here

even
if you didn't enable the HA.
If I may advise you to disable in the `agent.properties` file the property
`reboot.host.and.alert.management.on.heartbeat.timeout=false`. CloudStack
will still execute the heartbeat check but won't restart the agent host on
failure.

Best regards,
Slavka

On Tue, Feb 20, 2024 at 12:41 AM Swen  wrote:

> Hi all,
>
> we encountered a strange issue today in our lab installation. We are
> running
> CS 4.19.0 upgraded from CS 4.18.1 with linstor as primary storage. We are
> using a linstor jar file provided by Linbit which is not the default one
> part of default
> 4.19.0!
>
> This updated plugin already includes a new feature to use linstor storage
> for host
> ha. I provide this only for information reasons.
>
> The issue we encountered was that even we do not have HA enabled on
> cluster and host level, cloudstack agent on our KVM hosts triggered HA
> actions and rebooted our hosts. We found this on our agent.log:
>
> Feb 19 11:53:05 pc-kvm-2 java[6617]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 2 of 5.
>
> Feb 19 11:58:58 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 3 of 5.
>
> Feb 19 12:00:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 4 of 5.
>
> Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 5 of 5.
>
> Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; stopping
> cloudstack-agent.
>
> Feb 19 12:02:08 pc-kvm-2 heartbeat: kvmspheartbeat.sh will reboot system
> because it was unable to write the heartbeat to the storage.
>
> We and Linbit did some debugging. We tried to understand why the
> cloudstack agent is running those checks in the first place. We were unable
> to find any code which
> checks if host HA is enabled or not and will not perform HA tasks if HA is
> disabled. Can somebody please double-check this?
>
> Thank you very much!
>
> Regards,
> Swen
>
>
>

Re: new PMC member Harikrishna Patnala

[Slavka Peleva]

Congratulations Harikrishna!



On Tue, Jan 16, 2024 at 8:22 AM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:

> Congratulations Harikrishna!
>
> Regards,
> Suresh
>
> From: Daan Hoogland 
> Date: Monday, 15 January 2024 at 2:55 PM
> To: dev , users 
> Subject: new PMC member Harikrishna Patnala
> users and dev,
>
> The PMC have invited Harikrishna to join their ranks and he has
> gracefully accepted. Please join me in congratulating Hari.
>
> --
> Daan
>
>
>
>

Re: New committer: Alexandre Mattioli

[Slavka Peleva]

Congrats Alex!

On Thu, Jan 11, 2024 at 8:51 AM Abhishek Kumar  wrote:

> Congrats Alex!
>
> On Thu, 11 Jan 2024 at 03:58, Nux  wrote:
>
> > All,
> >
> > The Project Management Committee (PMC) for Apache CloudStack
> > has invited Alexandre Mattioli to become a committer and we are pleased
> > to announce that they have accepted.
> >
> > Alex has been instrumental in many features present today in Cloudstack,
> > with a focus on networking and VMWare:
> > - IPv6 static routing
> > - Edge Zones
> > - Autoscaling with VR
> > - VNF appliances
> > - VMWare NSX support
> > - Tungsten Fabric / OpenSDN
> > - Backup & recovery framework
> > - VLAN trunking and security policies in ESX
> > and so on.
> >
> >
> > Please join me in congratulating Alex!
> >
> >
>
> --
>
> Abhishek Kumar
>

Re: new committer: João Jandre Paraquetti

[Slavka Peleva]

Congratulations João!



On Tue, Dec 19, 2023 at 9:13 AM Vishesh Jindal 
wrote:

> Congratulations João!
> 
> From: Harikrishna Patnala 
> Sent: Tuesday, December 19, 2023 11:24 AM
> To: users@cloudstack.apache.org ; dev <
> d...@cloudstack.apache.org>
> Subject: Re: new committer: João Jandre Paraquetti
>
> Congratulations João
>
> Regards,
> Harikrishna
>
> From: Daan Hoogland 
> Date: Monday, 18 December 2023 at 6:17 PM
> To: dev , users 
> Subject: new committer: João Jandre Paraquetti
> community,
> The PMC have invited João Jandre Paraquetti to join the project as a
> committer and the invitation was gratefully accepted.
> Please join me in welcoming João.
> Congratulations João,
>
> --
> Daan
>
>
>
>
>
>
>

Re: new committer Vladimir Petrov

[Slavka Peleva]

Congrats Vladi! :)


On Wed, Dec 13, 2023 at 7:38 AM Jithin Raju 
wrote:

> Congratulations Vladi !
>
> -Jithin
>
> From: Daman Arora 
> Date: Wednesday, 13 December 2023 at 11:06 AM
> To: d...@cloudstack.apache.org 
> Cc: users 
> Subject: Re: new committer Vladimir Petrov
> Congrats Vladimir!
>
> On Wed, Dec 13, 2023, 11:05 a.m. Harikrishna Patnala <
> harikrishna.patn...@shapeblue.com> wrote:
>
> > Congratulations Vladi !
> >
> > Regards,
> > Harikrishna
> >
> > From: Daan Hoogland 
> > Date: Tuesday, 12 December 2023 at 3:22 PM
> > To: dev , users 
> > Subject: new committer Vladimir Petrov
> > community,
> >
> > The PMC has decided Vladi to become a committer and he has gracefully
> > accepted. Please join me in welcoming Vladi to the project as
> > committer.
> > Congratulations Vladi
> >
> > --
> > Daan
> >
> >
> >
> >
>
>
>
>

Re: new committer Bryan Lima

[Slavka Peleva]

Congratulations Bryan!

Best regards,
Slavka

On Fri, Dec 1, 2023 at 6:58 AM Suresh Kumar Anaparti <
sureshkumar.anapa...@gmail.com> wrote:

> Congratulations Bryan!
>
> Regards,
> Suresh
>
> On Thu, Nov 30, 2023 at 2:37 PM Daan Hoogland 
> wrote:
> >
> > All,
> >
> > The Project Management Committee (PMC) for Apache CloudStack
> > has invited Bryan Lima to become a PMC member and we are pleased
> > to announce that they have accepted.
> >
> > Bryan has contributed himself and assisted in reviewing and testing
> > the work of others. He has shown to be responsive, constructive and
> > pleasant to work with.
> >
> > please join me in congratulating Bryan
> >
> > --
> > Daan
>

Re: new PMC member: Abhishek Kumar

[Slavka Peleva]

Congratulations Abhishek!

Best regards,
Slavka

On Thu, Nov 23, 2023 at 11:12 AM Pearl d'Silva 
wrote:

> Congratulations Abhishek!!!
> Well deserved!
>
> Regards,
> Pearl
>
> 
> From: Harikrishna Patnala 
> Sent: November 23, 2023 4:01 AM
> To: users@cloudstack.apache.org ; dev <
> d...@cloudstack.apache.org>
> Subject: Re: new PMC member: Abhishek Kumar
>
> Congratulations Abhishek, well deserved.
>
> Regards,
> Harikrishna
>
>
> 
> From: Daan Hoogland 
> Sent: Thursday, November 23, 2023 9:41:52 AM
> To: users ; dev 
> Subject: new PMC member: Abhishek Kumar
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Abhishek Kumar to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Abhishek has contributed in the past and has shown effort to make the
> project run smoothly. He is also the Release Manager for the upcoming
> 4.19 release.
>
> please join me in congratulating Abhishek
>
> --
> Daan
>
>
>
>
>
>
>
>

Re: AW: Cloudstack Linstor cant do live vm snapshots?

[Slavka Peleva]

Hi Bryan,

Sorry, I haven't done any research about how to take the memory.
Unfortunately, with the current implementation, I don't think there is any
workaround.

Best regards,
Slavka

On Thu, Nov 16, 2023 at 9:51 AM Bryan Tiang 
wrote:

> Hi Slavka,
>
> Thanks! Another question, I understand that  Storage-based Instance
> Snapshots on KVM does not support memory snapshot.
>
> Are there any workaround to allow memory snapshot?
>
> Still using KVM and Linstor
>
> Regards,
> Bryan
> On 16 Nov 2023 at 3:21 PM +0800, Slavka Peleva
> , wrote:
> > Hi Bryan,
> >
> > Yes, you need qemu-guest-agent to be installed. This operation creates a
> > volume snapshot for each volume that is attached to the VM while the
> > virtual machine is frozen.
> > Storage-based Instance Snapshots on KVM
> > <
> https://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#storage-based-instance-snapshots-on-kvm
> >
> >
> > Best regards,
> > Slavka
> >
> > On Thu, Nov 16, 2023 at 7:47 AM Bryan Tiang 
> > wrote:
> >
> > > Hey Swen,
> > >
> > > Thanks for this. But for this to work, we need to make sure each VM
> > > spinner up has the QEMU agent installed, right?
> > >
> > > Regards,
> > > Bryan
> > > On 10 Nov 2023 at 9:54 PM +0800, m...@swen.io, wrote:
> > > > Hi Bryan,
> > > >
> > > > you can use KVM with linstor to do VM snapshots. You just need to
> enable
> > > kvm.snapshot.enabled and kvm.vmstoragesnapshot.enabled in global
> settings.
> > > No NFS storage needed at all.
> > > >
> > > > Regards,
> > > > Swen
> > > >
> > > > -Ursprüngliche Nachricht-
> > > > Von: Bryan Tiang 
> > > > Gesendet: Freitag, 10. November 2023 14:12
> > > > An: Vivek Kumar via users 
> > > > Betreff: Cloudstack Linstor cant do live vm snapshots?
> > > >
> > > > Hi Community,
> > > >
> > > > We are using Cloudstack with Linstor. We want to achieve live
> snapshots
> > > as this is an important feature for us (can’t live without it).
> > > >
> > > > But based on the Cloudstack documentation, KVM Supports VM Snapshots
> > > only when using NFS Shared Storage.
> > > >
> > > > Linstor does support NFS, but there are some limitations to it such
> as
> > > not being able to resize the NFS share file (need to create a new NFS
> and
> > > do manual migration).
> > > >
> > > > How are other users overcoming this issue with Cloudstack + Linstor?
> Our
> > > setup details below:
> > > >
> > > > Compute Hypervisor: Ubuntu 20/22 LTS KVM Primary Storage: Linstor Raw
> > > Block Storage
> > > >
> > > > Regards,
> > > > Bryan
> > > >
> > > >
> > >
>

Re: AW: Cloudstack Linstor cant do live vm snapshots?

[Slavka Peleva]

Hi Bryan,

Yes, you need qemu-guest-agent to be installed. This operation creates a
volume snapshot for each volume that is attached to the VM while the
virtual machine is frozen.
Storage-based Instance Snapshots on KVM


Best regards,
Slavka

On Thu, Nov 16, 2023 at 7:47 AM Bryan Tiang 
wrote:

> Hey Swen,
>
> Thanks for this. But for this to work, we need to make sure each VM
> spinner up has the QEMU agent installed, right?
>
> Regards,
> Bryan
> On 10 Nov 2023 at 9:54 PM +0800, m...@swen.io, wrote:
> > Hi Bryan,
> >
> > you can use KVM with linstor to do VM snapshots. You just need to enable
> kvm.snapshot.enabled and kvm.vmstoragesnapshot.enabled in global settings.
> No NFS storage needed at all.
> >
> > Regards,
> > Swen
> >
> > -Ursprüngliche Nachricht-
> > Von: Bryan Tiang 
> > Gesendet: Freitag, 10. November 2023 14:12
> > An: Vivek Kumar via users 
> > Betreff: Cloudstack Linstor cant do live vm snapshots?
> >
> > Hi Community,
> >
> > We are using Cloudstack with Linstor. We want to achieve live snapshots
> as this is an important feature for us (can’t live without it).
> >
> > But based on the Cloudstack documentation, KVM Supports VM Snapshots
> only when using NFS Shared Storage.
> >
> > Linstor does support NFS, but there are some limitations to it such as
> not being able to resize the NFS share file (need to create a new NFS and
> do manual migration).
> >
> > How are other users overcoming this issue with Cloudstack + Linstor? Our
> setup details below:
> >
> > Compute Hypervisor: Ubuntu 20/22 LTS KVM Primary Storage: Linstor Raw
> Block Storage
> >
> > Regards,
> > Bryan
> >
> >
>

Re: [DISCUSS] New Design for the Apache CloudStack Website

[Slavka Peleva]

Thanks, Ivet!

I like the design proposal. I am sure it will help the project a lot.

Best regards,
Slavka

On Thu, Aug 31, 2023 at 12:43 PM Rohit Yadav 
wrote:

> Thanks Ivet, the new iterated design looks impressive especially some of
> the new graphical elements.
>
> +1 to moving forward with the proposed design. Let's collect any further
> feedback and ideas from the community and if there are no objections go
> ahead with updating the preview/staging site (
> https://cloudstack.staged.apache.org/) and eventually publishing the
> website.
>
> Just to be clear on the CMS integration - the ASF infra has declined
> supporting a 3rd party git-based CMS that can be used with the project
> website. This is such a shame as I had created PoCs with some rather
> okay-ist git-based CMS such as Netlify-CMS, TinaCMS and SpinalCMS which
> would give similar UI-based workflow like the old Roller-based blog did.
>
> Nevertheless, for the purposes of publishing blogs the new Github-based
> document/markdown editor/CMS is fair enough and now allows uploading of
> assets (images, files etc.) and blog that can be edited directly for any
> committer incl. PMC members logged into Github and upon saving such changes
> the website is published by an automatic Github action that builds and
> published the websites. Unfortunately, any non-committer would need to
> follow the PR workflow. I had this documented at
> https://cloudstack.staged.apache.org/website-guide/ that I can help
> further update in this regard.
>
>
> Regards.
>
> 
> From: Ivet Petrova 
> Sent: Wednesday, August 30, 2023 19:04
> To: Giles Sirett 
> Cc: d...@cloudstack.apache.org ;
> users@cloudstack.apache.org ; Marketing <
> market...@shapeblue.com>
> Subject: Re: [DISCUSS] New Design for the Apache CloudStack Website
>
> Hi All,
>
> I uploaded the design here:
> https://drive.google.com/file/d/1pef7xWWMPYAA5UkbS_XMUxrz53KB7J5t/view?usp=sharing
>
>
> Kind regards,
>
>
>
>
>
>
>
> On 30 Aug 2023, at 16:31, Giles Sirett  giles.sir...@shapeblue.com>> wrote:
>
> Hi Ivet – thanks for pushing forward with this – excited to review a new
> design.
>
> On that note, I cant see a link in your mail ☹
>
> Kind Regards
> Giles
>
>
> Giles Sirett
> CEO
> giles.sir...@shapeblue.com
> www.shapeblue.com
>
>
>
>
> From: Ivet Petrova  ivet.petr...@shapeblue.com>>
> Sent: Wednesday, August 30, 2023 10:14 AM
> To: users@cloudstack.apache.org;
> Marketing mailto:market...@shapeblue.com>>
> Cc: dev mailto:d...@cloudstack.apache.org>>
> Subject: [DISCUSS] New Design for the Apache CloudStack Website
>
> Hello,
>
> I would like to start a discussion on the design of the Apache CloudStack
> Website and to propose a new design for it.
>
> As we all know, the website has not been changed for years in terms of
> design and information. The biggest issue we know we have is that the
> website is not showing the full potential of CloudStack. In addition to it
> during discussions with many community members, I have noted the following
> issues:
> - the existing website design is old-school
> - the current homepage does not collect enough information to show
> CloudStack's strengths
> - current website design is missing images from the ACS UI and cannot
> create a feel for the product in the users
> - the website has issues on a mobile device
> - we lack any graphic and diagrams
> - some important information like how to download is not very visible
>
> I collected a lot of feedback during last months and want to propose a new
> up to date design for the website, which is attached below. The new design
> will bring:
> - improved UX
> - look and feel corresponding to the CloudStack's capabilities and
> strengths
> - more graphical elements, diagrams
> - better branding
> - more important information, easily accessible for the potential users
>
> I hope you will like the new design – all feedback welcome. Once we have
> the design finalised, we will use Rohit’s proposal previously of a CMS,
> which is easy to edit.
>
> [cid:B5517475-02DA-472A-BD1D-F3B600AD28ED]
>
> Kind regards,
>
>

Re: Write Speeds

[Slavka Peleva]

Can you share the full agent.log with the VM deployment? Also, can you
search the agent.log for "IO uring driver for Qemu:  " and share the
whole log message?

Best regards,
Slavka

On Tue, Jul 11, 2023 at 1:55 PM Granwille Strauss 
wrote:

> Hi
>
> Thank you for the feedback, that's exactly what I did earlier, didn't do
> anything. I also set it in global config and you can also set it for the
> local primary storage. Nothing happened in the XML dumps.
> On 7/11/23 12:50, Slavka Peleva wrote:
>
> Can you set it from the VM's settings? The VM has to be stopped. I will
> check the global config later.
>
> [image: image.png]
>
>
>
> On Tue, Jul 11, 2023 at 1:38 PM Granwille Strauss 
> wrote:
>
>> Hi
>>
>> I am using the latest CS 4.18.0.0
>> On 7/11/23 12:28, Slavka Peleva wrote:
>>
>> Can you share the CS version that you're using? There are some differences
>> in enabling the IO policy depending on the version.
>>
>> Best regards,
>> Slavka
>>
>> On Tue, Jul 11, 2023 at 1:05 PM Granwille Strauss  
>> 
>> wrote:
>>
>>
>> Nope, didn't work. I added enable.io.uring=true to
>> /etc/cloudstack/agent/agent.properties, restarted cloudstack-agent.
>> Shutdown one VM machine. Set io.policy=io.uring for this VM then start up
>> VM again and XML dump remains the same:
>>
>> virsh dumpxml i-2-182-VM | grep drive
>>   
>>   
>>   
>>
>>
>> On 7/11/23 11:53, Slavka Peleva wrote:
>>
>> Hi,
>>
>> Can you check if the `enable.io.uring=true` property in the
>> agent.properties file is set? You have to restart the cloudstack-agent
>> service if you make any changes.
>>
>> Best regards,
>> Slavka
>>
>>
>> --
>> Regards / Groete
>> <https://www.namhost.com> <https://www.namhost.com> Granwille Strauss  //  
>> Senior Systems Admin
>>
>> *e:* granwi...@namhost.com
>> *m:* +264 81 323 1260 <+264813231260>
>> *w:* www.namhost.com
>> <https://www.facebook.com/namhost> <https://www.facebook.com/namhost> 
>> <https://twitter.com/namhost> 
>> <https://twitter.com/namhost><https://www.instagram.com/namhostinternetservices/>
>>  
>> <https://www.instagram.com/namhostinternetservices/><https://www.linkedin.com/company/namhos>
>>  
>> <https://www.linkedin.com/company/namhos><https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>>  <https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>>
>> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>>  
>> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>>
>> Namhost Internet Services (Pty) Ltd,
>>
>> 24 Black Eagle Rd, Hermanus, 7210, RSA
>>
>>
>>
>> The content of this message is confidential. If you have received it by
>> mistake, please inform us by email reply and then delete the message. It is
>> forbidden to copy, forward, or in any way reveal the contents of this
>> message to anyone without our explicit consent. The integrity and security
>> of this email cannot be guaranteed over the Internet. Therefore, the sender
>> will not be held liable for any damage caused by the message. For our full
>> privacy policy and disclaimers, please go 
>> tohttps://www.namhost.com/privacy-policy
>>
>> [image: Powered by 
>> AdSigner]<https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>
>>  
>> <https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>
>>
>> --
>> Regards / Groete
>>
>> <https://www.namhost.com> Granwille Strauss  //  Senior Systems Admin
>>
>> *e:* granwi...@namhost.com
>> *m:* +264 81 323 1260 <+264813231260>
>> *w:* www.namhost.com
>>
>> <https://www.facebook.com/namhost> <https://twitter.com/namhost>
>> <https://www.instagram.com/namhostinternetservices/>
>> <https://www.linkedin.com/company/namhos>
>> <https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>>
>>
>> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>>
>> Namhost Internet Services (Pty) Ltd,
>>
>> 24 Black Eagle Rd, Hermanus, 7210, RSA
>>
>>
>>
>> The content of this message is confidential. If you have received it by
>> mistake, please inform us by email reply and

Re: Write Speeds

[Slavka Peleva]

Can you set it from the VM's settings? The VM has to be stopped. I will
check the global config later.

[image: image.png]



On Tue, Jul 11, 2023 at 1:38 PM Granwille Strauss 
wrote:

> Hi
>
> I am using the latest CS 4.18.0.0
> On 7/11/23 12:28, Slavka Peleva wrote:
>
> Can you share the CS version that you're using? There are some differences
> in enabling the IO policy depending on the version.
>
> Best regards,
> Slavka
>
> On Tue, Jul 11, 2023 at 1:05 PM Granwille Strauss  
> 
> wrote:
>
>
> Nope, didn't work. I added enable.io.uring=true to
> /etc/cloudstack/agent/agent.properties, restarted cloudstack-agent.
> Shutdown one VM machine. Set io.policy=io.uring for this VM then start up
> VM again and XML dump remains the same:
>
> virsh dumpxml i-2-182-VM | grep drive
>   
>   
>   
>
>
> On 7/11/23 11:53, Slavka Peleva wrote:
>
> Hi,
>
> Can you check if the `enable.io.uring=true` property in the
> agent.properties file is set? You have to restart the cloudstack-agent
> service if you make any changes.
>
> Best regards,
> Slavka
>
>
> --
> Regards / Groete
> <https://www.namhost.com> <https://www.namhost.com> Granwille Strauss  //  
> Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
> <https://www.facebook.com/namhost> <https://www.facebook.com/namhost> 
> <https://twitter.com/namhost> 
> <https://twitter.com/namhost><https://www.instagram.com/namhostinternetservices/>
>  
> <https://www.instagram.com/namhostinternetservices/><https://www.linkedin.com/company/namhos>
>  
> <https://www.linkedin.com/company/namhos><https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>  <https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>
> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>  
> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go 
> tohttps://www.namhost.com/privacy-policy
>
> [image: Powered by 
> AdSigner]<https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>
>  
> <https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>
>
> --
> Regards / Groete
>
> <https://www.namhost.com> Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
> <https://www.facebook.com/namhost> <https://twitter.com/namhost>
> <https://www.instagram.com/namhostinternetservices/>
> <https://www.linkedin.com/company/namhos>
> <https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>
>
> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> <https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>
>

Re: Write Speeds

[Slavka Peleva]

Can you share the CS version that you're using? There are some differences
in enabling the IO policy depending on the version.

Best regards,
Slavka

On Tue, Jul 11, 2023 at 1:05 PM Granwille Strauss 
wrote:

> Nope, didn't work. I added enable.io.uring=true to
> /etc/cloudstack/agent/agent.properties, restarted cloudstack-agent.
> Shutdown one VM machine. Set io.policy=io.uring for this VM then start up
> VM again and XML dump remains the same:
>
> virsh dumpxml i-2-182-VM | grep drive
>   
>   
>   
>
>
> On 7/11/23 11:53, Slavka Peleva wrote:
>
> Hi,
>
> Can you check if the `enable.io.uring=true` property in the
> agent.properties file is set? You have to restart the cloudstack-agent
> service if you make any changes.
>
> Best regards,
> Slavka
>
>
> --
> Regards / Groete
>
> <https://www.namhost.com> Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
> <https://www.facebook.com/namhost> <https://twitter.com/namhost>
> <https://www.instagram.com/namhostinternetservices/>
> <https://www.linkedin.com/company/namhos>
> <https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>
>
>
> <https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> <https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>
>

Re: Write Speeds

[Slavka Peleva]

Hi,

Can you check if the `enable.io.uring=true` property in the
agent.properties file is set? You have to restart the cloudstack-agent
service if you make any changes.

Best regards,
Slavka

Re: [ANNOUNCE] New VP of Apache CloudStack - Rohit Yadav

[Slavka Peleva]

Congratulations, Rohit, I wish you all the best!
Thank you, Simon, for your work as a VP!

Best regards,
Slavka

On Thu, Mar 30, 2023 at 11:23 AM Boris Stoyanov <
boris.stoya...@shapeblue.com> wrote:

> Congrats Rohit!
>
> From: Simon Weller 
> Date: Thursday, 30 March 2023, 6:36
> To: d...@cloudstack.apache.org ,
> users@cloudstack.apache.org 
> Cc: priv...@cloudstack.apache.org 
> Subject: [ANNOUNCE] New VP of Apache CloudStack - Rohit Yadav
> All,
>
> I'm very pleased to announce that the ASF board has accepted the nomination
> of Rohit Yadav to be the new VP of the Apache CloudStack project.
>
> It has been my pleasure to serve as the VP over the past year, and I'd like
> to thank the community for all of the support.
>
> Rohit, congratulations and I wish you the best as you take on this new
> role.
>
> -Simon
>
>
>
>

Re: Daan Hoogland - New ASF Member

[Slavka Peleva]

Congratulations Daan!

Best regards,
Slavka

On Fri, Mar 24, 2023 at 12:01 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> Congratulations Daan!
>
> Regards,
> Nicolas Vaquez
> 
> From: Paul Angus 
> Sent: Friday, March 24, 2023 6:28:54 AM
> To: users@cloudstack.apache.org ;
> d...@cloudstack.apache.org 
> Subject: Daan Hoogland - New ASF Member
>
>
>
> It is my pleasure to announce that Daan Hoogland as been elected to become
> a
> member of the ASF.
>
> The ASF would like to recognize both his practical involvement and the way
> in which he has interacted with others in and around the ASF.
>
>
>
> Congratulations  Daan.
>
>
>
>
>
>
>
>
>
> Kind regards
>
>
>
> Paul Angus
>
>
>
>
>
>
>

Re: [ANNOUNCE] Ivet Petrova has joined the PMC

[Slavka Peleva]

Congrats Ivet!

On Wed, Feb 15, 2023 at 8:25 AM Kiran Chavala 
wrote:

> Congratulations Ivet!
> 
> From: David Jumani 
> Sent: 15 February 2023 11:36
> To: users@cloudstack.apache.org ;
> d...@cloudstack.apache.org 
> Cc: priv...@cloudstack.apache.org 
> Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC
>
> Congratulations Ivet!
>
> 
> From: Vishesh Jindal 
> Sent: Wednesday, February 15, 2023 10:24 AM
> To: users@cloudstack.apache.org 
> Cc: d...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC
>
> Congratulations Ivet!
> 
> From: Rohit Yadav 
> Sent: Wednesday, February 15, 2023 7:14 AM
> To: users@cloudstack.apache.org 
> Cc: d...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC
>
> Congratulations Ivet, well deserved!
>
> Regards.
> 
> From: Martijn Struijk 
> Sent: Wednesday, February 15, 2023 3:06:18 AM
> To: users@cloudstack.apache.org 
> Cc: d...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC
>
> Congratulations Ivet!
>
> On Tue, Feb 14, 2023 at 7:24 PM Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > Congratulations Ivet!
> >
> > Regards,
> > Nicolas Vazquez
> > 
> > From: Simon Weller 
> > Sent: Tuesday, February 14, 2023 1:01 PM
> > To: priv...@cloudstack.apache.org ;
> > d...@cloudstack.apache.org ;
> > users@cloudstack.apache.org 
> > Subject: [ANNOUNCE] Ivet Petrova has joined the PMC
> >
> > Hi everyone,
> >
> > It gives me great pleasure to announce that Ivet has been invited to join
> > the
> > CloudStack PMC and she has accepted.
> >
> > Please join me in congratulating Ivet!
> >
> > -Simon (on behalf of the CloudStack PMC)
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>
>
>
>
>

Re: Changing VM Name & Display Name Not Possible on 4.17.1.0

[Slavka Peleva]

Hi,

I've tested the update of the display name and the name of the VM on my lab
4.17.1.0 and it works fine (works on stopped VM). Can you share some logs,
also from the browser console?
To update the name/display name from the DB the correct tables are:
To update the name - the table is  `vm_instance`;
To update the display name - the DB table is `user_vm`;

Best regards,
Slavka

On Thu, Dec 8, 2022 at 4:52 PM Granwille Strauss
 wrote:

> Hi
>
> I am trying to change a VM name and its display name via CM, however, I
> cannot and get error 530, see attached screenshot. I have stopped the VM
> and tried changing it, same results and also rebooted the VM multiple times
> no luck.
>
> I tried changing it in the cloudstack DB under table user_vm_view but it
> gives me and error that reads "The target table user_vm_view of the UPDATE
> is not updatable." Any ideas how I can fix this? The name was accidentality
> set to "TestVM" but it was an actual clients VM machine and we're afraid at
> some point in future it will be deleted as it is seen as a "Test VM".
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>

Re: VM Volume Limit 1024 GB

[Slavka Peleva]

Hi Rafael,

you can increase the value of the
global setting `custom.diskoffering.size.max`

Best regards,
Slavka

On Tue, Dec 6, 2022 at 12:18 PM Nux  wrote:

> Check the user or domain limits.
>
> ---
> Nux
> www.nux.ro
>
> On 2022-12-06 10:15, Rafael del Valle wrote:
> > Hi!
> >
> > I ​cannot create an instance with 2000 GB data volume despite
> > available resources in ACS 4.16.1.
> >
> > I get a message:
> >
> > VM Creation failed. Volume size: 2000GB is out of allowed range. Max:
> > 1024 Min:1
> >
> > The configuration parameter storage.max.volume.size is 2000
> >
> >
> >
> > I cannot see any related account limit either.
> >
> > The volume type is Local Storage.
> >
> >
> > Where is the limit coming from?
> >
> >
> > R.
>

Re: VMs HA not working with Ceph

[Slavka Peleva]

Hello Pradeep, Ranjit,

As far as I know, you need to have an NFS primary storage and OOBM
configured. There is a PR that provides a solution to have HA for RBD, but
it's not merged yet - https://github.com/apache/cloudstack/pull/5862.

I hope the links below will help you
https://docs.cloudstack.apache.org/en/latest/adminguide/reliability.html#ha-enabled-hosts
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack
https://www.shapeblue.com/host-ha-for-kvm-hosts-in-cloudstack/#Host-HA_on_KVM_host

Best regards,
Slavka

On Fri, Dec 2, 2022 at 9:02 AM Ranjit Jadhav 
wrote:

> Hello Guys,
>
> We are also struggling with this HA thing any guidance will be highly
> appreciated.
>
> Regards,
> Ranjit
>
> On Thu, 1 Dec 2022 at 20:50, pspa...@hotmail.com 
> wrote:
>
> > Hi,
> > I have build new infra with Ceph storage everything working well.
> > But VMs HA not working. Can anyone guide me.
> >
> > Regards Pradeep Kumar
>

Re: Recover virtual router

[Slavka Peleva]

Hi Sam,

You can also try deploying a new guest VM, or if you have stopped VMs, you
can start one. This will create a new VR.

Best regards,
Slavka

On Tue, Nov 29, 2022 at 2:09 PM Ruben Bosch  wrote:

> Hi Sam,
>
> If you click the "Restart Network" button in the network overview the
> virtual router will be recreated.
>
> Met vriendelijke groet / Kind regards,
>
> Ruben Bosch
> CLDIN
>
> > On 29 Nov 2022, at 13:06, Samuel Ngoda  wrote:
> >
> > Hello all,
> >
> > I have just upgraded to cloudstack 4.17.
> >
> > I made a mistake and deleted the only virtual router without having a
> backup.
> >
> > Is there a way of recreating or recovering it?
> >
> > Currently I am unable to restart the network to recreate the router
> > because it requires running router to be available.
> >
> > Regards,
> >
> > Sam
> > Hello all,
> >
> >
> > I made a mistake and deleted the only virtual router without having a
> backup.
> >
> > Is there a way of recreating or recovering it?
> >
> > Regards,
> >
> > Sam
> >
> >
> >
> >
> >
> >
> > On Sun, Nov 27, 2022 at 12:41 PM Martha  wrote:
> >>
> >>
> >>
> >> Hello all,
> >>
> >>
> >>
> >> I made a mistake and deleted the only virtual router without having a
> backup.
> >>
> >> Is there a way of recreating or recovering it?
> >>
> >> Regards,
> >>
> >> Sam
> >>
> >>
> >>
> >> Sent from Mail for Windows
> >>
> >>
>
>

Re: Drivers

[Slavka Peleva]

Hi,

`*kvm.vmstoragesnapshot.enabled` *requires only qemu-guest-agent. It is
used to freeze/thaw the virtual machine during snapshotting - VM snapshots
without memory


Best regards,
Slavka

On Wed, Oct 12, 2022 at 7:42 PM Granwille Strauss
 wrote:

> Hi Nux
>
> That sounds great. For what  it's worth, I did find the following setting
> in global config:
>
> *kvm.vmstoragesnapshot.enabled*: For live snapshot of virtual machine
> instance on KVM hypervisor without memory. Requieres qemu version 1.6+ (on
> NFS or Local file system) and qemu-guest-agent installed on guest VM
>
> So it seems it does use qemu-ga to some sort.
> On 10/12/22 18:09, Nux wrote:
>
> Hello,
>
> AFAIK Cloudstack does not leverage the qemu-ga functionality for anything
> - yet. It doesn't hurt to have it though, it may be useful for your own
> operations as it can do various things - such as connect to the socket from
> the hypervisor side then check IP addesses, freeze filesystems etc. I would
> bake qemu-ga in my templates tbh.
>
> Also, you never know, in the future Cloudstack might also leverage it for
> various features.
> ---
> Nux
> www.nux.ro
>
>
> On 2022-10-12 17:04, Granwille Strauss wrote:
>
> Hi Nux
>
> Thank you. Is it worth installing qemu-guest-agent on our guest Linux VMs?
> Would this provide any significant change?
> On 10/12/22 17:44, Nux wrote:
>
> Hi,
>
> Make sure you have the virtio drivers installed.
>
> Linux has them by default, but Windows opted not to have support for it,
> so you will have to do it for them.
>
> If you do not use virtio devices (ie paravirt) your IO will suffer.
> ---
> Nux
> www.nux.ro
>
>
> On 2022-10-12 15:13, Granwille Strauss wrote:
>
> Hi Guys
>
> I run KVM node via Cloudstack, and want to confirm if there are any
> additional guest agents & drivers that I need to install to my guest VM?
> For both Linux and Windows guests?
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 

Re: Cannot find storage pool

[Slavka Peleva]

Hi Groete,

Can you share the end of this message?

> internal error: Child process (/usr/bin/mount -o nodev,nosuid,noexec
> 156.38.173.122:/mnt/primary /mnt/81ffca3a-9775-375d-a1c0-9504c0ec3d89)
> unexpected exit st>
>
> Best regards,
Slavka

On Thu, Sep 29, 2022 at 1:17 PM Granwille Strauss
 wrote:

> Hi Guys
>
> I tried making volume snapshots and the first 4 VMs were succesfull. When
> I tried the 5th VM volume snapshot, the process just "hung" and managed to
> get stuck in "snapshotting" and in "Creating" states.
>
> I rebooted both my KVM server and CM server and now the host cannot
> connect to CM. I am getting this error:
>
> 2022-09-29 12:11:37,104 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (agentRequest-Handler-2:null) (logid:c2cf2636) Didn't find an existing
> storage pool 81ffca3a-9775-375d-a1c0-9504c0ec3d89 by UUID, checking for
> pools with duplicate paths
>
> I updated the snapshots and volumes table in database and set status and
> state to "Ready" and "BackedUp" restarted CM and agent with no luck. I
> rebooted libvrtd too but its looking for the storage pool and I have no
> idea where or what happened with it:
>
> internal error: Child process (/usr/bin/mount -o nodev,nosuid,noexec
> 156.38.173.122:/mnt/primary /mnt/81ffca3a-9775-375d-a1c0-9504c0ec3d89)
> unexpected exit st>
>
> My primary storage is on CM server at /mnt/primary but I also have local
> storage enabled at /var/lib/libvirt/images
>
> Any help please? My host is not connecting any more and all production VMs
> are down.
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>

Re: Error migrate System VMs after upgrageing to 4.17

[Slavka Peleva]

Hi Chris,

The deployment fails because CS cannot find a free IP address to allocate
for the system VM. Can you check if you explicitly added a range for the
system VMs, or you can check with this `select * from user_ip_address where
forsystemvms = 1;` If you don't have any ranges, you can get free IPs
with `SELECT
* FROM cloud.user_ip_address where allocated IS NULL  AND removed IS NULL;`
. To get the exact query executed by CS, you need to increase the log level
to TRACE.

Best regards,
Slavka

On Mon, Aug 29, 2022 at 8:03 PM vas...@gmx.de  wrote:

> Hi Slavka,
>
> no, i am not using any kind of custome offerings.
>
> I try to provide a more detailled log this time.
> Situation:
> v-83-VM was the "broken" consoleproxy. So the following log starts with
> it's expunging.
> Afterwards the new consoleproxy shall be deployed - v-85-VM.
>
> This first deployment (logid:dcfe0999) fails due to Insufficent address
> capacity - which i can't really understand or see in the database, checking
> the availeable IPs for systemVMs (given that i might looking up the wrong
> tables).
> How ever CS is working as expected trying to deploy the console proxy
> (logid:440fd101) Sync job-4288).
> That job fails with "Unable to create deployment, no usable volumes found
> for the VM: 85".
> Afterwards i have another try to start the consoleproxy (job-4289) which
> fails for the same reason. And thats how things go on in the log file...
>
>
> 2022-08-29 17:01:16,224 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Cleaning up hypervisor data structures (ex. SRs in XenServer) for managed
> storage. Data from VM instance {id: "83", name: "v-83-VM", uuid:
> "b1d1f9c6-eafe-4527-9335-e649c646aab0", type="ConsoleProxy"}.
> 2022-08-29 17:01:16,225 DEBUG [o.a.c.e.o.VolumeOrchestrator]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Cleaning storage for vm: 83
> 2022-08-29 17:01:16,233 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Expunged VM instance {id: "83", name: "v-83-VM", uuid:
> "b1d1f9c6-eafe-4527-9335-e649c646aab0", type="ConsoleProxy"}
> 2022-08-29 17:01:16,255 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Complete async job-4286, jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.SystemVmResponse/systemvm/{"id":"b1d1f9c6-eafe-4527-9335-e649c646aab0","systemvmtype":"consoleproxy","zoneid":"48e2e928-3300-43b5-8e3a-d9b358022502","zonename":"xx","dns1":"10.129.0.4","dns2":"195.10.195.195","name":"v-83-VM","templateid":"c20799e4-a990-449a-aae6-4b67374c7aff","templatename":"systemvm-kvm-4.17.0","created":"2022-08-29T10:38:26+0200","state":"Stopped","isdynamicallyscalable":"false","hasannotations":"false"}
> 2022-08-29 17:01:16,256 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Publish async job-4286 complete on message bus
> 2022-08-29 17:01:16,256 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Wake up jobs related to job-4286
> 2022-08-29 17:01:16,256 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Update db status for job-4286
> 2022-08-29 17:01:16,256 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286 ctx-442b1cb2) (logid:5fe8559a)
> Wake up jobs joined with job-4286 and disjoin all subjobs created from job-
> 4286
> 2022-08-29 17:01:16,260 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-35:ctx-29e06f28 job-4286) (logid:5fe8559a) Done executing
> org.apache.cloudstack.api.command.admin.systemvm.DestroySystemVmCmd for
> job-4286
> 2022-08-29 17:01:16,260 INFO  [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-35:ctx-29e06f28 job-4286) (logid:5fe8559a) Remove
> job-4286 from job monitoring
> 2022-08-29 17:01:17,691 DEBUG [o.a.c.h.HAManagerImpl]
> (BackgroundTaskPollManager-6:ctx-6af18142) (logid:fe263a70) HA health check
> task is running...
>
> 2022-08-29 17:01:21,694 DEBUG [o.a.c.h.HAManagerImpl]
> (BackgroundTaskPollManager-6:ctx-89b1442f) (logid:0efc40b2) HA health check
> task is running...
> 2022-08-29 17:01:25,698 DEBUG [o.a.c.h.HAManagerImpl]
> (BackgroundTaskPollManager-5:ctx-62313d05) (logid:7073663f) HA health check
> task is running...
> 2022-08-29 17:01:25,767 DEBUG [c.c.s.StatsCollector]
> (secstorage-1:ctx-c80e5a6e) (logid:f8e3eb60) Verifying image storage [1].
> Capacity: total=[1 TB], used=[828 GB], threshold=[100.0%].
> 2022-08-29 17:01:25,773 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-c80e5a6e) (logid:f8e3eb60) Zone [1] is ready to launch
> secondary storage VM.
> 2022-08-29 17:01:26,031 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-2d236928) (

Re: Error migrate System VMs after upgrageing to 4.17

[Slavka Peleva]

Thanks, Chris, for the information!

Are you using custom offerings for the system VMs? Can you share more info
if yes?

About the log, it's not the complete log from where the deployment started.
The deployment begins a bit earlier than what you shared. Can you search
the management log for `Sync job-3539 execution on object VmWorkJobQueue`
to get the `logid` for the volume creation (coloured in blue)? And if
possible, share the logs with the found log ID

Here is an example from my logs:

2022-08-29 17:07:49,114 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(consoleproxy-1:ctx-a952a3dc) (logid:89157bb9) Sync job-60484 execution on
object VmWorkJobQueue.4904

2022-08-29 17:07:50,816 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-5:ctx-56172581 job-60479/job-60484 ctx-a900986d)
(logid:95d750ae) Execute VM work job:
com.cloud.vm.VmWorkStart{"dcId":0,"userId":1,"accountId":1,"vmId":4904,"handlerName":"VirtualMachineManagerImpl"}
2022-08-29 17:07:50,817 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-5:ctx-56172581 job-60479/job-60484 ctx-a900986d)
(logid:95d750ae) orchestrating VM start for 'v-4904-VM'
com.cloud.vm.VirtualMachineProfile$Param@b66cdd7d set to null


On Mon, Aug 29, 2022 at 2:29 PM vas...@gmx.de  wrote:

> Hi Slavka,
>
> thats what i did after your suggestion / informatin and where the error
> occured.
> Deleted / Destroyed the consoleproxy and waited till recreation. Which
> didn't worked throwing the error i pasted above.
> Sorry for beeing so unspecific.
>
> Regards,
> Chris
>
> Am Mo., 29. Aug. 2022 um 12:46 Uhr schrieb Slavka Peleva <
> slav...@storpool.com>:
>
>> Hi Chris,
>>
>> I mean to recreate the system VMs by destroying them.
>>
>> On Mon, Aug 29, 2022 at 12:38 PM vas...@gmx.de  wrote:
>>
>>> Hi Slavka,
>>>
>>> didn't tried to restart the SystemVMs. Reading through the docs i had
>>> the impression that "live-patching" would be enough for this
>>> Anyway - I tried my luck with the console proxy.
>>>
>>> Which failed utterly. Not starting as it isn't finding any useable
>>> storage pool. - logs at the end of the mail.
>>>
>>> I tried deploying a VM using the same storage pool which worked
>>> wonderfully.
>>> There i noticed that all my custome storage-offerings are unuseable at
>>> the moment. They are not accepting any custome storage sizes anymore...
>>> Throwing failures "VM Creation failed. Volume size: -1GB is out of allowed
>>> tange. Max:3072 Min:1"...
>>> So this is also currently broken
>>>
>>> 2022-08-29 10:51:56,189 DEBUG [c.c.v.VmWorkJobDispatcher]
>>> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539) (logid:ba10fec5) Run
>>> VM work job: com.cloud.vm.VmWorkStart for VM 83, job origin: 3445
>>> 2022-08-29 10:51:56,191 DEBUG [c.c.v.VmWorkJobHandlerProxy]
>>> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
>>> (logid:ba10fec5) Execute VM work job:
>>> com.cloud.vm.VmWorkStart{"dcId":0,"userId":1,"accountId":1,"vmId":83,"handlerName":"VirtualMachineManagerImpl"}
>>> 2022-08-29 10:51:56,192 DEBUG [c.c.v.VirtualMachineManagerImpl]
>>> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
>>> (logid:ba10fec5) orchestrating VM start for 'v-83-VM'
>>> com.cloud.vm.VirtualMachineProfile$Param@b66cdd7d set to null
>>> 2022-08-29 10:51:56,198 DEBUG [c.c.c.CapacityManagerImpl]
>>> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
>>> (logid:ba10fec5) VM instance {id: "83", name: "v-83-VM", uuid:
>>> "b1d1f9c6-eafe-4527-9335-e649c646aab0", type="ConsoleProxy"} state
>>> transited from [Stopped] to [Starting] with event [StartRequested]. VM's
>>> original host: null, new host: null, host before state transition: null
>>> 2022-08-29 10:51:56,198 DEBUG [c.c.v.VirtualMachineManagerImpl]
>>> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
>>> (logid:ba10fec5) Successfully transitioned to start state for VM instance
>>> {id: "83", name: "v-83-VM", uuid: "b1d1f9c6-eafe-4527-9335-e649c646aab0",
>>> type="ConsoleProxy"} reservation id = 6641ccc0-bcef-4b1a-a1f7-8dd8000626ad
>>> 2022-08-29 10:51:56,203 DEBUG [c.c.v.VirtualMachineManagerImpl]
>>> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
>>> (logid:ba10fec5) Deploy avoids pods: null, clusters: null, hosts: null
&

Re: Error migrate System VMs after upgrageing to 4.17

[Slavka Peleva]

ZXEAfgAFTAANbW9kdWxlVmVyc2lvbnEAfgAFeHABAAAUx3QAA2FwcHQAJmNvbS5jbG91ZC52bS5WaXJ0dWFsTWFjaGluZU1hbmFnZXJJbXBsdAAeVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbC5qYXZhdAAQb3JjaGVzdHJhdGVTdGFydHBwc3EAfgAMAP9wdAAvamRrLmludGVybmFsLnJlZmxlY3QuR2VuZXJhdGVkTWV0aG9kQWNjZXNzb3I5NDVwdAAGaW52b2tlcHBzcQB-AAwCK3B0ADFqZGsuaW50ZXJuYWwucmVmbGVjdC5EZWxlZ2F0aW5nTWV0aG9kQWNjZXNzb3JJbXBsdAAhRGVsZWdhdGluZ01ldGhvZEFjY2Vzc29ySW1wbC5qYXZhcQB-ABR0AAlqYXZhLmJhc2V0AAcxMS4wLjE2c3EAfgAMAgAAAjZwdAAYamF2YS5sYW5nLnJlZmxlY3QuTWV0aG9kdAALTWV0aG9kLmphdmFxAH4AFHEAfgAYcQB-ABlzcQB-AAwBa3EAfgAOdAAiY29tLmNsb3VkLnZtLlZtV29ya0pvYkhhbmRsZXJQcm94eXQAGlZtV29ya0pvYkhhbmRsZXJQcm94eS5qYXZhdAAPaGFuZGxlVm1Xb3JrSm9icHBzcQB-AAwBAAAVP3EAfgAOcQB-AA9xAH4AEHEAfgAgcHBzcQB-AAwBZnEAfgAOdAAgY29tLmNsb3VkLnZtLlZtV29ya0pvYkRpc3BhdGNoZXJ0ABhWbVdvcmtKb2JEaXNwYXRjaGVyLmphdmF0AAZydW5Kb2JwcHNxAH4ADAEAAAJscQB-AA50AD9vcmcuYXBhY2hlLmNsb3Vkc3RhY2suZnJhbWV3b3JrLmpvYnMuaW1wbC5Bc3luY0pvYk1hbmFnZXJJbXBsJDV0ABhBc3luY0pvYk1hbmFnZXJJbXBsLmphdmF0AAxydW5JbkNvbnRleHRwcHNxAH4ADAEwcQB-AA50AD5vcmcuYXBhY2hlLmNsb3Vkc3RhY2subWFuYWdlZC5jb250ZXh0Lk1hbmFnZWRDb250ZXh0UnVubmFibGUkMXQAG01hbmFnZWRDb250ZXh0UnVubmFibGUuamF2YXQAA3J1bnBwc3EAfgAMAQAAADdxAH4ADnQAQm9yZy5hcGFjaGUuY2xvdWRzdGFjay5tYW5hZ2VkLmNvbnRleHQuaW1wbC5EZWZhdWx0TWFuYWdlZENvbnRleHQkMXQAGkRlZmF1bHRNYW5hZ2VkQ29udGV4dC5qYXZhdAAEY2FsbHBwc3EAfgAMAQAAAGZxAH4ADnQAQG9yZy5hcGFjaGUuY2xvdWRzdGFjay5tYW5hZ2VkLmNvbnRleHQuaW1wbC5EZWZhdWx0TWFuYWdlZENvbnRleHRxAH4AMHQAD2NhbGxXaXRoQ29udGV4dHBwc3EAfgAMAQAAADRxAH4ADnEAfgAzcQB-ADB0AA5ydW5XaXRoQ29udGV4dHBwc3EAfgAMAQAAAC1xAH4ADnQAPG9yZy5hcGFjaGUuY2xvdWRzdGFjay5tYW5hZ2VkLmNvbnRleHQuTWFuYWdlZENvbnRleHRSdW5uYWJsZXEAfgAscQB-AC1wcHNxAH4ADAEAAAI4cQB-AA5xAH4AJ3EAfgAocQB-AC1wcHNxAH4ADAIAAAIDcHQALmphdmEudXRpbC5jb25jdXJyZW50LkV4ZWN1dG9ycyRSdW5uYWJsZUFkYXB0ZXJ0AA5FeGVjdXRvcnMuamF2YXEAfgAxcQB-ABhxAH4AGXNxAH4ADAIAAAEIcHQAH2phdmEudXRpbC5jb25jdXJyZW50LkZ1dHVyZVRhc2t0AA9GdXR1cmVUYXNrLmphdmFxAH4ALXEAfgAYcQB-ABlzcQB-AAwCAAAEaHB0ACdqYXZhLnV0aWwuY29uY3VycmVudC5UaHJlYWRQb29sRXhlY3V0b3J0ABdUaHJlYWRQb29sRXhlY3V0b3IuamF2YXQACXJ1bldvcmtlcnEAfgAYcQB-ABlzcQB-AAwCAAACdHB0AC5qYXZhLnV0aWwuY29uY3VycmVudC5UaHJlYWRQb29sRXhlY3V0b3IkV29ya2VycQB-AEJxAH4ALXEAfgAYcQB-ABlzcQB-AAwCAAADPXB0ABBqYXZhLmxhbmcuVGhyZWFkdAALVGhyZWFkLmphdmFxAH4ALXEAfgAYcQB-ABlzcgAfamF2YS51dGlsLkNvbGxlY3Rpb25zJEVtcHR5TGlzdHq4F7Q8p57eAgAAeHB4AAAQmncIAAB4
> 2022-08-29 10:51:56,264 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
> (logid:ba10fec5) Publish async job-3539 complete on message bus
> 2022-08-29 10:51:56,264 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
> (logid:ba10fec5) Wake up jobs related to job-3539
> 2022-08-29 10:51:56,264 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
> (logid:ba10fec5) Update db status for job-3539
> 2022-08-29 10:51:56,266 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539 ctx-073f2751)
> (logid:ba10fec5) Wake up jobs joined with job-3539 and disjoin all subjobs
> created from job- 3539
> 2022-08-29 10:51:56,276 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539) (logid:ba10fec5) Done
> with run of VM work job: com.cloud.vm.VmWorkStart for VM 83, job origin:
> 3445
> 2022-08-29 10:51:56,276 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539) (logid:ba10fec5) Done
> executing com.cloud.vm.VmWorkStart for job-3539
> 2022-08-29 10:51:56,278 INFO  [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-58:ctx-dd8fe695 job-3445/job-3539) (logid:ba10fec5)
> Remove job-3539 from job monitoring
> 2022-08-29 10:51:56,285 WARN  [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-88c25b3a) (logid:d39faaa7) Unable to allocate console
> proxy standby capacity for zone [1] due to [Unable to orchestrate start VM
> instance {id: "83", name: "v-83-VM", uuid:
> "b1d1f9c6-eafe-4527-9335-e649c646aab0", type="ConsoleProxy"} due to [Unable
> to create deployment, no usable volumes found for the VM: 83].].
> com.cloud.utils.exception.CloudRuntimeException: Unable to orchestrate
> start VM instance {id: "83", name: "v-83-VM", uuid:
> "b1d1f9c6-eafe-4527-9335-e649c646aab0", type="ConsoleProxy"} due to [Unable
> to create deployment, no usable volumes found for the VM: 83].
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5319)
> at jdk.internal.reflect.GeneratedMethodAccessor945.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> com.cloud.vm.VmWorkJobHandlerProxy

Re: Error migrate System VMs after upgrageing to 4.17

[Slavka Peleva]

Hi Chris,

Did you recreate the system VMs? In the 4.17 version, the `systemvm.iso` is
deprecated. In its place, you should have the file on agents
`/usr/share/cloudstack-common/vms/agent.zip`.
Can you share the complete log if the system VMs are newly created after
the upgrade?

Best regards,
Slavka

On Sun, Aug 28, 2022 at 2:16 PM vas...@gmx.de  wrote:

> Hi everyone,
>
> faceing some challanges again after upgradeing to 4.17.
> Did as explained in the docs.
>
> Afterwards I am now not able to migrate system VMs to different hosts.
> Getting the error
> "Exception during migrate: org.libvirt.LibvirtException: Cannot access
> storage file '/usr/share/cloudstack-common/vms/systemvm.iso': No such file
> or directory"
>
> Checked the exitstence of the file on the servers:
> Mangement-Server has a "systemvm.iso.bak"
> Hosts - no "systemvm.iso" at all present.
>
> Maybe someone has an idea on how to move on with this?
>
> Regards,
> Chris
>

Re: Problem creating a VM

[Slavka Peleva]

Thanks for the logs!

Do you have another primary storage, or do you use only the local one?

   - Can you check if local storage is enabled for the Zone?
   - Check the tags of the primary storage. Also, the scope has to be
   `HOST` and the type `FileSystem`.
   - Check the storage tags of the compute offering (they should be the
   same as the primary storage tags) and the Storage type - it should be
   `local`. Sometimes I forget to mark it as a local when creating a new
   Service offering, and I face the same problem when I try to deploy a VM.

Best regards,
Slavka


On Sun, Aug 21, 2022 at 4:14 PM Aufgabe Zwei  wrote:

> Hi,
> thank you for the quick responses.
>
> @Slavka is right. I tried the suggestions in the advisory but it didn't
> work.
>
> I am actually doing a single machine deployment. One thing is that, when I
> try to attach a volume with the attach volume button, no vm is displayed in
> the vm drop down.
> The vm status is: Error
> I'm getting this when I try to create new instance
> No destination found for a deployment for VM instance
>
>
>
> agent-log:
>
> >
> > 2022-08-21 12:39:32,721 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:39:32,721 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:39:32,721 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:39:37,722 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:39:37,722 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:39:37,723 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:39:42,723 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:39:42,724 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:39:42,724 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:39:47,725 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:39:47,725 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:39:47,726 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:39:52,726 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:39:52,727 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:39:52,727 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:39:57,728 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:39:57,728 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:39:57,728 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:40:02,729 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:40:02,729 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:40:02,729 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:40:07,729 INFO  [cloud.agent.Agent] (Agent-Handler-3:null)
> > (logid:) Reconnecting to host:192.168.122.10
> > 2022-08-21 12:40:07,730 INFO  [utils.nio.NioClient]
> (Agent-Handler-3:null)
> > (logid:) Connecting to 192.168.122.10:8250
> > 2022-08-21 12:40:07,730 WARN  [utils.nio.NioConnection]
> > (Agent-Handler-3:null) (logid:) Unable to connect to remote: is there a
> > server running on port 8250
> > 2022-08-21 12:40:09,789 INFO  [cloud.agent.Agent]
> > (AgentShutdownThread:null) (logid:) Stopping the agent: Reason = sig.kill
> > 2022-08-21 12:40:11,109 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:) Agent started
> > 2022-08-21 12:40:11,111 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:) Implementation Version is 4.17.0.1
> > 2022-08-21 12:40:11,113 INFO  [cloud.agent.AgentShell] (main:null)
> > (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
> > 2022-08-21 12:40:11,118

Re: Problem creating a VM

[Slavka Peleva]

Hi,

Can you share everything from the management log with `logid:0e77f2bc`
because it's not the whole log for this call (StartVMCmdByAdmin)?

According to your shared log, no volumes are allocated to the pool. Also,
is this VM already worked and then destroyed (without expunging)? What is
the current state of the VM? Probably the deployment failed, and you tried
to start the VM.
If possible, can you try to deploy a new VM and share the log?

Chris, the problem mentioned in the advisory shouldn't affect local storage.

Best regards,
Slavka

On Sun, Aug 21, 2022 at 2:51 PM vas...@gmx.de  wrote:

> HI,
>
> as a quick thought - have you seen the following advisorty
>
> https://blogs.apache.org/cloudstack/entry/advisory-apache-cloudstack-advisory-on
>
> also it would be helpful to see the agent logs from the host where the VM
> shall be deployed to.
> Regards,
> Chris
>
> Am So., 21. Aug. 2022 um 13:09 Uhr schrieb Aufgabe Zwei <
> aufgabez...@gmail.com>:
>
> > Hello,
> >
> > I would be grateful if you can assist or point me in the right direction.
> >
> > I have tried for almost a month to create a test deployment of cloudstack
> > but each time I get to creating a vm instance, I get the error message
> >
> > Start instance
> > > (VM1) Unable to create deployment, no usable volumes found for the VM:
> > 1015
> > >
> >
> > I tried to find a fix on my own and have literally done a lot of
> searching
> > and reading around but I just can find the reason.
> >
> > I have ensured that the host, storage are correctly tagged. I have
> enabled
> > local storage and created local service offerings
> >
> > I followed these guides:
> >
> > Quick Installation Guide — Apache CloudStack 4.17.0.0 documentation
> > <
> >
> http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html#setting-up-a-zone
> > >
> >
> > hackerbook/1-user.md at main · shapeblue/hackerbook · GitHub
> > 
> >
> > Thank you
> >
> > management log:
> >
> > > 2022-08-21 10:58:58,379 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > Trying to allocate a host and storage pools from dc:1,
> > > pod:null,cluster:null, requested cpu: 4500, requested ram: (2.00 GB)
> > > 2147483648
> > > 2022-08-21 10:58:58,379 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > Is
> > > ROOT volume READY (pool already allocated)?: No
> > > 2022-08-21 10:58:58,381 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > Deploy avoids pods: [], clusters: [], hosts: []
> > > 2022-08-21 10:58:58,381 DEBUG [c.c.d.FirstFitPlanner]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > Searching all possible resources under this Zone: 1
> > > 2022-08-21 10:58:58,382 DEBUG [c.c.d.FirstFitPlanner]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > Listing clusters in order of aggregate capacity, that have (at least
> one
> > > host with) enough CPU and RAM capacity under this Zone: 1
> > > 2022-08-21 10:58:58,383 DEBUG [c.c.d.FirstFitPlanner]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > Removing from the clusterId list these clusters from avoid set: []
> > > 2022-08-21 10:58:58,384 DEBUG [c.c.d.FirstFitPlanner]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > The clusterId list for the given offering tag: [1]
> > > 2022-08-21 10:58:58,385 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb)
> (logid:0e77f2bc)
> > > Checking resources in Cluster: 1 under Pod: 1
> > > 2022-08-21 10:58:58,386 INFO  [c.c.a.m.a.i.FirstFitAllocator]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb
> > > FirstFitRoutingAllocator) (logid:0e77f2bc)  Guest VM is requested with
> > > Custom[UEFI] Boot Type false
> > > 2022-08-21 10:58:58,386 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb
> > > FirstFitRoutingAllocator) (logid:0e77f2bc) Looking for hosts in dc: 1
> > >  pod:1  cluster:1
> > > 2022-08-21 10:58:58,386 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb
> > > FirstFitRoutingAllocator) (logid:0e77f2bc) Looking for hosts having tag
> > > specified on SvcOffering:local
> > > 2022-08-21 10:58:58,386 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> > > (API-Job-Executor-8:ctx-a898686b job-3069 ctx-2b5b16cb
> > > FirstFitRoutingAllocator) (logid:0e77f2bc) Hosts with tag 'local'
> > are:[Host
> > > {"id": "43", "name": "rs2", "uuid":
> > "a3c2ef7e-d639-4dba-b727-e7bd0c371e4c",
> > > "type"="Routing"}]
> > > 2022-08-21 10:58:58,386 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> > > (API-Job-Executor-8:ctx-

Re: VR for VPC won't start anymore

[Slavka Peleva]

Hi Christopher,

I did some tests in my lab, and maybe the more painless way to try to solve
this problem is:


   - Register a new systemvm template from here - system vm template
   <https://download.cloudstack.org/systemvm/4.16/>
   - When it is downloaded and installed, check its `template.properties`
   file to see if everything is there. Also, check the record in the DB
   - If everything looks alright - update the `type` of this template in
   the vm_template table to SYSTEM
   - Go to the configurations menu and search for `router.template.kvm`.
   Update the value with the name of the new systemvm template and restart the
   management.


With this change, CS will try to create the VR with the new template. If
that doesn't work, you could update the setting `router.template.kvm` to
its old value.

Best regards,
Slavka

On Fri, Aug 5, 2022 at 1:07 PM vas...@gmx.de  wrote:

> Hi Slavka,
>
> thank you for your explanations - really nice to have some insides of this
> whole process.
> Regarding your questions:
>
> secondary stoage vm, console proxy were created with the same template.
>
> So what has happend - i had som brief discussions with our admin team to
> get things together:
> Basically it seems that we have these problems since we tried to upgrade
> the environment to 4.17 (from the information i have, the team tried to do
> this before beeing aware of the advisory - otherwise i would have suggested
> to skip 4.17 and wait for 4.17.1 / 4.18). How ever the upgrade process
> failed for us and so we rolled back to 4.16.1. It seems that something went
> wrong in this process - as the problems occured since then. The guys
> responsible for performing the update meant, that some parts of the
> upgrade-guide where not quiet clear - especially the part on how to deploy
> the new systemvm templates since the changes made in 4.16 / 4.16.1.
>
> The environment itself "was" build up as a testbed - sadly some people
> where thinking that you can deploy services and make them useable in daily
> work - meaning its now something i would call "semi-productive" So i
> can't just throw everything away and build it newly ...
> That's why i hope to get around the corner on "fixing" the current
> systemVM-Template / database and migrate as fast as possible to 4.17.1 -
> making the current systemtemplate "obsolete".
>
> Regards,
> Chris
>
> Am Fr., 5. Aug. 2022 um 10:16 Uhr schrieb Slavka Peleva <
> slav...@storpool.com>:
>
>> Hi Christopher,
>>
>> Just for understanding:
>>> When deploying a new "systemvm"-template, which i normally would do
>>> while upgardeing mi CS-Environment, the values of the template.properties
>>> will be transfaired into DB. The management server will then make use of
>>> the values which are stored in the DB?
>>
>>
>> Yes. When the system VM template is seeded, CS (or you do it manually)
>> executes a script which creates the `template.properties` file and fills it
>> with the information you shared. Then it takes from it the data and updates
>> the DB. In your `template.properties` file, the `virtualsize` is empty.
>> Probably something happened while the `qemu-img info` (from that script)
>> was executed.
>>
>> I can't advise you on how to proceed because I don't know what steps you
>> made before. Is this a test setup?
>>
>> Are the system VMs (secondary storage/console proxy VMs) created with the
>> same template? Can you check when they are deployed, and are there any
>> updates on this template? You can find the info for the template in the
>> template_store_ref table -> created and last_updated columns.
>>
>> Best regards,
>> Slavka
>>
>> On Thu, Aug 4, 2022 at 9:50 PM vas...@gmx.de  wrote:
>>
>>> hi slavka,
>>> i checked the log and didn't found anything like "failed to read from
>>> template.properties".
>>>
>>> Just for understanding:
>>> When deploying a new "systemvm"-template, which i normally would do
>>> while upgardeing mi CS-Environment, the values of the template.properties
>>> will be transfaired into DB. The management server will then make use of
>>> the values which are stored in the DB?
>>>
>>> i destroyed the "stopped" router in my installation and triggered a
>>> re-deployment. The term "template" is mentioned inside the logs only for
>>> two reasons:
>>> 1. Successfull router health check of the running router (the primary
>>> one of my vpc)
>>> 2. In the mentioned error log
>>> &quo

Re: VR for VPC won't start anymore

[Slavka Peleva]

Hi Christopher,

Just for understanding:
> When deploying a new "systemvm"-template, which i normally would do while
> upgardeing mi CS-Environment, the values of the template.properties will be
> transfaired into DB. The management server will then make use of the values
> which are stored in the DB?


Yes. When the system VM template is seeded, CS (or you do it manually)
executes a script which creates the `template.properties` file and fills it
with the information you shared. Then it takes from it the data and updates
the DB. In your `template.properties` file, the `virtualsize` is empty.
Probably something happened while the `qemu-img info` (from that script)
was executed.

I can't advise you on how to proceed because I don't know what steps you
made before. Is this a test setup?

Are the system VMs (secondary storage/console proxy VMs) created with the
same template? Can you check when they are deployed, and are there any
updates on this template? You can find the info for the template in the
template_store_ref table -> created and last_updated columns.

Best regards,
Slavka

On Thu, Aug 4, 2022 at 9:50 PM vas...@gmx.de  wrote:

> hi slavka,
> i checked the log and didn't found anything like "failed to read from
> template.properties".
>
> Just for understanding:
> When deploying a new "systemvm"-template, which i normally would do while
> upgardeing mi CS-Environment, the values of the template.properties will be
> transfaired into DB. The management server will then make use of the values
> which are stored in the DB?
>
> i destroyed the "stopped" router in my installation and triggered a
> re-deployment. The term "template" is mentioned inside the logs only for
> two reasons:
> 1. Successfull router health check of the running router (the primary one
> of my vpc)
> 2. In the mentioned error log
> " at
> org.apache.cloudstack.storage.datastore.db.TemplateDataStoreVO.getSize(TemplateDataStoreVO.java:280)
> at
> com.cloud.template.TemplateManagerImpl.getTemplateSize(TemplateManagerImpl.java:2009)
> "
>
> so the question for me is  - can i manually place the missing values in
> the DB, so that the template is useable again? Or will i wait until i
> upgrade to 4.17.1 - which might bring a new systemVM template which will
> then be seeded again ?
>
> Regards,
> Chris
>
> Am Do., 4. Aug. 2022 um 19:10 Uhr schrieb Slavka Peleva <
> slav...@storpool.com>:
>
>> Hi Christopher,
>>
>> For some reason, these fields' values are empty, which probably
>> happened while you seed the system VM template.
>>
>>> qcow2.virtualsize=
>>> virtualsize=
>>> qcow2.size=
>>
>>
>> From the DB record, the only option for the values of physical_size = 0
>> and size=Null, is that CS couldn't read the `template.properties` file. Can
>> you search in the management log file for a message like "Failed to read
>> from template.properties"? It should contain more detailed information
>> about the failure.
>>
>> Best regards,
>> Slavka
>>
>> On Thu, Aug 4, 2022 at 7:13 PM vas...@gmx.de  wrote:
>>
>>> Hi everyone -
>>>
>>> @Gary
>>> thanks for your input
>>>
>>> @Wei ZHOU 
>>> Yes, the image is completely downloaded to the imagestore. I also checked
>>> the availeabilty on the storage beneath - everything seems to be in place
>>> like it should
>>>
>>> Following the values out ouf the db you requested:
>>> id= 18
>>> store_id = 1
>>> download_pct = 100
>>> size = "NULL"
>>> store_role = Image
>>> physical_size = 0
>>> download_state = DOWNLOADED
>>> state = READY
>>> install_path =
>>> /template/tmpl/1/212/0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>>>
>>> @Slavka
>>> Following the information of the 'template.properties'
>>>
>>> filename=0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>>> description=SystemVM Template ( kvm )
>>> hvm=false
>>> size=460067328
>>> qcow2=true
>>> id=212
>>> public=true
>>> qcow2.filename=0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>>> uniquename=routing-212
>>> qcow2.virtualsize=
>>> virtualsize=
>>> qcow2.size=
>>>
>>> Regards,
>>> Chris
>>>
>>> Am Do., 4. Aug. 2022 um 12:05 Uhr schrieb Slavka Peleva
>>> :
>>>
>>> > Hi Christopher,
>>> >
>>> > Can you share the information of the `template.properties` file
&g

Re: VR for VPC won't start anymore

[Slavka Peleva]

Hi Christopher,

For some reason, these fields' values are empty, which probably
happened while you seed the system VM template.

> qcow2.virtualsize=
> virtualsize=
> qcow2.size=


>From the DB record, the only option for the values of physical_size = 0 and
size=Null, is that CS couldn't read the `template.properties` file. Can you
search in the management log file for a message like "Failed to read from
template.properties"? It should contain more detailed information about the
failure.

Best regards,
Slavka

On Thu, Aug 4, 2022 at 7:13 PM vas...@gmx.de  wrote:

> Hi everyone -
>
> @Gary
> thanks for your input
>
> @Wei ZHOU 
> Yes, the image is completely downloaded to the imagestore. I also checked
> the availeabilty on the storage beneath - everything seems to be in place
> like it should
>
> Following the values out ouf the db you requested:
> id= 18
> store_id = 1
> download_pct = 100
> size = "NULL"
> store_role = Image
> physical_size = 0
> download_state = DOWNLOADED
> state = READY
> install_path =
> /template/tmpl/1/212/0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>
> @Slavka
> Following the information of the 'template.properties'
>
> filename=0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
> description=SystemVM Template ( kvm )
> hvm=false
> size=460067328
> qcow2=true
> id=212
> public=true
> qcow2.filename=0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
> uniquename=routing-212
> qcow2.virtualsize=
> virtualsize=
> qcow2.size=
>
> Regards,
> Chris
>
> Am Do., 4. Aug. 2022 um 12:05 Uhr schrieb Slavka Peleva
> :
>
> > Hi Christopher,
> >
> > Can you share the information of the `template.properties` file located
> on
> > your secondary storage, where the template file is downloaded? You can
> find
> > the path in the template_store_ref tabled - install_path.
> >
> > Best regards,
> > Slavka
> >
> > On Thu, Aug 4, 2022 at 12:41 PM Gary Dixon  > .invalid>
> > wrote:
> >
> > > Hi Christopher
> > >
> > > My values show :
> > > size=262144 physical size=375471104 and this is for a 4.15.1
> systemVM
> > > template
> > >
> > > BR
> > > Gary
> > >
> > > Gary Dixon​
> > > Senior Technical Consultant
> > > T:  *0161 537 4980* <0161%20537%204980>
> > > W: www.quadris.co.uk
> > > The information contained in this e-mail from Quadris may be
> confidential
> > > and privileged for the private use of the named recipient.  The
> contents
> > of
> > > this e-mail may not necessarily represent the official views of
> Quadris.
> > > If you have received this information in error you must not copy,
> > > distribute or take any action or reliance on its contents.  Please
> > destroy
> > > any hard copies and delete this message.
> > > -Original Message-
> > > From: vas...@gmx.de 
> > > Sent: 04 August 2022 09:40
> > > To: users@cloudstack.apache.org; Wei ZHOU 
> > > Subject: Re: VR for VPC won't start anymore
> > >
> > > I forgot to ask - might anyone take a quick look into the database and
> > can
> > > give a hind if the fields are indeed "filled" with values
> > > (template_store_res.size / template_store_res.physical_size)?
> > > Another question for understanding would be the difference of the
> values
> > -
> > > physical size is the actual amount of data on a datasystemlevel - but
> > what
> > > represents the value of "size"?
> > >
> > > Regards,
> > > Christopher
> > >
> > > Am Mi., 3. Aug. 2022 um 23:14 Uhr schrieb vas...@gmx.de  >:
> > >
> > > > Wei, seems like you are heading twards the right direction - like
> > always.
> > > >
> > > > i took a look into the "template_store_res" table... and guess: There
> > > > is a entry for the current systemvmtemplate-4.16.1. How ever: The
> > > > field for "size" ist "null" and "physical_size" is "0".
> > > >
> > > > Might this be the reason for the " java.lang.NullPointerException" ?
> > > >
> > > > Regards,
> > > > Chris
> > > >
> > > > Am Mi., 3. Aug. 2022 um 21:56 Uhr schrieb Wei ZHOU
> > > >  > > > >:
> > > >
> > > >> It looks there is no entry in template_store_ref table for the
> > > >> systemvm template
&

Re: VR for VPC won't start anymore

[Slavka Peleva]

Hi Christopher,

Can you share the information of the `template.properties` file located on
your secondary storage, where the template file is downloaded? You can find
the path in the template_store_ref tabled - install_path.

Best regards,
Slavka

On Thu, Aug 4, 2022 at 12:41 PM Gary Dixon 
wrote:

> Hi Christopher
>
> My values show :
> size=262144 physical size=375471104 and this is for a 4.15.1 systemVM
> template
>
> BR
> Gary
>
> Gary Dixon​
> Senior Technical Consultant
> T:  *0161 537 4980* <0161%20537%204980>
> W: www.quadris.co.uk
> The information contained in this e-mail from Quadris may be confidential
> and privileged for the private use of the named recipient.  The contents of
> this e-mail may not necessarily represent the official views of Quadris.
> If you have received this information in error you must not copy,
> distribute or take any action or reliance on its contents.  Please destroy
> any hard copies and delete this message.
> -Original Message-
> From: vas...@gmx.de 
> Sent: 04 August 2022 09:40
> To: users@cloudstack.apache.org; Wei ZHOU 
> Subject: Re: VR for VPC won't start anymore
>
> I forgot to ask - might anyone take a quick look into the database and can
> give a hind if the fields are indeed "filled" with values
> (template_store_res.size / template_store_res.physical_size)?
> Another question for understanding would be the difference of the values -
> physical size is the actual amount of data on a datasystemlevel - but what
> represents the value of "size"?
>
> Regards,
> Christopher
>
> Am Mi., 3. Aug. 2022 um 23:14 Uhr schrieb vas...@gmx.de :
>
> > Wei, seems like you are heading twards the right direction - like always.
> >
> > i took a look into the "template_store_res" table... and guess: There
> > is a entry for the current systemvmtemplate-4.16.1. How ever: The
> > field for "size" ist "null" and "physical_size" is "0".
> >
> > Might this be the reason for the " java.lang.NullPointerException" ?
> >
> > Regards,
> > Chris
> >
> > Am Mi., 3. Aug. 2022 um 21:56 Uhr schrieb Wei ZHOU
> >  > >:
> >
> >> It looks there is no entry in template_store_ref table for the
> >> systemvm template
> >>
> >> -Wei
> >>
> >> On Wed, 3 Aug 2022 at 21:43, vas...@gmx.de  wrote:
> >>
> >> > Hi everyone,
> >> >
> >> > faceing currently some challanges regarding my network
> >> > configuration in
> >> CS
> >> > 4.16.1.
> >> >
> >> > Setup:
> >> > VPC with redundant routers and some tiers as well as an private
> gateway.
> >> >
> >> > Today i wanted to restart the whole VPC - sadly only one vrouter
> >> > "survived"  Currently i can't depoly any networks in or outside
> >> > the VPC. Also the second router shall be delployed but keeps in the
> >> > stopped state.
> >> > I really dont have a clue where to look at first...
> >> >
> >> > here the logfile from the Management-Server:
> >> >
> >> > 2022-08-03 20:35:48,768 DEBUG [c.c.n.r.NetworkHelperImpl]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Allocating the VR with id=74 in datacenter Zone {"id": "1", "name":
> >> > "xx", "uuid": "48e2e928-3300-43b5-8e3a-d>
> >> > 2022-08-03 20:35:48,776 DEBUG [c.c.n.r.NetworkHelperImpl]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Adding nic for Virtual Router in Control network
> >> > 2022-08-03 20:35:48,781 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Found existing network configuration for offering [Network Offering
> >> > [3-Control-System-Control-Network]: Ntwk[202|>
> >> > 2022-08-03 20:35:48,781 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Releasing lock for
> >> > Acct[60bddbd5-1d8a-11ec-83ce-525400c9c662-system] -- Account {"id":
> >> > 1, "name": "system", "uuid>
> >> > 2022-08-03 20:35:48,785 DEBUG [c.c.n.r.NetworkHelperImpl]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Adding nic for Virtual Router in Public network
> >> > 2022-08-03 20:35:48,789 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Found existing network configuration for offering [Network Offering
> >> > [1-Public-System-Public-Network]: Ntwk[200|Pu>
> >> > 2022-08-03 20:35:48,789 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Releasing lock for
> >> > Acct[60bddbd5-1d8a-11ec-83ce-525400c9c662-system] -- Account {"id":
> >> > 1, "name": "system", "uuid>
> >> > 2022-08-03 20:35:48,793 INFO [c.c.n.r.NetworkHelperImpl]
> >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
> >> (logid:6b6b9867)
> >> > Use same MAC as previous RvR, the MAC is 1e:00:59:00:00:b2
> >> > 2022-08-03 20:35:48,793 DEBUG [c.c.n.r.NetworkHelperImpl]

Fwd: [VOTE] Apache Cloudstack 4.17.0.0 RC4

[Slavka Peleva]

Sorry, I've missed to add and the users' list

-- Forwarded message -----
From: Slavka Peleva 
Date: Thu, Jun 2, 2022 at 6:47 PM
Subject: Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4
To: dev 


Hi all,

+1

Tested with Basic Zone on Rocky Linux with KVM hypervisors.
- live migration
- live migration with storage
- basic VM operations - VM snapshots with memory/ without memory,
revert/delete
- register iso/template and deploy VM from it
- tested UEFI support
- basic volume and snapshot operations with StorPool/NFS/Ceph storage
- executed a few smoke tests

Best regards,
Slavka


On Thu, Jun 2, 2022 at 4:04 PM Rohit Yadav 
wrote:

> +1 (binding)
>
> Testing 4.17.0.0 RC4 using mbx, tested EL7 kvm based env and basic VM,
> volume, network, template and systemvm/router workflows.
>
>
> Regards.
>
> 
> From: Nicolas Vazquez 
> Sent: Wednesday, June 1, 2022 02:33
> To: users@cloudstack.apache.org ;
> d...@cloudstack.apache.org 
> Subject: Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4
>
> Sorry for the typo – meant RC4 instead of RCR :)
>
> For testing purposes, I have uploaded convenience packages to:
> https://download.cloudstack.org/testing/4.17.0.0-RC4/
>
> The system VM template can be downloaded from here if needed:
> https://download.cloudstack.org/systemvm/4.17
>
> Regards,
> Nicolas Vazquez
>
>
> From: Nicolas Vazquez 
> Date: Tuesday, 31 May 2022 at 14:40
> To: d...@cloudstack.apache.org , users <
> users@cloudstack.apache.org>
> Subject: [VOTE] Apache Cloudstack 4.17.0.0 RC4
> Hi all,
>
> I have created a 4.17.0.0 release (RCR) with the following artefacts up
> for testing and a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
> Commit: c56220fcf2348c7809331dcc266775f3d7130fe6
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.17.0.0/
>
> PGP release keys (signed using 239A653975E13A0EEF5122A1656E1BCC8CB54F84):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 6th June 2022.
>
> 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)
>
> Regards,
> Nicolas Vazquez
>
>
>
>
>
>
>
>
>
>

Re: Cludstack vm backup

[Slavka Peleva]

Hi Mariusz,

The dummy backup plugin is only for tests. Only the Veeam backup provider
is supported for now by CS, which works with VMware HW.

Best regards,
Slavka

On Fri, May 27, 2022 at 11:09 AM Mariusz Wojtarek <
mariusz.wojta...@support-online.pl> wrote:

> Hi,
>
> I am using cloudstack with kvm should dummy backup works with vms host on
> kvm ? when I try to make backup using dummy it not working, every backup
> size is 1GB.
>
>
>
>
> 
> Support OnLine Sp. z o.o., ul. Poleczki 23, 02-822 Warszawa, NIP:
> 951-20-32-692, Regon: 017431965, KRS: 078497,
> XIII Wydzia? Gospodarczy Krajowego Rejestru S?dowego w Warszawie, Kapita?
> zak?adowy: 50 000 PLN - op?acony w pe?nej wysoko?ci.
> W przypadku podania w ramach niniejszej korespondencji Pa?stwa danych
> osobowych, prosimy zapozna? si? z nast?puj?c? informacj?
> https://www.support-online.pl/dane-osobowe
> In case any of your private data was included within this conversation,
> please consult this website https://www.support-online.pl/en/personal-data
>

Re: Cannot create vmsnapshot

[Slavka Peleva]

Yes, it's not possible to take VM snapshot with Ceph as primary storage.
There is an alternative included in 4.17 (still not released) for those
storage drivers that are using the raw format - KVM VM snapshots improvement


Best regards,
Slavka

Re: Cannot create vmsnapshot

[Slavka Peleva]

Hi Ricardo,

I would not recommend you to update the DB manually. The format is set
depending on which primary storage you are using. You can double-check what
is the image format with `virsh dumpxml --domain vm-id`. Currently, libvirt
doesn't support internal snapshots with disks in raw format.

Best regards,
Slavka

On Fri, Apr 29, 2022 at 1:14 AM Ricardo Pertuz 
wrote:

> Hi Wei,
>
> It's RAW, what should be done, can I change it manually? The vms are
> deployed without any "RAW" parameter
>
> +--++
> | uuid   | format
>  |
> +--++
> | a73edffd--4fbc-b5a4-bf72ad72ee44 | RAW|
> +--++
>
>
>
> On 28/04/22, 2:53 PM, "Wei ZHOU"  wrote:
>
> Hi Ricardo,
>
> hypervisor looks good.
>
> You can get the volume format by db query.
> select format from volumes where id=xxx;
>
> -Wei
>
> On Thu, 28 Apr 2022 at 21:24, Ricardo Pertuz  >
> wrote:
>
> > Thanks Wei
> >
> > VM
> > 
> > hypervisor:"KVM"
> >
> > Volume
> > -
> > hypervisor:"KVM"
> >
> > Where can I find the volume format?
> >
> >
> >
> > On 28/04/22, 11:59 AM, "Wei ZHOU"  wrote:
> >
> > Hi Ricardo,
> >
> > The template looks good. Could you please check the hypervisor
> type of
> > the
> > vm and the format of the volume ?
> >
> > -Wei
> >
> >
> > On Thu, 28 Apr 2022 at 18:33, Ricardo Pertuz <
> ricardo.per...@kuasar.co
> > >
> > wrote:
> >
> > > Hi,
> > >
> > > I am not able to create vmsnapshot on ACS 4.15.2, not sure
> what I’m
> > > missing, even though the error is very clear
> > >
> > > "HTTP: 530, error code: 4250, error message: We only support
> create
> > vm
> > > snapshots from vm with QCOW2 image"
> > >
> > > However the underlying image is QCOW2, not sure if there is
> global
> > setting
> > > I have to permit
> > >
> > >   "template": [
> > > {
> > >   "account": "admin",
> > >   "bits": 0,
> > >   "checksum":
> > >
> >
> "5c30c580180e55b277b7b9b0449c7f524a40d3abd424a5ae986cf2e2274c5acd4f1491d050139c50e039168f3e112d186bd368fd9faeb4f1998ddae1391ebfac",
> > >   "created": "2022-04-25T17:58:20-0500",
> > >   "crossZones": true,
> > >   "deployasis": false,
> > >   "details": {},
> > >   "directdownload": false,
> > >   "displaytext": "",
> > >   "domain": "ROOT",
> > >   "domainid": "3d529151-0f38-11ec-8796-02005d71003e",
> > >   "downloaddetails": [
> > > {
> > >   "datastore": "x",
> > >   "downloadPercent": "100",
> > >   "downloadState": "DOWNLOADED"
> > > }
> > >   ],
> > >   "format": "QCOW2",
> > >   "hypervisor": "KVM",
> > >   "id": "37994ffb-4ea5-4411-bf69-ebf39bd04a9a",
> > >   "isdynamicallyscalable": false,
> > >   "isextractable": false,
> > >   "isfeatured": true,
> > >   "ispublic": true,
> > >   "isready": true,
> > >   "name": "xx",
> > >   "ostypeid": "xx",
> > >   "ostypename": "Debian GNU/Linux 10 (64-bit)",
> > >   "passwordenabled": false,
> > >   "physicalsize": 2604466176,
> > >   "requireshvm": true,
> > >   "size": 160,
> > >   "sshkeyenabled": true,
> > >   "status": "Download Complete",
> > >   "tags": [],
> > >   "templatetype": "USER",
> > >   "url": "xx
> > >   "zoneid": "x",
> > >   "zonename": ""
> > > }
> > >
> >
> >
>
>

Re: libvirt.vif.driver ignored in ACS 4.16

[Slavka Peleva]

Hi Felipe,

Did you restart the agent after updating the `agent.properties` file? I've
set this on my lab with the values you have shared, and it gets the correct
Vif driver.

Best regards,
Slavka

On Thu, Apr 28, 2022 at 1:28 AM Felipe Polanco 
wrote:

> Hi,
>
> We are trying to setup Open Vswitch in ACS 4.16 and we have added the
> following lines to the agent config file and manually created the bridges
> in OVS:
>
> network.bridge.type=openvswitch
> libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.OvsVifDriver
>
> # ovs-vsctl show
> a6558802-d843-4285-90bc-c884ee9df0d2
> Bridge cloudbr0
> Port bond0
> Interface eth2
> Interface eth3
> Port cloudbr0
> Interface cloudbr0
> type: internal
> Port vlan110
> tag: 110
> Interface vlan110
> type: internal
> Port vlan100
> tag: 100
> Interface vlan100
> type: internal
> ovs_version: "2.13.5"
>
>
>
> However, cloudstack-agent keeps crashing with error about not being able to
> find the private NIC and that the libvirt.vif.driver is not specified and
> is defaulting to BridgeVifDriver and failing
>
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.agent.AgentShell]
> (main:) (logid:) Agent started
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.agent.AgentShell]
> (main:) (logid:) Implementation Version is 4.16.1.0
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.agent.AgentShell]
> (main:) (logid:) agent.properties found at
> /etc/cloudstack/agent/agent.properties
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.agent.AgentShell]
> (main:) (logid:) Defaulting to using properties file for storage
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.agent.AgentShell]
> (main:) (logid:) Defaulting to the constant time backoff algorithm
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.utils.LogUtils] (main:)
> (logid:) log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
> Mar 24 21:50:10 PS-NODE5 java[164130]: INFO  [cloud.agent.AgentShell]
> (main:) (logid:) Using default Java settings for IPv6 preference for agent
> connection
> Mar 24 21:50:11 PS-NODE5 java[164130]: INFO  [cloud.agent.Agent] (main:)
> (logid:) id is
> Mar 24 21:50:11 PS-NODE5 java[164130]: WARN
>  [cloud.resource.ServerResourceBase] (main:) (logid:) Nics are not
> specified in properties file/db, will try to au
> todiscover
> Mar 24 21:50:11 PS-NODE5 java[164130]: INFO
>  [cloud.resource.ServerResourceBase] (main:) (logid:) Designating private
> to be nic cni-podman0
> Mar 24 21:50:11 PS-NODE5 java[164130]: ERROR
> [kvm.resource.LibvirtComputingResource] (main:) (logid:) uefi properties
> file not found due to: Unable to find fi
> le uefi.properties.
> Mar 24 21:50:11 PS-NODE5 java[164130]: INFO
>  [kvm.resource.LibvirtConnection] (main:) (logid:) No existing libvirtd
> connection found. Opening a new one
> Mar 24 21:50:11 PS-NODE5 java[164130]: WARN
>  [kvm.storage.KVMStoragePoolManager] (main:) (logid:) Duplicate
> StorageAdaptor type PowerFlex, not loading com.clo
> ud.hypervisor.kvm.storage.ScaleIOStorageAdaptor
> Mar 24 21:50:11 PS-NODE5 java[164130]: INFO
>  [kvm.resource.LibvirtComputingResource] (main:) (logid:) *No
> libvirt.vif.driver specified. Defaults to BridgeVifDr*
> iver.
> Mar 24 21:50:11 PS-NODE5 java[164130]: ERROR
> [kvm.resource.LibvirtComputingResource] (main:) (logid:) Failed to get
> private nic name
> Mar 24 21:50:11 PS-NODE5 java[164130]: ERROR [cloud.agent.AgentShell]
> (main:) (logid:) Unable to start agent: Failed to get private nic name
>
> Any idea why the agent would ignore this line?
>
> Thanks,
>

Re: Secondary Storage Check Capacity

[Slavka Peleva]

Hi Evgeniy,

I have never changed the size of the secondary storage, but CS should
recalculate the new size (after a quick code check). The new value will be
applied after the interval set in `storage.stats.interval` (configuration
setting)

Best regards,
Slavka

On Thu, Mar 24, 2022 at 2:49 PM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> MB someone are changed size of existing Secondary Storage?
> I have 1 NFS server which I use as Secondary Storage. Now I have to shrink
> it. If I do it does CS recalculate size of storage?
>
>
>
>
>
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> 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: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon Weller

[Slavka Peleva]

Congratulations and good luck, Simon! Thank you, Gabriel, for your great
work!

Best regards,
Slavka

On Thu, Mar 17, 2022 at 12:57 PM Rohit Yadav  wrote:

> Congratulations Simon! And thank you Gabriel.
>
> Regards.
>
> On Thu, Mar 17, 2022 at 3:25 PM Gabriel Beims Bräscher
>  wrote:
> >
> > Hello, all CloudStack community!
> >
> > It gives me great pleasure to announce that the ASF board last night
> accepted
> > our PMC's nomination of Simon Weller as the next PMC Chair / VP of
> > the Apache CloudStack project.
> >
> > I would like to thank everyone for the support I've received over the
> past year.
> > It was a great honor being the PMC Chair of this amazing
> project/community!
> >
> > To Simon, my sincere congratulations, and I wish you success in the new
> role!
> > Very well deserved!
> >
> > Please join me in congratulating Simon, the CloudStack PMC Chair / VP.
> >
> > Best Regards,
> > Gabriel Bräscher.
>

Re: [!!Mass Mail]Re: Build CS from Sources

[Slavka Peleva]

This means that the class is compiled with a higher version of java than
the version with which you try to run it (compiled with 11 and try to run
it now with 8). You need to set the `JAVA_HOME` environment variable with
the correct version of java (needed for the project - if I remember
correct from 4.14 it is java 11 before that java 8) and rerun the build.

Best regards,
Slavka

On Mon, Mar 14, 2022 at 2:17 PM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Thx, Slavka!
>
> But when I try command `mvn clean install -DskipTests` in tools directory
> now I have new error:
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile) @ cloud-apidoc ---
> Error: A JNI error has occurred, please check your installation and try
> again
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> com/cloud/api/doc/ApiXmlDocWriter has been compiled by a more recent
> version of the Java Runtime (class file version 55.0), this version of the
> Java Runtime only recognizes class file versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601)
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache CloudStack Developer Tools . SUCCESS [1.058s]
> [INFO] Apache CloudStack apidocs . FAILURE [4.473s]
> [INFO] Apache CloudStack marvin .. SKIPPED
> [INFO] Apache CloudStack DevCloud4 ... SKIPPED
> [INFO] Apache CloudStack DevCloud-KVM  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 5.715s
> [INFO] Finished at: Mon Mar 14 15:14:59 MSK 2022
> [INFO] Final Memory: 36M/154M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project
> cloud-apidoc: Command execution failed. Process exited with an error: 1
> (Exit value: 1) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :cloud-apidoc
>
>
>
>
>
> -Original Message-
> From: Slavka Peleva [mailto:slav...@storpool.com.INVALID]
> Sent: Monday, March 14, 2022 1:53 PM
> To: users@cloudstack.apache.org
> Subject: [!!Mass Mail]Re: Build CS from Sources
>
> Hi Evgeniy,
>
> I don't tell that this solution is perfect, but I had this problem once
> and those steps helped me to solve it:
> - In the main CS directory, execute - `mvn clean install -DskipTests`
> (this will download all required dependencies and build the CS modules
> locally. I use the option `-DskipTests` because in this case, you don't
> want to run all tests )
> - when the build finishes you should go to the `tools` directory and
> execute the same command `mvn clean install -DskipTests` it could fail like
> this:
>
> [INFO] Apache CloudStack Developer Tools .. SUCCESS [
>  0.781 s]
> [INFO] Apache CloudStack apidocs .. SUCCESS [
> 10.257 s]
> [INFO] Apache CloudStack marvin ... SUCCESS [
>  3.650 s]
> [INFO] Apache CloudStack DevCloud4  FAILURE [
>  0.059 s]
> [INFO] Apache CloudSta

Re: Build CS from Sources

[Slavka Peleva]

Hi Evgeniy,

I don't tell that this solution is perfect, but I had this problem once and
those steps helped me to solve it:
- In the main CS directory, execute - `mvn clean install -DskipTests` (this
will download all required dependencies and build the CS modules locally. I
use the option `-DskipTests` because in this case, you don't want to run
all tests )
- when the build finishes you should go to the `tools` directory and
execute the same command `mvn clean install -DskipTests`
it could fail like this:

[INFO] Apache CloudStack Developer Tools .. SUCCESS [
 0.781 s]
[INFO] Apache CloudStack apidocs .. SUCCESS [
10.257 s]
[INFO] Apache CloudStack marvin ... SUCCESS [
 3.650 s]
[INFO] Apache CloudStack DevCloud4  FAILURE [
 0.059 s]
[INFO] Apache CloudStack DevCloud-KVM . SKIPPED

But you can proceed after that with packaging.

Best regards,
Slavka


On Mon, Mar 14, 2022 at 11:12 AM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> Does somebody try to build CS from sources?
> Try It with official documentation and on one step I get ERROR:
>
> Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (compile) on project cloud-apidoc: Command execution failed. Process exited
> with an error: 1 (Exit value: 1) -> [Help 1]
>
> I try to build rmps for el8.
>
>
>
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> 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: Multiple primary storage issue

[Slavka Peleva]

Hi Irvin,

You have to add the same storage tags of your primary storage to the
compute offering that you're using while deploying a VM. If this does not
work, can you share more information about the two primary storage
(Zone-wide or Cluster-wide), their tags and the compute offering tags?

Best regards,
Slavka

On Wed, Mar 2, 2022 at 8:17 AM jcapagcuan .  wrote:

> Hi Antoine,
>
> Yes, I’m using tags whenever i add data disk and that works fine. My issue
> is for the root disk when I launch from a template, that’s when it
> randomizes where to put the root disk to the 2 primary storage.
>
> Thanks,
> Irvin
>
> > On Mar 2, 2022, at 10:05 AM, Antoine Boucher 
> wrote:
> >
> > Use tags on storage and on templates, compute offering or instance
> creation.
> >
> > Antoine Boucher
> > antoi...@haltondc.com
> >
> >
> > Confidentiality Warning: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential, and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, retransmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return e-mail, and delete this message and any attachments
> from your system.
> >
> > On Mar 1, 2022, at 19:02, jcapagcuan .  wrote:
> >
> > Hi,
> >
> > I have created 2 primary storage for my Cloudstack (4.16.0). Whenever I
> launch an instance from a template, it randomizes from the 2 primary
> storage on where it will put the root disk. Is there a way to restrict the
> root disk to a specific storage?
> >
> > Thanks,
> > Irvin
> >
>
>

Re: KVM VM options

[Slavka Peleva]

Hi Jonathan,

You can change this option from the UI when you stop the VM, and in its
settings tab, you can add `video.hardware` with the required value.

Best regards,
Slavka

On Fri, Jan 7, 2022 at 12:41 PM Jonathan McLoughlin <
jonathan.mclough...@gmail.com> wrote:

> I have deployed a single host cloudstack environment for lab purposes using
> KVM as a hypervisor, its been working great for testing.
>
> I am trying to update the qemu-kvm boot options for a Fedora desktop VM,
> specifically, I want to pass "-vga std" or "-vga qxl" to increase the
> default resolution on this desktop VM.
>
> All VM's currently booting with "-vga cirrus" which limits the emulated
> graphic resolution
>
> Tried some config options, reviewed the docs and tried googling but no
> luck.
>
> I am aware of vGPU options when using xen hypervisor but unfortunately I am
> using a vanilla centos7 qemu-kvm hypervisor.
>
> Using NoMachine client to connect to the Fedora desktop VM.
>

Re: upgrade host to AlmaLinux

[Slavka Peleva]

Hello Piotr,

Maybe Andrija's answer on this thread could help you -
https://www.mail-archive.com/users@cloudstack.apache.org/msg32326.html

Best regards,
Slavka

On Fri, Dec 31, 2021 at 12:32 PM Piotr Pisz  wrote:

> Hello Users!
>
> I have a small problem, I did a test migration from CentOS 8 to AlmaLinux
> (without any problem), but Cloudstack refuses to reconnect the host with
> the message:
>
> java.lang.IllegalArgumentException: Can't add host: 192.168.10.42 with
> hostOS: AlmaLinux into a cluster,in which there are CentOS hosts added
>
> I removed this host from CS but when connecting it again I get the message
> as above.
>
> Maybe it would be a good idea if CS detects the host re-addition and
> prompts you to add it again (instead of rejecting it automatically)?
>
> Regards,
> Piotr
>
>
>
>

Re: UEFI on KVM silently becomes BIOS mode

[Slavka Peleva]

Hi Pieter,

This is a known issue in 4.16 with the missing loader tag in the XML
definition. There is a fix that will get in the 4.16.1.0 release -
https://github.com/apache/cloudstack/pull/5692

Best regards,
Slavka


On Sat, Dec 18, 2021 at 3:15 PM Piotr Pisz  wrote:

> Hi Pieter,
>
>
>
> I run it in CentOS 8:
>
>
>
> Cloudstack:
>
>
>
> i-4-46-VM
>
> e9c33f2d-7237-4cc1-b466-5d85a04ed549
>
> Other PV Virtio-SCSI (64-bit)
>
>  policy='require' name='vmx'/> policy='require' name='smx'/>
>
> 
>
> Apache Software Foundation
>
> CloudStack KVM Hypervisor
>
> e9c33f2d-7237-4cc1-b466-5d85a04ed549
>
> 
>
> 
>
> 
>
> hvm
>
>  template='/usr/share/edk2/ovmf/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/e9c33f2d-7237-4cc1-b466-5d85a04ed549.fd dev='cdrom'/>
>
> 
>
> 
>
> 
>
>
>
> Virsh dump:
>
>
>
>   
>
>
>
>   Apache Software Foundation
>
>   CloudStack KVM Hypervisor
>
>   e9c33f2d-7237-4cc1-b466-5d85a04ed549
>
> 
>
>   
>
>   
>
> hvm
>
> 
>
> 
>
> 
>
>   
>
>
>
> Regards,
>
> Piotr
>
>
>
>
>
> From: Pieter Harvey 
> Sent: Friday, December 17, 2021 5:46 PM
> To: Pieter Harvey 
> Cc: "users@cloudstack.apache.org" 
> Subject: Re: UEFI on KVM silently becomes BIOS mode
>
>
>
> Hi Piotr,
>
>
>
> Is there any way to get this debug info (or xml dump) from CloudStack,
> what it is creating versus what ends up in virsh?
>
>
>
> I think I have configured everything correctly
>
> 1. cloudstack uefi enabled in database for host (host.uefi.enable)
>
> 2. host agent has uefi.properties with all paths configured (snippet below
> based Ubuntu 20.04.3)
>
> 3. instance is configured for UEFI (tried both legacy and secure boot)
>
>
>
> uefi.properties
>
> ==
>
> guest.nvram.template.secure=/usr/share/OVMF/OVMF_VARS.fd
>
> guest.nvram.template.legacy=/usr/share/OVMF/OVMF_VARS.fd
>
> guest.loader.secure=/usr/share/OVMF/OVMF_CODE.secboot.fd
>
> guest.loader.legacy=/usr/share/OVMF/OVMF_CODE.fd
>
> guest.nvram.path=/var/lib/libvirt/qemu/nvram/
>
>
>
> sudo ls -lh /usr/share/OVMF/
>
> 
>
> -rw-r--r-- 1 root root 1.9M Sep 20 13:11 OVMF_CODE.fd
>
> lrwxrwxrwx 1 root root   20 Sep 20 13:11 OVMF_CODE.ms.fd ->
> OVMF_CODE.secboot.fd
>
> -rw-r--r-- 1 root root 1.9M Sep 20 13:11 OVMF_CODE.secboot.fd
>
> -rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.fd
>
> -rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.ms.fd
>
> -rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.snakeoil.fd
>
>
>
> syslog
>
> =
>
> java[47841]: INFO  [kvm.resource.LibvirtComputingResource] (main:)
> (logid:) uefi.properties file found at
> /etc/cloudstack/agent/uefi.properties
>
> java[47841]: INFO  [kvm.resource.LibvirtComputingResource] (main:)
> (logid:) guest.nvram.template.legacy = /usr/share/OVMF/OVMF_VARS.fd
>
> java[47841]: INFO  [kvm.resource.LibvirtComputingResource] (main:)
> (logid:) guest.loader.legacy = /usr/share/OVMF/OVMF_CODE.fd
>
> java[47841]: INFO  [kvm.resource.LibvirtComputingResource] (main:)
> (logid:) guest.nvram.template.secure = /usr/share/OVMF/OVMF_VARS.fd
>
> java[47841]: INFO  [kvm.resource.LibvirtComputingResource] (main:)
> (logid:) guest.loader.secure =/usr/share/OVMF/OVMF_CODE.secboot.fd
>
> java[47841]: INFO  [kvm.resource.LibvirtComputingResource] (main:)
> (logid:) guest.nvram.path = /var/lib/libvirt/qemu/nvram/
>
>
>
>
>
> -
>
> Pieter
>
>
>
> On 17 Dec 2021, at 16:15, Piotr Pisz  pi...@piszki.pl> > wrote:
>
>
>
>
>
> Hi Pieter,
>
>
>
>
>
>
>
> I have just checked, everything works as expected, maybe you have
> something wrongly configured, check according to this:
>
>
>
>
>
>
>
> https://lab.piszki.pl/cloudstack-vm-with-vtpm-and-secure-boot-uefi/
>
>
>
>
>
>
>
> Regards,
>
>
>
> Piotr
>
>
>
>
>
>
>
>
>
>
>
> From: Pieter Harvey  pieter.har...@icloud.com.INVALID> >
>
> Sent: Friday, December 17, 2021 4:11 PM
>
> To: "users@cloudstack.apache.org  " <
> users@cloudstack.apache.org  >
>
> Subject: UEFI on KVM silently becomes BIOS mode
>
>
>
>
>
>
>
> Hello,
>
>
>
>
>
>
>
> Maybe it's something wrong with CloudStack, maybe it's my brain but I have
> an issue regarding UEFI on CloudStack (4.16) + KVM (Ubuntu 20.04)
>
>
>
>
>
>
>
> 1. CloudStack Compute node is running, and can boot machines configured as
> UEFI in the GUI (secure or legacy).
>
>
>
>
>
>
>
> 2. When the machine is booted, I check the virsh xml config on the host
> and noticed that the machine is still in BIOS mode, even though CloudStack
> "thinks" it has deployed a fresh UEFI enabled instance.
>
>
>
>
>
>
>
> I have configured uefi.properties on the agent and the host is UEFI
> enabled in CloudStack but this is the config snippet of a deployed machine
>
>
>
>
>
>
>
> 
>
>
>
> hvm
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
>
>
>
>
> However what I am expecting to see is:
>
>
>
>
>
>
>
> 
>
>
>
> hvm
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
>
>
>
>
> So CloudStack has changed the 

Re: Issues with libvirt after upgrading to RockyLinux 8.5

[Slavka Peleva]

Sorry, I didn't pay attention to your CS version. After the upgrade, I
think you will have the same problem. Because in the DB, there is
information about host/hosts on this cluster that is/are with CentOS.

Best regards,
Slavka

On Thu, Dec 16, 2021 at 8:49 AM Jeremy Hansen 
wrote:

> I noticed in the compatibility matrix that Rocky isn’t supported until
> 4.16.0.0.  If I upgrade Cloudstack first, would this help or is it still
> going to complain about the centos/rocky mix?  If I convert all my existing
> nodes to Rocky, which is the plan anyway, will this go away?  Shouldn’t
> CentOS and Rocky be considered that same thing… sort of…?
>
> Thanks
> -jeremy
>
>
>
>
> On Wednesday, Dec 15, 2021 at 10:43 PM, Slavka Peleva <
> slav...@storpool.com.INVALID> wrote:
> Hi Jeremy,
>
> It will help if you have another cluster for Rocky Linux. Hosts need to be
> of the same OS, it's not possible to mix OSes in the same cluster.
>
> Best regards,
> Slavka
>
> On Thu, Dec 16, 2021 at 4:08 AM Jeremy Hansen 
> wrote:
>
> Any tips on how I would troubleshoot this? I’ve tried downgrading libvirt
> and qemu and ca-certificates to the same version as the other functional
> nodes. That didn’t seem to help. This is obviously an ssl issue but I
> don’t really know what to do about it.
>
> 2021-12-15 18:04:14,438 INFO [cloud.agent.AgentShell] (main:null)
> (logid:) Agent started
> 2021-12-15 18:04:14,444 INFO [cloud.agent.AgentShell] (main:null)
> (logid:) Implementation Version is 4.15.0.0
> 2021-12-15 18:04:14,447 INFO [cloud.agent.AgentShell] (main:null)
> (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
> 2021-12-15 18:04:14,466 INFO [cloud.agent.AgentShell] (main:null)
> (logid:) Defaulting to using properties file for storage
> 2021-12-15 18:04:14,467 INFO [cloud.agent.AgentShell] (main:null)
> (logid:) Defaulting to the constant time backoff algorithm
> 2021-12-15 18:04:14,471 INFO [cloud.utils.LogUtils] (main:null) (logid:)
> log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
> 2021-12-15 18:04:14,485 INFO [cloud.agent.AgentShell] (main:null)
> (logid:) Using default Java settings for IPv6 preference for agent
> connection
> 2021-12-15 18:04:14,592 INFO [cloud.agent.Agent] (main:null) (logid:) id
> is 0
> 2021-12-15 18:04:14,606 ERROR [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) uefi properties file not found due to: Unable to find
> file uefi.properties.
> 2021-12-15 18:04:14,663 INFO [kvm.resource.LibvirtConnection] (main:null)
> (logid:) No existing libvirtd connection found. Opening a new one
> 2021-12-15 18:04:14,890 INFO [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) No libvirt.vif.driver specified. Defaults to
> BridgeVifDriver.
> 2021-12-15 18:04:15,086 INFO [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) iscsi session clean up is disabled
> 2021-12-15 18:04:15,129 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-15 18:04:15,139 INFO [utils.nio.NioClient] (main:null) (logid:)
> Connecting to 192.168.30.59:8250
> 2021-12-15 18:04:15,153 INFO [utils.nio.Link] (main:null) (logid:) Conf
> file found: /etc/cloudstack/agent/agent.properties
> 2021-12-15 18:04:15,919 INFO [utils.nio.NioClient] (main:null) (logid:)
> SSL: Handshake done
> 2021-12-15 18:04:15,920 INFO [utils.nio.NioClient] (main:null) (logid:)
> Connected to 192.168.30.59:8250
> 2021-12-15 18:04:16,057 INFO [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Attempting to create storage pool
> 18796842-a137-475d-9799-9874240e3c0c (Filesystem) in libvirt
> 2021-12-15 18:04:16,062 ERROR [kvm.resource.LibvirtConnection]
> (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken:
> invalid
> connection pointer in virConnectGetVersion
> 2021-12-15 18:04:16,066 INFO [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Found existing defined storage pool
> 18796842-a137-475d-9799-9874240e3c0c, using it.
> 2021-12-15 18:04:16,066 INFO [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Trying to fetch storage pool
> 18796842-a137-475d-9799-9874240e3c0c from libvirt
> 2021-12-15 18:04:16,151 INFO [cloud.serializer.GsonHelper]
> (Agent-Handler-1:null) (logid:) Default Builder inited.
> 2021-12-15 18:04:16,272 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Proccess agent startup answer, agent id = 0
> 2021-12-15 18:04:16,273 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Set agent id 0
> 2021-12-15 18:04:16,289 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Startup Resp

Re: Issues with libvirt after upgrading to RockyLinux 8.5

[Slavka Peleva]

Hi Jeremy,

It will help if you have another cluster for Rocky Linux. Hosts need to be
of the same OS, it's not possible to mix OSes in the same cluster.

Best regards,
Slavka

On Thu, Dec 16, 2021 at 4:08 AM Jeremy Hansen 
wrote:

> Any tips on how I would troubleshoot this?  I’ve tried downgrading libvirt
> and qemu and ca-certificates to the same version as the other functional
> nodes.  That didn’t seem to help.  This is obviously an ssl issue but I
> don’t really know what to do about it.
>
> 2021-12-15 18:04:14,438 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Agent started
> 2021-12-15 18:04:14,444 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Implementation Version is 4.15.0.0
> 2021-12-15 18:04:14,447 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties
> 2021-12-15 18:04:14,466 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Defaulting to using properties file for storage
> 2021-12-15 18:04:14,467 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Defaulting to the constant time backoff algorithm
> 2021-12-15 18:04:14,471 INFO  [cloud.utils.LogUtils] (main:null) (logid:)
> log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
> 2021-12-15 18:04:14,485 INFO  [cloud.agent.AgentShell] (main:null)
> (logid:) Using default Java settings for IPv6 preference for agent
> connection
> 2021-12-15 18:04:14,592 INFO  [cloud.agent.Agent] (main:null) (logid:) id
> is 0
> 2021-12-15 18:04:14,606 ERROR [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) uefi properties file not found due to: Unable to find
> file uefi.properties.
> 2021-12-15 18:04:14,663 INFO  [kvm.resource.LibvirtConnection] (main:null)
> (logid:) No existing libvirtd connection found. Opening a new one
> 2021-12-15 18:04:14,890 INFO  [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) No libvirt.vif.driver specified. Defaults to
> BridgeVifDriver.
> 2021-12-15 18:04:15,086 INFO  [kvm.resource.LibvirtComputingResource]
> (main:null) (logid:) iscsi session clean up is disabled
> 2021-12-15 18:04:15,129 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-15 18:04:15,139 INFO  [utils.nio.NioClient] (main:null) (logid:)
> Connecting to 192.168.30.59:8250
> 2021-12-15 18:04:15,153 INFO  [utils.nio.Link] (main:null) (logid:) Conf
> file found: /etc/cloudstack/agent/agent.properties
> 2021-12-15 18:04:15,919 INFO  [utils.nio.NioClient] (main:null) (logid:)
> SSL: Handshake done
> 2021-12-15 18:04:15,920 INFO  [utils.nio.NioClient] (main:null) (logid:)
> Connected to 192.168.30.59:8250
> 2021-12-15 18:04:16,057 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Attempting to create storage pool
> 18796842-a137-475d-9799-9874240e3c0c (Filesystem) in libvirt
> 2021-12-15 18:04:16,062 ERROR [kvm.resource.LibvirtConnection]
> (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: invalid
> connection pointer in virConnectGetVersion
> 2021-12-15 18:04:16,066 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Found existing defined storage pool
> 18796842-a137-475d-9799-9874240e3c0c, using it.
> 2021-12-15 18:04:16,066 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (Agent-Handler-1:null) (logid:) Trying to fetch storage pool
> 18796842-a137-475d-9799-9874240e3c0c from libvirt
> 2021-12-15 18:04:16,151 INFO  [cloud.serializer.GsonHelper]
> (Agent-Handler-1:null) (logid:) Default Builder inited.
> 2021-12-15 18:04:16,272 INFO  [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Proccess agent startup answer, agent id = 0
> 2021-12-15 18:04:16,273 INFO  [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Set agent id 0
> 2021-12-15 18:04:16,289 INFO  [cloud.agent.Agent] (Agent-Handler-2:null)
> (logid:) Startup Response Received: agent id = 0
> 2021-12-15 18:04:16,289 INFO  [cloud.agent.Agent]
> (AgentShutdownThread:null) (logid:) Stopping the agent: Reason = sig.kill
>
> I also noticed this:
>
> 2021-12-15 18:05:34,542 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentConnectTaskPool-19617:ctx-e0dfdb18) (logid:d3930423) Failed to handle
> host connection:
> java.lang.IllegalArgumentException: Can't add host: 192.168.30.54 with
> hostOS: Rocky into a cluster,in which there are CentOS hosts added
> at
> com.cloud.hypervisor.kvm.discoverer.LibvirtServerDiscoverer.createHostVOForConnectedAgent(LibvirtServerDiscoverer.java:456)
> at
> com.cloud.resource.ResourceManagerImpl.dispatchToStateAdapters(ResourceManagerImpl.java:1719)
> at
> com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1946)
> at
> com.cloud.resource.ResourceManagerImpl.createHostVOForConnectedAgent(ResourceManagerImpl.java:2278)
> at jdk.internal.reflect.GeneratedMethodAccessor510.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl

Re: Zone not ready to launch system VMs though they are already running...

[Slavka Peleva]

Hi Peter,

The error from your usage.log says that the `db.cloud.maxActive` from your
`db.properties` file is empty, and you have to provide a value for it.
Also, if those properties are empty too - `db.cloud.maxIdle` and
`db.cloud.maxWait` - the init of DB will fail again.

Best regards,
Slavka






On Wed, Dec 1, 2021 at 9:55 AM Peter Stine
 wrote:

> Wei,
>
> That got the Zone to recognize as up and ready.
> To the database point, in the usage log, I now see that is is failing to
> load the db configuration. As I am not using default logins, this means it
> won't correctly connect to the database. I am not sure what is stopping
> cloudstack from loading the database configuration.
>
> Here is the warning:
> 2021-11-30 18:09:34,747 WARN  [db.Transaction.Transaction] (main:null)
> (logid:) Unable to load db configuration, using defaults with 5
> connections. Falling back on assumed datasource on localhost:3306 using
> username:password=cloud:cloud. Please check your configuration
> java.lang.NumberFormatException: null
> at java.base/java.lang.Integer.parseInt(Integer.java:614)
> at java.base/java.lang.Integer.parseInt(Integer.java:770)
> at
> com.cloud.utils.db.TransactionLegacy.initDataSource(TransactionLegacy.java:1030)
> at
> com.cloud.utils.db.TransactionLegacy.(TransactionLegacy.java:1008)
> at
> com.cloud.utils.db.TransactionContextBuilder.interceptStart(TransactionContextBuilder.java:49)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:116)
> at
> com.cloud.usage.dao.UsagePortForwardingRuleDaoImpl_EnhancerByCloudStack_56282efc.createPartialSelectSql()
> at com.cloud.utils.db.GenericDaoBase.(GenericDaoBase.java:238)
> at
> com.cloud.usage.dao.UsagePortForwardingRuleDaoImpl.(UsagePortForwardingRuleDaoImpl.java:50)
> at
> com.cloud.usage.dao.UsagePortForwardingRuleDaoImpl_EnhancerByCloudStack_56282efc.()
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:291)
> at
> net.sf.cglib.proxy.Enhancer$EnhancerFactoryData.newInstance(Enhancer.java:448)
> at net.sf.cglib.proxy.Enhancer.nextInstance(Enhancer.java:700)
> at
> net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:298)
> at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:480)
> at net.sf.cglib.proxy.Enhancer.create(Enhancer.java:305)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor.postProcessBeforeInstantiation(ComponentInstantiationPostProcessor.java:92)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInstantiation(AbstractAutowireCapableBeanFactory.java:1144)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveBeforeInstantiation(AbstractAutowireCapableBeanFactory.java:1119)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:944)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:923)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:588)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:144)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:85)
> at com.cloud.usage.UsageServer.start(UsageServer.java:52)
> at com.cloud.usage.UsageServer.main(UsageServer.java:41)
>
> 
> From: "Wei ZHOU" 
> Sent: 11/30/21 1:00 PM
> To: users , peter.st...@granddial.com
> Subject: Re: Zone not ready to launch system VMs though they are already
> running...
>
> Hi Peter,
>
> This seems to be caused by database connection problems. Try to restart
> cloudstack management service, and also mariadb if it still doesn't work.

Re: [!!Mass Mail]io uring is not supported by this QEMU binary

[Slavka Peleva]

Hi all,

I tried to deploy a VM on Ubuntu 20.04, and I had the same issue:

error: unsupported configuration: io uring is not supported by this QEMU binary

kernel version - 5.4.0-90-generic
Libvirt/qemu :

Compiled against library: libvirt 7.6.0
Using library: libvirt 7.6.0
Using API: QEMU 7.6.0
Running hypervisor: QEMU 6.0.0

grep io_uring_setup /proc/kallsyms
 t io_uring_setup
 T __x64_sys_io_uring_setup
 T __ia32_sys_io_uring_setup
 d event_exit__io_uring_setup
 d event_enter__io_uring_setup
 d __syscall_meta__io_uring_setup
 d args__io_uring_setup
 d types__io_uring_setup
 t __event_exit__io_uring_setup
 t __event_enter__io_uring_setup
 t __p_syscall_meta__io_uring_setup
 t _eil_addr___ia32_sys_io_uring_setup
 t _eil_addr___x64_sys_io_uring_setup
grep -i uring /boot/config-$(uname -r)
CONFIG_IO_URING=y


With Ubuntu 21.04 with versions of:

kernel - 5.11.0-40-generic
libvirt/qemu -

Compiled against library: libvirt 7.6.0
Using library: libvirt 7.6.0
Using API: QEMU 7.6.0
Running hypervisor: QEMU 5.2.0

and Ubuntu 21.10 with versions of:

kernel - 5.13.0-21-generic
qemu/libvirt -
  Compiled against library: libvirt 7.6.0
  Using library: libvirt 7.6.0
  Using API: QEMU 7.6.0
  Running hypervisor: QEMU 6.0.0

I didn't have a problem deploying a VM with io_uring

Best regards,
Slavka


On Wed, Nov 24, 2021 at 10:11 PM Mauro Ferraro - G2K Hosting <
mferr...@g2khosting.com> wrote:

> Hi,
>
> We were try to deploy io_uring, but is supported since kernel 5.1 and
> CentOS 8 has Kernel 4.8.
>
> There is a backport request at redhat but is still in progress since april.
>
> https://access.redhat.com/solutions/4723221
>
> I tnink redhat will include this when the updates the kernel version.
>
> We think the best solution for this is to support Ubuntu 21.10 at
> cloudstack Host, because it meets all the requirements to work with
> io_uring,
>
> Ubuntu 21.10
>
> Qemu version 6 (io_uring supported since Qemu 5)
> Libvirt  7.6 (io_uring supported since Libvirt 7)
>
> Kernel 5.13 (io_uring supported with last performance enhancements)
>
> What do you think?
>
> Regards,
>
>
> El 24/11/2021 a las 07:00, Piotr Pisz escribió:
> > Hi,
> >
> >
> >
> > Thank you Gabriel for the explanations, being able to set up IO_Driver
> via agent.properties is a good direction.
> >
> > I will try to check why it is not supported in CentOS8 SIG
> Virtualization.
> >
> >
> >
> > Regards,
> >
> > Piotr
> >
> >
> >
> >
> >
> > From: Gabriel Bräscher 
> > Sent: Wednesday, November 24, 2021 10:02 AM
> > To: pi...@piszki.pl
> > Cc: users ; Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by>
> > Subject: Re: [!!Mass Mail]io uring is not supported by this QEMU binary
> >
> >
> >
> > Hi Piotr,
> >
> > Unfortunately, the current implementation does not allow to customize
> the driver via the agent.properties.
> > Instead, it evaluates Libvirt and Qemu versions in order to assess if it
> is supported.
> >
> > I considered the libvirt & qemu documentation where address support for
> io_uring  and release notes.
> >
> > According to release notes, io_urin is supported in:
> >  Qemu >= 5.0 [1], and
> >  Libvirt >= 6.3.0 [2].
> > (for reference) The kernel feature (io_uring itself) is described in
> this lwn.net   article [3].
> >
> > However, I am not confident (anymore) that RedHat is supporting it [4,5].
> > It also might be that there has been a regression in the newer Qemu
> release.
> >
> > For the record, I've just re-checked a KVM host running 4.16.0.0 and I
> have indeed VMs running with io_uring configured in the "domain.xml".
> > Host details: Ubuntu 20.04, Qemu 5.0.0, Libvirt 6.3.0.
> >
> >
> >
> > As a conclusion, considering that it is not as stable and widely
> supported as assumed before, I will propose a PR that would allow
> customizing the disk IO_Driver in the "agent.properties".
> >
> > Additionally, I will double-check documentation, release announcements,
> and bugs raised in qemu, libvirt, redhat, & ubuntu scopes.
> >
> > [1] https://wiki.qemu.org/ChangeLog/5.0
> > [2] https://libvirt.org/news.html#v6-3-0-2020-05-05
> > [3] https://lwn.net/Articles/776703/
> > [4] https://bugzilla.redhat.com/show_bug.cgi?id=1769597
> > [5] https://bugzilla.redhat.com/show_bug.cgi?id=1769598
> >
> > Any feedback and tests with different OS and Libvurt/Qemu releases are
> very appreciated.
> >
> > Best Regards,
> >
> > Gabriel.
> >
> >
> >
> > Em qua., 24 de nov. de 2021 às 09:37, Piotr Pisz   > escreveu:
> >
> > Hi!
> >
> >
> >
> > Gabriel, could you suggest how to disable io_uring with agent.properties?
> >
> > In the second lab, I turned off advanced virtualization repo and
> downgrade qemu to native for CentOS 8 and everything works fine.
> >
> > Generally, I use a lot of nested 

Re: Dynamic VM Scaling KVM

[Slavka Peleva]

I just forgot to mention that the working VM was deployed first with
qemu-kvm-ev (before switching to qemu-kvm for the tests), and the domain
XML had  tag.
We had an offline conversation with Daniel, and we found that the memory
hotplug is included in qemu version 2.1.

Regards,
Slavka

On Fri, Nov 19, 2021 at 12:42 PM Slavka Peleva  wrote:

> Hi all,
>
> I've tested the dynamic scaling with qemu-kvm and qemu-kvm-ev. Here are
> the results for both with "Custom constrained" compute offering:
>
> qemu-kvm-ev
> deploy VM - passed
> scale VM - passed
>
> qemu-kvm
> deploy VM - failed with the same error (org.libvirt.LibvirtException:
> internal error: process exited while connecting to monitor: qemu: invalid
> ram size: size=524288k,slots=16,maxmem=4194304k)
> scale VM on existing VM - passed
>
> Best regards,
> Slavka
>
> On Fri, Nov 19, 2021 at 6:12 AM Abishek  wrote:
>
>> Thanks a lot Wei for helping out. I will first try it in the Ubuntu
>> environment.
>>
>> On Fri, 19 Nov 2021 at 00:09, Wei ZHOU  wrote:
>>
>> > Great, thanks Daniel.
>> >
>> > Abishek, now it seems you need to install qemu-kvm-ev for testing the
>> > feature.
>> >
>> > -Wei
>> >
>> > On Thursday, 18 November 2021, Daniel Augusto Veronezi Salvador <
>> > dvsalvador...@gmail.com> wrote:
>> >
>> > > Hi Abishek, Wei, I tested this feature with Ubuntu 20.04 + KVM. Some
>> > > community members tested with CentOS7 and qemu-kvm-ev and it worked.
>> > Also,
>> > > as live snapshots and live migrations, hotplug memory is a known
>> > limitation
>> > > of qemu-kvm. I cannot give you advice regarding this replacement too,
>> as
>> > I
>> > > do not use CentOS. Best regards, Daniel Salvador
>> > >
>> > > On 17/11/2021 09:07, Wei ZHOU wrote:
>> > >
>> > >> Hi Abishek,
>> > >>
>> > >> I cannot give your advice on it as I did not install qemu-kvm-ev to
>> > >> replace
>> > >> qemu-kvm before.
>> > >>
>> > >> I suspect that the issue you faced is caused by qemu-kvm. qemu-kvm-ev
>> > >> supports more advanced features than qemu-kvm.
>> > >>
>> > >> cc @Daniel, what hypervisor did you use to test the dynamic scaling ?
>> > >>
>> > >> -Wei
>> > >>
>> > >> On Wed, 17 Nov 2021 at 11:42, Abishek  wrote:
>> > >>
>> > >> HI Wei,
>> > >>>
>> > >>> I have not tested with qemu-kvm-ev. I am willing to try but what
>> > >>> effect will it have on my existing setup when I install qemu-kvm-ev
>> in
>> > my
>> > >>> existing qemu-kvm. Should I have to remove qemu-kvm and install
>> > >>> qemu-kvm-ev? In the previous test I was able to start the machine
>> with
>> > >>> Fixed Offering but the option for Scaling the VM in UI was not
>> present
>> > >>> while the VM was in running state but was available when the VM was
>> in
>> > >>> shutdown state only.
>> > >>>
>> > >>> Thank You.
>> > >>>
>> > >>> On Wed, 17 Nov 2021 at 15:23, Wei ZHOU
>> wrote:
>> > >>>
>> > >>> Hi Abishek,
>> > >>>>
>> > >>>> Have you tested with qemu-kvm-ev instead of qemu-kvm ?
>> > >>>>
>> > >>>> -Wei
>> > >>>>
>> > >>>> On Wed, 17 Nov 2021 at 10:00, Abishek  wrote:
>> > >>>>
>> > >>>> Hello Wei,
>> > >>>>>
>> > >>>>> I am very grateful for your response. In my test environment I
>> first
>> > >>>>> created a service offering of Custom Constrained (minCore=1,
>> > >>>>>
>> > >>>> maxCore=10,
>> > >>>
>> > >>>> minRam=1GB, maxRam=12GB, CPUSpeed=2000) with dynamic scaling
>> enabled.
>> > >>>>>
>> > >>>> But
>> > >>>
>> > >>>> every time I tried to start the VM under this ServiceOffering I got
>> > the
>> > >>>>> above mentioned error. Please find the following agent log for
>> that
>> > >>>>> particular VM:
>> > >>>>>
>> > >>>&g

Re: Dynamic VM Scaling KVM

[Slavka Peleva]

Hi all,

I've tested the dynamic scaling with qemu-kvm and qemu-kvm-ev. Here are the
results for both with "Custom constrained" compute offering:

qemu-kvm-ev
deploy VM - passed
scale VM - passed

qemu-kvm
deploy VM - failed with the same error (org.libvirt.LibvirtException:
internal error: process exited while connecting to monitor: qemu: invalid
ram size: size=524288k,slots=16,maxmem=4194304k)
scale VM on existing VM - passed

Best regards,
Slavka

On Fri, Nov 19, 2021 at 6:12 AM Abishek  wrote:

> Thanks a lot Wei for helping out. I will first try it in the Ubuntu
> environment.
>
> On Fri, 19 Nov 2021 at 00:09, Wei ZHOU  wrote:
>
> > Great, thanks Daniel.
> >
> > Abishek, now it seems you need to install qemu-kvm-ev for testing the
> > feature.
> >
> > -Wei
> >
> > On Thursday, 18 November 2021, Daniel Augusto Veronezi Salvador <
> > dvsalvador...@gmail.com> wrote:
> >
> > > Hi Abishek, Wei, I tested this feature with Ubuntu 20.04 + KVM. Some
> > > community members tested with CentOS7 and qemu-kvm-ev and it worked.
> > Also,
> > > as live snapshots and live migrations, hotplug memory is a known
> > limitation
> > > of qemu-kvm. I cannot give you advice regarding this replacement too,
> as
> > I
> > > do not use CentOS. Best regards, Daniel Salvador
> > >
> > > On 17/11/2021 09:07, Wei ZHOU wrote:
> > >
> > >> Hi Abishek,
> > >>
> > >> I cannot give your advice on it as I did not install qemu-kvm-ev to
> > >> replace
> > >> qemu-kvm before.
> > >>
> > >> I suspect that the issue you faced is caused by qemu-kvm. qemu-kvm-ev
> > >> supports more advanced features than qemu-kvm.
> > >>
> > >> cc @Daniel, what hypervisor did you use to test the dynamic scaling ?
> > >>
> > >> -Wei
> > >>
> > >> On Wed, 17 Nov 2021 at 11:42, Abishek  wrote:
> > >>
> > >> HI Wei,
> > >>>
> > >>> I have not tested with qemu-kvm-ev. I am willing to try but what
> > >>> effect will it have on my existing setup when I install qemu-kvm-ev
> in
> > my
> > >>> existing qemu-kvm. Should I have to remove qemu-kvm and install
> > >>> qemu-kvm-ev? In the previous test I was able to start the machine
> with
> > >>> Fixed Offering but the option for Scaling the VM in UI was not
> present
> > >>> while the VM was in running state but was available when the VM was
> in
> > >>> shutdown state only.
> > >>>
> > >>> Thank You.
> > >>>
> > >>> On Wed, 17 Nov 2021 at 15:23, Wei ZHOU
> wrote:
> > >>>
> > >>> Hi Abishek,
> > 
> >  Have you tested with qemu-kvm-ev instead of qemu-kvm ?
> > 
> >  -Wei
> > 
> >  On Wed, 17 Nov 2021 at 10:00, Abishek  wrote:
> > 
> >  Hello Wei,
> > >
> > > I am very grateful for your response. In my test environment I
> first
> > > created a service offering of Custom Constrained (minCore=1,
> > >
> >  maxCore=10,
> > >>>
> >  minRam=1GB, maxRam=12GB, CPUSpeed=2000) with dynamic scaling
> enabled.
> > >
> >  But
> > >>>
> >  every time I tried to start the VM under this ServiceOffering I got
> > the
> > > above mentioned error. Please find the following agent log for that
> > > particular VM:
> > >
> > > https://controlc.com/4618c4d8
> > >
> > > HOST OS : Centos 7.9
> > > QEMU:   QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-175.el7_9.4),
> > >
> >  Copyright
> > 
> > > (c) 2003-2008 Fabrice Bellard
> > >
> > > And I think the error seems to be with the service offering (Custom
> > > Constrained). So, I created two Fixed services offering A(1 core
> and
> > >
> >  1GB)
> > >>>
> >  and B(2 Core and 2 GB) with dynamic scaling enabled. I then built a
> VM
> > > based on service offering A and the VM started(finally). But I did
> > not
> > >
> >  find
> > 
> > > any option to scale the VM while it's running. I was only able to
> > scale
> > >
> >  the
> > 
> > > VM to shutdown state.
> > >
> > > Thank You.
> > >
> > > On Wed, 17 Nov 2021 at 13:11, Wei ZHOU
> > wrote:
> > >
> > > Hi Abishek,
> > >>
> > >> I guess the error is same as before:
> > >>
> > >> qemu: invalid ram size: size=4194304k,slots=16,maxmem=1583660032k
> > >>
> > >>
> > >> What are your hypervisor/qemu version and guest OS version ?
> > >> Can you check agent.log and share the xml definition of the vm ?
> > >>
> > >> -Wei
> > >>
> > >> On Wed, 17 Nov 2021 at 05:18, Abishek Budhathoki <
> > abckd...@gmail.com
> > >> wrote:
> > >>
> > >> Hello Wei,
> > >>>
> > >>> I have also tested with limited service offering where max RAM is
> > >>>
> > >> 12GB
> > 
> > > and
> > >>
> > >>> CPU is 12 core. But the result is the same. I can not start the
> VM.
> > >>>
> > >> But
> > 
> > > if
> > >>
> > >>> I turn off Dynamic Scaling to Off on Advance Mode while creating
> > >>>
> > >> the
> > >>>
> >  instance I can start the VM.
> > >>>
> > >

Re: Size of the snapshots volume

[Slavka Peleva]

Unfortunately, I'm not familiar with XCP-NG. I rechecked your steps, and
there isn't a call to delete a volume snapshot. I think that destroying a
VM works almost the same for all hypervisors, and the volume snapshots
won't be deleted automatically. Can you check if they are visible in the UI?

On Thu, Oct 21, 2021 at 3:03 PM Yordan Kostov  wrote:

> Hey Slavka,
>
> Deployment is 4.15.2 + XCP-NG 8.2 utilizing fiber channel SAN as
> primary storage.
>
> Regards,
> Jordan
>
> -Original Message-
> From: Slavka Peleva 
> Sent: Thursday, October 21, 2021 2:54 PM
> To: users@cloudstack.apache.org
> Subject: Re: Size of the snapshots volume
>
>
> [X] This message came from outside your organization
>
>
> Hi Yordan,
>
> can you share what are you using for primary storage? In some cases, the
> deletion of snapshots on secondary isn't implemented. According to the
> code, the cleanup of the snapshots is only for the DB, not for cleaning the
> secondary storage.
>
> Best regards,
> Slavka
>
> On Thu, Oct 21, 2021 at 2:37 PM Vivek Kumar  .invalid>
> wrote:
>
> > Hello,
> >
> > You can check the the snapshot status in - snapshots table in DB. You
> > can also verify the status in  table called - snapshot_store_ref. Yes
> > cloudStack runs a cleanup job, timings depends what you have defined
> > in global setting  -
> >
> > storage.cleanup.delay   Determines how long (in seconds) to wait before
> > actually expunging destroyed volumes. The default value = the default
> value
> > of storage.cleanup.interval.Advanced
> > 86400
> >
> > storage.cleanup.enabled Enables/disables the storage cleanup thread.
> > Advanced
> > true
> >
> > storage.cleanup.intervalThe interval (in seconds) to wait before
> > running the storage cleanup thread.Advanced
> > 86400
> >
> >
> >
> > Vivek Kumar
> > Sr. Manager - Cloud & DevOps
> > IndiQus Technologies
> > M +91 7503460090
> > https://urldefense.com/v3/__http://www.indiqus.com__;!!A6UyJA!3CYjCk-6
> > l_RJxlZSVAgmTqt2LJFeWODa5bdiKclS7xGT1weD16tUBUGwVHeDrYKQpLoahZ_meJ1V$
> >
> >
> >
> >
> > > On 21-Oct-2021, at 4:38 PM, Yordan Kostov 
> wrote:
> > >
> > > Here is another thing I noticed.
> > > - have a VM with a volume snapshots
> > > - Expunge the VM so the disk is removed also
> > > - check the Secondary Storage - backup still remains.
> > >
> > > Does anyone knows if Cloudstack does a cleanup later or the orphaned
> > backups will remain?
> > >
> > > Regards,
> > > Jordan
> > >
> > > -Original Message-
> > > From: benoit lair 
> > > Sent: Tuesday, October 19, 2021 1:22 PM
> > > To: users@cloudstack.apache.org
> > > Subject: Re: Size of the snapshots volume
> > >
> > >
> > > [X] This message came from outside your organization
> > >
> > >
> > > Hello Yordan,
> > >
> > > I had same results with xcp-ng 8.2 and ACS 4.15.1
> > >
> > > The max filled during the life of the disk will be the size of the
> > snapshot
> > >
> > > That's why i looking towards SDS with a solution giving me
> > > possibility
> > to do some thin provisionning with XCP-NG I was thinking about an SDS
> > which could give me block storage or at least file storage and acting
> > as a proxy between my iscsi array and my xcp-ng
> > >
> > > Linstor could be a solution, but for the moment i don't know if the
> > plugin will be compatible with xcp-ng
> > >
> > > Regards, Benoit
> > >
> > > Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a
> > écrit :
> > >
> > >> Hello Benoit,
> > >>
> > >>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from
> > >> template - Centos 7, 46 GB hdd, 4% full
> > >>- VM1 - root disk is as full as template.
> > >>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
> > >> test_file1 )then the file was removed so the used space is again 4%.
> > >>- scheduled backup goes through both VMs. First snapshot size
> is
> > >>- VM1 -  2.3G
> > >>- VM2 -  41G
> > >>- Then on VM2 this script was run to fill and empty the disk
> > >> again
> > >> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> > >> 

Re: Size of the snapshots volume

[Slavka Peleva]

Hi Yordan,

can you share what are you using for primary storage? In some cases, the
deletion of snapshots on secondary isn't implemented. According to the
code, the cleanup of the snapshots is only for the DB, not for cleaning the
secondary storage.

Best regards,
Slavka

On Thu, Oct 21, 2021 at 2:37 PM Vivek Kumar 
wrote:

> Hello,
>
> You can check the the snapshot status in - snapshots table in DB. You can
> also verify the status in  table called - snapshot_store_ref. Yes
> cloudStack runs a cleanup job, timings depends what you have defined in
> global setting  -
>
> storage.cleanup.delay   Determines how long (in seconds) to wait before
> actually expunging destroyed volumes. The default value = the default value
> of storage.cleanup.interval.Advanced
> 86400
>
> storage.cleanup.enabled Enables/disables the storage cleanup thread.
> Advanced
> true
>
> storage.cleanup.intervalThe interval (in seconds) to wait before
> running the storage cleanup thread.Advanced
> 86400
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> IndiQus Technologies
> M +91 7503460090
> www.indiqus.com
>
>
>
>
> > On 21-Oct-2021, at 4:38 PM, Yordan Kostov  wrote:
> >
> > Here is another thing I noticed.
> > - have a VM with a volume snapshots
> > - Expunge the VM so the disk is removed also
> > - check the Secondary Storage - backup still remains.
> >
> > Does anyone knows if Cloudstack does a cleanup later or the orphaned
> backups will remain?
> >
> > Regards,
> > Jordan
> >
> > -Original Message-
> > From: benoit lair 
> > Sent: Tuesday, October 19, 2021 1:22 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Size of the snapshots volume
> >
> >
> > [X] This message came from outside your organization
> >
> >
> > Hello Yordan,
> >
> > I had same results with xcp-ng 8.2 and ACS 4.15.1
> >
> > The max filled during the life of the disk will be the size of the
> snapshot
> >
> > That's why i looking towards SDS with a solution giving me possibility
> to do some thin provisionning with XCP-NG I was thinking about an SDS which
> could give me block storage or at least file storage and acting as a proxy
> between my iscsi array and my xcp-ng
> >
> > Linstor could be a solution, but for the moment i don't know if the
> plugin will be compatible with xcp-ng
> >
> > Regards, Benoit
> >
> > Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a
> écrit :
> >
> >> Hello Benoit,
> >>
> >>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from
> >> template - Centos 7, 46 GB hdd, 4% full
> >>- VM1 - root disk is as full as template.
> >>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
> >> test_file1 )then the file was removed so the used space is again 4%.
> >>- scheduled backup goes through both VMs. First snapshot size is
> >>- VM1 -  2.3G
> >>- VM2 -  41G
> >>- Then on VM2 this script was run to fill and empty the disk
> >> again
> >> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> >>- scheduled backup goes through both VMs. All snapshots size is:
> >>- VM1 - 2.3G
> >>- VM2 - 88G
> >>
> >>Once the disk is filled you will get a snapshot with size no
> >> less than the size of the whole disk.
> >>May be there is a way to shrink it but I could not find it.
> >>
> >> Best regards,
> >> Jordan
> >>
> >> -Original Message-
> >> From: Yordan Kostov 
> >> Sent: Tuesday, October 12, 2021 3:58 PM
> >> To: users@cloudstack.apache.org
> >> Subject: RE: Size of the snapshots volume
> >>
> >>
> >> [X] This message came from outside your organization
> >>
> >>
> >> Hello Benoit,
> >>
> >>Unfortunately no.
> >>When I do it I will make sure to drop a line here.
> >>
> >> Best regards,
> >> Jordan
> >>
> >> -Original Message-
> >> From: benoit lair 
> >> Sent: Tuesday, October 12, 2021 3:40 PM
> >> To: users@cloudstack.apache.org
> >> Subject: Re: Size of the snapshots volume
> >>
> >>
> >> [X] This message came from outside your organization
> >>
> >>
> >> Hello Jordan,
> >>
> >> Could you proceed to your tests ? Have you got the same results ?
> >>
> >> Regards, Benoit Lair
> >>
> >> Le lun. 4 oct. 2021 à 17:59, Yordan Kostov  a
> >> écrit
> >> :
> >>
> >>> Here are a few considerations:
> >>>
> >>> - First snapshot of volume is always full snap.
> >>> - XenServer/XCP-NG backups are always thin.
> >>> - Thin provisioning calculations never go down. Even if you delete
> >>> data from disk.
> >>>
> >>> As you filled the disk of the VM to top the thin provisioning
> >>> threats it as full VM from that moment on even if data is deleted.
> >>> So the full snap that will be migrated to NFS will always be of max
> size.
> >>>
> >>> I am not 100% certain as I am yet to start running backup tests.
> >>>
> >>> Best regards,
> >>> Jordan
> >>>
> >>> -Original Message-
> >>> From: Florian Noel 
> >>> Sent: Monday, October 4, 2021 6:22 PM

Re: [!!Mass Mail]RE: Cloudstack 4.15.2 upgrade fail

[Slavka Peleva]

Sorry, I thought that the question for the space was for me because I've
missed that Евгений appeared in the conversation :)
Great Yordan!

On Mon, Oct 18, 2021 at 1:00 PM Slavka Peleva  wrote:

> No, there aren't any spaces. Can you update the type of the system VM form
> "USER" to "SYSTEM"?
>
> On Mon, Oct 18, 2021 at 12:48 PM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
>> Does you have space before systemvm template name?
>>
>> -Original Message-
>> From: Yordan Kostov [mailto:yord...@nsogroup.com]
>> Sent: Monday, October 18, 2021 12:42 PM
>> To: users@cloudstack.apache.org
>> Subject: [!!Mass Mail]RE: Cloudstack 4.15.2 upgrade fail
>>
>> Thank you Slavka,
>>
>> The template is already named that way:  https://imgur.com/aVQLpSY
>> From the screenshot you can see 2 entries - first one is the old 4.15
>> template and the second one is the new 4.15.1 template set with proper name.
>> Is there any other place the name should be changed?
>>
>> Best regards,
>> Jordan
>>
>>
>> -Original Message-
>> From: Slavka Peleva 
>> Sent: Monday, October 18, 2021 12:38 PM
>> To: users@cloudstack.apache.org
>> Subject: Re: Cloudstack 4.15.2 upgrade fail
>>
>>
>> [X] This message came from outside your organization
>>
>>
>> Hi Yordan,
>>
>> During the upgrade, CloudStack is looking for a specific template name -
>> "systemvm-xenserver-4.15.1". You can rename the uploaded template directly
>> in the DB, or I think you have to set for template's name -
>> "systemvm-xenserver-4.15.1" while uploading it.
>>
>> Best regards,
>> Slavka
>>
>> On Mon, Oct 18, 2021 at 12:12 PM Yordan Kostov 
>> wrote:
>>
>> > Hello everyone,
>> >
>> > Environment is  4.15.0 ACS on Centos 7 in HA setup on
>> > 3 node galera cluster managing XCP-NG hosts.
>> > Today I performed upgrade of ACS from to 4.15.2 as per
>> > this guide
>> > https://urldefense.com/v3/__http://docs.cloudstack.apache.org/en/lates
>> > t/upgrading/upgrade/upgrade-4.15.html__;!!A6UyJA!1XHKwiVUKxx9w1MZaZS2G
>> > n9gPDucxWw1w3wUXtx5wMFBlhYesJ5XbhTbeMakyy3EhaJ2P4styS-H$
>> >
>> > After upgrade the management service is running but GUI gives this
>> error:
>> > HTTP ERROR 503 Service Unavailable
>> > URI:
>> >
>> > /client/
>> >
>> > STATUS:
>> >
>> > 503
>> >
>> > MESSAGE:
>> >
>> > Service Unavailable
>> >
>> > SERVLET:
>> >
>> > -
>> >
>> >
>> > In management-server.log I see this error pops after starting the
>> service:
>> > 2021-10-18 11:04:55,142 ERROR [c.c.u.DatabaseUpgradeChecker]
>> > (main:null)
>> > (logid:) Unable to upgrade the database
>> > com.cloud.utils.exception.CloudRuntimeException: 4.15.1.0XenServer
>> > SystemVm template not found. Cannot upgrade system Vms
>> >
>> > I do registered the template upload as per the guide steps.
>> >
>> > Any advice?
>> >
>> > Best regards,
>> > Jordan
>> >
>> Внимание!
>> Это электронное письмо и все прикрепленные к нему файлы являются
>> конфиденциальными и предназначены исключительно для использования лицом
>> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
>> (лицами), которому (которым) предназначено это письмо, не копируйте и не
>> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
>> почтовой системы. Любое несанкционированное использование, распространение,
>> раскрытие, печать или копирование этого электронного письма и прикрепленных
>> к нему файлов, кроме как лицом (лицами) которому (которым) они
>> предназначены, является незаконным и запрещено. Принимая во внимание, что
>> передача данных посредством Интернет не является безопасной, мы не несем
>> никакой ответственности за любой потенциальный ущерб, причиненный в
>> результате ошибок при передаче данных или этим сообщением и прикрепленными
>> к нему файлами.
>>
>> 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: [!!Mass Mail]RE: Cloudstack 4.15.2 upgrade fail

[Slavka Peleva]

No, there aren't any spaces. Can you update the type of the system VM form
"USER" to "SYSTEM"?

On Mon, Oct 18, 2021 at 12:48 PM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Does you have space before systemvm template name?
>
> -Original Message-
> From: Yordan Kostov [mailto:yord...@nsogroup.com]
> Sent: Monday, October 18, 2021 12:42 PM
> To: users@cloudstack.apache.org
> Subject: [!!Mass Mail]RE: Cloudstack 4.15.2 upgrade fail
>
> Thank you Slavka,
>
> The template is already named that way:  https://imgur.com/aVQLpSY
> From the screenshot you can see 2 entries - first one is the old 4.15
> template and the second one is the new 4.15.1 template set with proper name.
> Is there any other place the name should be changed?
>
> Best regards,
> Jordan
>
>
> -Original Message-
> From: Slavka Peleva 
> Sent: Monday, October 18, 2021 12:38 PM
> To: users@cloudstack.apache.org
> Subject: Re: Cloudstack 4.15.2 upgrade fail
>
>
> [X] This message came from outside your organization
>
>
> Hi Yordan,
>
> During the upgrade, CloudStack is looking for a specific template name -
> "systemvm-xenserver-4.15.1". You can rename the uploaded template directly
> in the DB, or I think you have to set for template's name -
> "systemvm-xenserver-4.15.1" while uploading it.
>
> Best regards,
> Slavka
>
> On Mon, Oct 18, 2021 at 12:12 PM Yordan Kostov 
> wrote:
>
> > Hello everyone,
> >
> > Environment is  4.15.0 ACS on Centos 7 in HA setup on
> > 3 node galera cluster managing XCP-NG hosts.
> > Today I performed upgrade of ACS from to 4.15.2 as per
> > this guide
> > https://urldefense.com/v3/__http://docs.cloudstack.apache.org/en/lates
> > t/upgrading/upgrade/upgrade-4.15.html__;!!A6UyJA!1XHKwiVUKxx9w1MZaZS2G
> > n9gPDucxWw1w3wUXtx5wMFBlhYesJ5XbhTbeMakyy3EhaJ2P4styS-H$
> >
> > After upgrade the management service is running but GUI gives this error:
> > HTTP ERROR 503 Service Unavailable
> > URI:
> >
> > /client/
> >
> > STATUS:
> >
> > 503
> >
> > MESSAGE:
> >
> > Service Unavailable
> >
> > SERVLET:
> >
> > -
> >
> >
> > In management-server.log I see this error pops after starting the
> service:
> > 2021-10-18 11:04:55,142 ERROR [c.c.u.DatabaseUpgradeChecker]
> > (main:null)
> > (logid:) Unable to upgrade the database
> > com.cloud.utils.exception.CloudRuntimeException: 4.15.1.0XenServer
> > SystemVm template not found. Cannot upgrade system Vms
> >
> > I do registered the template upload as per the guide steps.
> >
> > Any advice?
> >
> > Best regards,
> > Jordan
> >
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> 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: Cloudstack 4.15.2 upgrade fail

[Slavka Peleva]

Hi Yordan,

During the upgrade, CloudStack is looking for a specific template name -
"systemvm-xenserver-4.15.1". You can rename the uploaded template directly
in the DB, or I think you have to set for template's name -
"systemvm-xenserver-4.15.1" while uploading it.

Best regards,
Slavka

On Mon, Oct 18, 2021 at 12:12 PM Yordan Kostov  wrote:

> Hello everyone,
>
> Environment is  4.15.0 ACS on Centos 7 in HA setup on 3
> node galera cluster managing XCP-NG hosts.
> Today I performed upgrade of ACS from to 4.15.2 as per
> this guide
> http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.15.html
>
> After upgrade the management service is running but GUI gives this error:
> HTTP ERROR 503 Service Unavailable
> URI:
>
> /client/
>
> STATUS:
>
> 503
>
> MESSAGE:
>
> Service Unavailable
>
> SERVLET:
>
> -
>
>
> In management-server.log I see this error pops after starting the service:
> 2021-10-18 11:04:55,142 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: 4.15.1.0XenServer
> SystemVm template not found. Cannot upgrade system Vms
>
> I do registered the template upload as per the guide steps.
>
> Any advice?
>
> Best regards,
> Jordan
>

Re: Shrinking RBD volume

[Slavka Peleva]

Hi Joshua,

I was able to reproduce the same problem with libvirt version 4.5.0

Error 530, org.libvirt.LibvirtException: invalid argument: can't shrink
capacity below existing allocation
{
  "accountid": "7e36ad14-f8eb-11eb-909b-02000a02012b",
  "cmd":
"org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin",
  "created": "2021-08-10T10:11:05+0300",
  "jobid": "9fb0bb12-bcfe-4109-974d-2b40cdcf5f59",
  "jobprocstatus": 0,
  "jobresult": {
"errorcode": 530,
"errortext": "org.libvirt.LibvirtException: invalid argument: can't
shrink capacity below existing allocation"
  },
  "jobresultcode": 530,
  "jobresulttype": "object",
  "jobstatus": 2,
  "userid": "7e36ccac-f8eb-11eb-909b-02000a02012b"
}

with libvirt version 5.0.0 there is another problem, but I didn't dig more
why

{
  "accountid": "8d16cd0d-3574-11eb-8b84-02000a02019c",
  "cmd":
"org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin",
  "completed": "2021-08-10T09:45:51+0300",
  "created": "2021-08-10T09:45:48+0300",
  "jobid": "7cbff5cb-90f2-4c70-8f94-40e8eef0dc7e",
  "jobprocstatus": 0,
  "jobresult": {
"errorcode": 530,
"errortext": "Failed to resize volume operation of volume UUID:
[b6809fce-bfb4-4b4f-a1e5-46cccd14e582] due to -
org.libvirt.LibvirtException: unsupported flags (0x4) in function
virStorageBackendRBDResizeVol"
  },
  "jobresultcode": 530,
  "jobresulttype": "object",
  "jobstatus": 2,
  "userid": "8d16eccb-3574-11eb-8b84-02000a02019c"
}

Best regards,
Slavka

On Tue, Aug 10, 2021 at 8:14 AM Joshua Schaeffer 
wrote:

> Is shrinking an RBD datadisk volume supported in ACS 4.15.0.0? When I try
> to shrink the volume (volume has no data on it and is unattached) I get an
> error:
>
> 2021-08-10 04:05:03,150 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-19:ctx-24b7cda8 job-771 ctx-c40ce838) (logid:ef1cc616)
> Seq 17-2639953806569271643: Sending  { Cmd , MgmtId: 90520733511963, via:
> 17(bllcloudcmp01), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.storage.ResizeVolumeCommand":{"path":"649f1b12-fd51-4171-bf70-b22a3cb74c57","pool":{"id":"10","uuid":"35850adc-d711-306f-b111-9c90205274b1","host":"bllcloudceph01-storage.harmonywave.cloud","path":"cloudstack","userInfo":"cloudstack:AQDURgdhqpXiOBAAuDq6_LET116OIBZU11pg0Q==","port":"0","type":"RBD"},"currentSize":"107374182400","newSize":"(20.00
> GB)
> 21474836480","shrinkOk":"true","vmInstance":"none","managed":"false","wait":"0"}}]
> }
> 2021-08-10 04:05:03,443 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-12:null) (logid:) Seq 17-2639953806569271643:
> Processing:  { Ans: , MgmtId: 90520733511963, via: 17, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.storage.ResizeVolumeAnswer":{"newSize":"(0 bytes)
> 0","result":"false","details":"org.libvirt.LibvirtException: invalid
> argument: can't shrink capacity below existing allocation","wait":"0"}}] }
> 2021-08-10 04:05:03,443 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-19:ctx-24b7cda8 job-771 ctx-c40ce838) (logid:ef1cc616)
> Seq 17-2639953806569271643: Received:  { Ans: , MgmtId: 90520733511963,
> via: 17(bllcloudcmp01), Ver: v1, Flags: 10, { ResizeVolumeAnswer } }
> 2021-08-10 04:05:03,507 WARN  [o.a.c.s.d.ObjectInDataStoreManagerImpl]
> (API-Job-Executor-19:ctx-24b7cda8 job-771 ctx-c40ce838) (logid:ef1cc616)
> Unsupported data object (VOLUME,
> org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@577a814a),
> no need to delete from object in store ref table
> 2021-08-10 04:05:03,510 WARN  [c.c.s.VolumeApiServiceImpl]
> (API-Job-Executor-19:ctx-24b7cda8 job-771 ctx-c40ce838) (logid:ef1cc616)
> Failed to resize the volume Vol[75|vm=null|DATADISK]
> 2021-08-10 04:05:03,581 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (API-Job-Executor-19:ctx-24b7cda8 job-771) (logid:ef1cc616) Unexpected
> exception while executing
> org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin
> com.cloud.utils.exception.CloudRuntimeException: Exception caught during
> resize volume operation of volume UUID: 649f1b12-fd51-4171-bf70-b22a3cb74c57
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateResizeVolume(VolumeApiServiceImpl.java:1288)
> at
> com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:1147)
> at
> com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:191)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.pro

Re: Can't select network offerings in new shared networks

[Slavka Peleva]

Hi Joshua,

Yes, I saw your previous email - and from what I understand, you're talking
about the virtual router in UI `Zones -> Zona-A ->PhysicalNetworkInBasicZone
-> Network Service Providers -> Virtual Router`, which is disabled, and
you're trying to enable it. Is that right? This information corresponds to
DB table `physical_network_service_providers`. I'm talking about another
table - `virtual_router_providers` in which the virtual router is missing
or is disabled. The `virtual_router_providers` has a relation with the
`physical_network_service_providers` table. Here is a reproduction of the
exception you got:


(localcloud) 🐱 > update networkserviceprovider
id=e6bae6cd-a701-4798-ac7a-8f073567c345 state=Disabled
{
  "networkserviceprovider": {
"canenableindividualservice": true,
"id": "e6bae6cd-a701-4798-ac7a-8f073567c345",
"name": "VirtualRouter",
"physicalnetworkid": "39cb8051-8b36-4bac-b71b-8a04d6979856",
"servicelist": [
  "Vpn",
  "Dhcp",
  "Dns",
  "Gateway",
  "Firewall",
  "Lb",
  "SourceNat",
  "StaticNat",
  "PortForwarding",
  "UserData"
],
"state": "Disabled"
  }
}
(localcloud) 🐱 > configure virtualrouterelement
id=3883f5da-a284-4984-8016-00dfdee703bf enabled=false
{
  "virtualrouterelement": {
"enabled": false,
"id": "3883f5da-a284-4984-8016-00dfdee703bf",
"nspid": "e6bae6cd-a701-4798-ac7a-8f073567c345"
  }
}
(localcloud) 🐱 > update networkserviceprovider
id=e6bae6cd-a701-4798-ac7a-8f073567c345 state=Enabled
{
  "accountid": "8d16cd0d-3574-11eb-8b84-02000a02019c",
  "cmd":
"org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd",
  "completed": "2021-07-16T09:14:56+0300",
  "created": "2021-07-16T09:14:56+0300",
  "jobid": "e5fd2c8e-7152-43e1-bae1-3c8b378fce9d",
  "jobprocstatus": 0,
  "jobresult": {
"errorcode": 530,
"errortext": "Provider is not ready, cannot Enable the provider, please
configure the provider first"
  },
  "jobresultcode": 530,
  "jobresulttype": "object",
  "jobstatus": 2,
  "userid": "8d16eccb-3574-11eb-8b84-02000a02019c"
}
🙈 Error: async API failed for job e5fd2c8e-7152-43e1-bae1-3c8b378fce9d
(localcloud) 🐱 > configure virtualrouterelement
id=3883f5da-a284-4984-8016-00dfdee703bf enabled=true
{
  "virtualrouterelement": {
"enabled": true,
"id": "3883f5da-a284-4984-8016-00dfdee703bf",
"nspid": "e6bae6cd-a701-4798-ac7a-8f073567c345"
  }
}
(localcloud) 🐱 > update networkserviceprovider
id=e6bae6cd-a701-4798-ac7a-8f073567c345 state=Enabled
{
  "networkserviceprovider": {
"canenableindividualservice": true,
"id": "e6bae6cd-a701-4798-ac7a-8f073567c345",
"name": "VirtualRouter",
"physicalnetworkid": "39cb8051-8b36-4bac-b71b-8a04d6979856",
"servicelist": [
  "Vpn",
  "Dhcp",
  "Dns",
  "Gateway",
  "Firewall",
  "Lb",
  "SourceNat",
  "StaticNat",
  "PortForwarding",
  "UserData"
],
"state": "Enabled"
  }
}

I'm talking about how to fix the problem with the exception. The problem
with the network offerings I couldn't help, because I'm with a Basic
network and don't have those options.

Best regards,
Slavka

On Fri, Jul 16, 2021 at 12:31 AM Joshua Schaeffer <
jschaef...@harmonywave.com> wrote:

> On 7/15/21 2:54 AM, Slavka Peleva wrote:
> > Hi Joshua,
> >
> > Can you check if the `VirtualRouter` provider is disabled and try to
> enable
> > it? Probably you're getting this error because it's disabled. You can
> check
> > the state with cloudmonkey/cmk ("list virtualrouterelements") or through
> DB
> > ("SELECT * FROM cloud.virtual_router_providers where
> type="VirtualRouter";")
> Slavka, thanks for your reply. Yes the "VirtualRouter" is disabled as I
> mentioned in my original post, however when I try to enable it I get the
> error message I provided as well:
>
> Enable provider
> (VirtualRouter) Provider is not ready, cannot Enable the provider,
> pleaseconfigure the provider first
>
> How do I actually configure the provider? I wasn&#

Re: Failure to start Virtual Router after upgrade to 4.15.1

[Slavka Peleva]

That's great! :)

On Thu, Jul 15, 2021 at 11:16 PM Edward St Pierre 
wrote:

> Hi Slavka,
>
> You are a lifesaver, I had two versions of the api in the directory:
> cloud-api-4.13.0.0.jar
> cloud-api-4.15.1.0.jar
>
> Removed the old version from the previous update and all is good.  Thanks
> for your help.
>
> Ed
>
>
> On Thu, 15 Jul 2021 at 20:55, Slavka Peleva 
> wrote:
>
> > Hi Eduard,
> >
> > Did you upgrade and cloudstack agents? I guess that `cloud-api` jar in
> > `/usr/share/cloudstack-agent/lib` is with an older version that does not
> > have the method `isPrivateGateway`
> >
> > Best regards,
> > Slavka
> >
> > On Thu, Jul 15, 2021 at 10:02 PM Edward St Pierre <
> > edward.stpie...@gmail.com>
> > wrote:
> >
> > > Hello,
> > >
> > > Any help or pointers would be greatly appreciated.
> > >
> > > After upgrading CS  Virtual routers to 4.15.1 The VM does actually get
> > > built and powers on (visible via console proxy), and then is suddenly
> > > powered off. and this error is displayed in the interface
> > >
> > > '(r-340-VM) Resource [Host:10] is unreachable: Host 10: Unable to start
> > > instance due to Unable to start VM:f308d9b5-632c-47d2-9b24-01f02bb257a5
> > due
> > > to error in finalizeStart, not retrying'
> > >
> > >
> > > Looking through the logs I cannot find anything other than the below
> snip
> > > that seem interesting:
> > >
> > > :"java.lang.NoSuchMethodError: 'boolean
> > > com.cloud.agent.api.to.IpAddressTO.isPrivateGateway()'
> > >
> > > Here are the full logs:
> > >
> > > 2021-07-15 19:45:43,250 DEBUG [c.c.a.t.Request]
> > > (AgentManager-Handler-5:null) (logid:) Seq 10-6995779071166649120:
> > > Processing:  { Ans: , MgmtId: 345050527765, via: 10, Ver: v1, Flags:
> > > 1110,
> > >
> > >
> >
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"340","name":"r-340-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"500","maxSpeed":"500","minRam":"(256.00
> > > MB) 268435456","maxRam":"(256.00 MB)
> > > 268435456","arch":"x86_64","os":"Debian GNU/Linux 9
> > > (64-bit)","platformEmulator":"Debian GNU/Linux 9 (64-bit)","bootArgs":"
> > > vpccidr=10.0.0.0/16 domain=cs9cloud.internal dns1=81.19.54.209 dns2=
> > > template=domP name=r-340-VM eth0ip=169.254.146.220
> > >
> > >
> >
> eth0mask=255.2","enableHA":"true","limitCpuUse":"false","enableDynamicallyScaleVm":"false","vncPassword":"M_cgfURA4I7i0BNoy2pmYw","vncAddr":"10.100.6.201","params":{},"uuid":"f308d9b5-632c-47d2-9b24-01f02bb257a5","enterHardwareSetup":"false","disks":[{"data":{"org.apache.
> > > cloudstack.storage.to
> > >
> >
> .VolumeObjectTO":{"uuid":"8a7e0ad0-69b1-46ed-a75c-e984b836a989","volumeType":"ROOT","dataStore":{"org.
> > > apache.cloudstack.storage.to
> > >
> >
> .PrimaryDataStoreTO":{"uuid":"658c4937-b7bc-3aa7-a0d3-aa144224dd52","id":"7","poolType":"RBD","host":"ceph-mon.cloudstack","path":"cloudstack2019","port":"6789","url":"RBD://ceph-mon.cloudstack/cloudstack2019/?ROLE=Primary&STOREUUID=658c4937-b7bc-3aa7-a0d3-aa144224dd52","isManaged":"false"}},"name":"ROOT-340","size":"(2.44
> > > GB)
> > >
> > >
> >
> 262144","path":"8a7e0ad0-69b1-46ed-a75c-e984b836a989","volumeId":"468","vmName":"r-340-VM","accountId":"9","format":"RAW","provisioningType":"THIN","id":"468","deviceId":"0","bytesReadRate":"(0
> > > bytes) 0","bytesWriteRate":"(0 bytes) 0","iopsReadRate":"(0 bytes)
> > > 0","iopsWriteRate":"(0 bytes)
> > >
&

Re: Failure to start Virtual Router after upgrade to 4.15.1

[Slavka Peleva]

Hi Eduard,

Did you upgrade and cloudstack agents? I guess that `cloud-api` jar in
`/usr/share/cloudstack-agent/lib` is with an older version that does not
have the method `isPrivateGateway`

Best regards,
Slavka

On Thu, Jul 15, 2021 at 10:02 PM Edward St Pierre 
wrote:

> Hello,
>
> Any help or pointers would be greatly appreciated.
>
> After upgrading CS  Virtual routers to 4.15.1 The VM does actually get
> built and powers on (visible via console proxy), and then is suddenly
> powered off. and this error is displayed in the interface
>
> '(r-340-VM) Resource [Host:10] is unreachable: Host 10: Unable to start
> instance due to Unable to start VM:f308d9b5-632c-47d2-9b24-01f02bb257a5 due
> to error in finalizeStart, not retrying'
>
>
> Looking through the logs I cannot find anything other than the below snip
> that seem interesting:
>
> :"java.lang.NoSuchMethodError: 'boolean
> com.cloud.agent.api.to.IpAddressTO.isPrivateGateway()'
>
> Here are the full logs:
>
> 2021-07-15 19:45:43,250 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-5:null) (logid:) Seq 10-6995779071166649120:
> Processing:  { Ans: , MgmtId: 345050527765, via: 10, Ver: v1, Flags:
> 1110,
>
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":"340","name":"r-340-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"500","maxSpeed":"500","minRam":"(256.00
> MB) 268435456","maxRam":"(256.00 MB)
> 268435456","arch":"x86_64","os":"Debian GNU/Linux 9
> (64-bit)","platformEmulator":"Debian GNU/Linux 9 (64-bit)","bootArgs":"
> vpccidr=10.0.0.0/16 domain=cs9cloud.internal dns1=81.19.54.209 dns2=
> template=domP name=r-340-VM eth0ip=169.254.146.220
>
> eth0mask=255.2","enableHA":"true","limitCpuUse":"false","enableDynamicallyScaleVm":"false","vncPassword":"M_cgfURA4I7i0BNoy2pmYw","vncAddr":"10.100.6.201","params":{},"uuid":"f308d9b5-632c-47d2-9b24-01f02bb257a5","enterHardwareSetup":"false","disks":[{"data":{"org.apache.
> cloudstack.storage.to
> .VolumeObjectTO":{"uuid":"8a7e0ad0-69b1-46ed-a75c-e984b836a989","volumeType":"ROOT","dataStore":{"org.
> apache.cloudstack.storage.to
> .PrimaryDataStoreTO":{"uuid":"658c4937-b7bc-3aa7-a0d3-aa144224dd52","id":"7","poolType":"RBD","host":"ceph-mon.cloudstack","path":"cloudstack2019","port":"6789","url":"RBD://ceph-mon.cloudstack/cloudstack2019/?ROLE=Primary&STOREUUID=658c4937-b7bc-3aa7-a0d3-aa144224dd52","isManaged":"false"}},"name":"ROOT-340","size":"(2.44
> GB)
>
> 262144","path":"8a7e0ad0-69b1-46ed-a75c-e984b836a989","volumeId":"468","vmName":"r-340-VM","accountId":"9","format":"RAW","provisioningType":"THIN","id":"468","deviceId":"0","bytesReadRate":"(0
> bytes) 0","bytesWriteRate":"(0 bytes) 0","iopsReadRate":"(0 bytes)
> 0","iopsWriteRate":"(0 bytes)
>
> 0","hypervisorType":"KVM","directDownload":"false","deployAsIs":"false"}},"diskSeq":"0","path":"8a7e0ad0-69b1-46ed-a75c-e984b836a989","type":"ROOT","_details":{"storageHost":"ceph-mon.cloudstack","managed":"false","storagePort":"6789","volumeSize":"(2.44
> GB)
>
> 262144"}}],"nics":[{"deviceId":"0","networkRateMbps":"-1","defaultNic":"false","pxeDisable":"true","nicUuid":"efeacfd4-95d1-4cdb-897d-a2f79bc25782","details":{"PromiscuousMode":"false","MacAddressChanges":"true","ForgedTransmits":"true"},"dpdkEnabled":"false","uuid":"bae5a165-83f2-4134-8ae0-6dc7a149a32a","ip":"169.254.146.220","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:92:dc","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":"false"}],"guestOsDetails":{},"extraConfig":{}},"result":"true","wait":"0","bypassHostMaintenance":"false"}},{"com.cloud.agent.api.check.CheckSshAnswer":{"result":"true","wait":"0","bypassHostMaintenance":"false"}},{"com.cloud.agent.api.GetDomRVersionAnswer":{"templateVersion":"Cloudstack
> Release 4.15.1 Wed 10 Mar 2021 05:38:45 AM
> UTC","scriptsVersion":"ac3f3efc5ffe5dbab9616395c32e0d3d
> ","result":"true","details":"Cloudstack Release 4.15.1 Wed 10 Mar 2021
> 05:38:45 AM UTC&ac3f3efc5ffe5dbab9616395c32e0d3d
>
> ","wait":"0","bypassHostMaintenance":"false"}},{"com.cloud.agent.api.PlugNicAnswer":{"result":"true","details":"success","wait":"0","bypassHostMaintenance":"false"}},{"com.cloud.agent.api.Answer":{"result":"false","details"
>
> at
>
> com.cloud.agent.resource.virtualnetwork.facade.IpAssociationConfigItem.generateConfig(IpAssociationConfigItem.java:45)
> at
>
> com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.generateCommandCfg(VirtualRoutingResource.java:489)
> at
>
> com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.executeRequest(VirtualRoutingResource.java:142)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtNetworkElementCommandWrapper.execute(LibvirtNetworkElementCommandWrapper.java:35)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtNetworkElementCommandWrapper.execute(LibvirtNetworkElementCommandWrapper.java:29)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(Li

Re: Can't select network offerings in new shared networks

[Slavka Peleva]

Hi Joshua,

Can you check if the `VirtualRouter` provider is disabled and try to enable
it? Probably you're getting this error because it's disabled. You can check
the state with cloudmonkey/cmk ("list virtualrouterelements") or through DB
("SELECT * FROM cloud.virtual_router_providers where type="VirtualRouter";")

Best regards,
Slavka

On Wed, Jul 14, 2021 at 7:41 PM Joshua Schaeffer 
wrote:

> ACS: 4.15.0.0
> Hypervisor: KVM
> OS: Ubuntu 20.04
>
> In creating a shared network I'm only given one network offering option
> and trying to figure out how to make the other offerings that are included
> with the base install available. I'm creating the shared network in the UI
> and the only network offering I can choose from is "QuickCloudNoServices".
> I can see in the list of network offerings that there are others defined
> and they are just the defaults included with the base install. Below are
> some screenshots of what I'm seeing:
>
>
> https://drive.google.com/file/d/1Y5G8J2-mfj68K0MoLIROHVfuziZIqq_m/view?usp=sharing
>
> https://drive.google.com/file/d/1Fz2NRM3ZssN3IGQ_Ju1FJJtGyM-Q1hSb/view?usp=sharing
>
> I think this is because the "VirtualRouter" network service provided for
> my guest network is disabled, but I get an error when I try to enable it.
> Under the physical network I click on the network, go to the "Network
> Service Providers' tab, select the "VirtualRouter" provider, and click
> "Enable provider". Afterwards I get the following message in the UI:
>
> Enable provider
> (VirtualRouter) Provider is not ready, cannot Enable the provider, please
> configure the provider first
>
> And I see the following in the management-server logs (I don't see
> anything relevant from the compute logs):
>
> 2021-07-14 16:08:54,090 DEBUG [c.c.a.ApiServlet]
> (qtp1644231115-6023:ctx-b12d46cd) (logid:4beba9f7) ===START===
> 172.16.44.18 -- GET
> id=a6bca386-7a6a-410b-aaa2-fe15c8f422d4&state=Enabled&command=updateNetworkServiceProvider&response=json
> 2021-07-14 16:08:54,134 DEBUG [c.c.a.ApiServer]
> (qtp1644231115-6023:ctx-b12d46cd ctx-23ad5938) (logid:4beba9f7) CIDRs from
> which account 'Acct[f8d6949d-cd74-11eb-b1da-5254008f72d5-admin]' is allowed
> to perform API calls: 0.0.0.0/0,::/0
> 2021-07-14  16:08:54,372 INFO
> [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-4:ctx-975d9732 job-324)
> (logid:b295210b) Add job-324 into job monitoring
> 2021-07-14 16:08:54,389 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (qtp1644231115-6023:ctx-b12d46cd ctx-23ad5938) (logid:4beba9f7) submit
> async job-324, details: AsyncJobVO {id:324, userId: 2, accountId: 2,
> instanceType: PhysicalNetworkServiceProvider, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd,
> cmdInfo:
> {"response":"json","ctxUserId":"2","httpmethod":"GET","ctxStartEventId":"812","id":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","state":"Enabled","ctxDetails":"{\"interface
> com.cloud.network.PhysicalNetworkServiceProvider\":\"a6bca386-7a6a-410b-aaa2-fe15c8f422d4\"}","ctxAccountId":"2","uuid":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","cmdEventType":"SERVICE.PROVIDER.UPDATE"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 90520733511963, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: null, removed: null}
> 2021-07-14 16:08:54,393 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-4:ctx-975d9732 job-324) (logid:321ad13e) Executing
> AsyncJobVO {id:324, userId: 2, accountId: 2, instanceType:
> PhysicalNetworkServiceProvider, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd,
> cmdInfo:
> {"response":"json","ctxUserId":"2","httpmethod":"GET","ctxStartEventId":"812","id":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","state":"Enabled","ctxDetails":"{\"interface
> com.cloud.network.PhysicalNetworkServiceProvider\":\"a6bca386-7a6a-410b-aaa2-fe15c8f422d4\"}","ctxAccountId":"2","uuid":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","cmdEventType":"SERVICE.PROVIDER.UPDATE"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 90520733511963, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: null, removed: null}
> 2021-07-14 16:08:54,394 DEBUG [c.c.a.ApiServlet]
> (qtp1644231115-6023:ctx-b12d46cd ctx-23ad5938) (logid:4beba9f7) ===END===
> 172.16.44.18 -- GET
> id=a6bca386-7a6a-410b-aaa2-fe15c8f422d4&state=Enabled&command=updateNetworkServiceProvider&response=json
> 2021-07-14 16:08:54,473 DEBUG [c.c.a.ApiServlet]
> (qtp1644231115-6056:ctx-331a4fdf) (logid:c108be52) ===START===
> 172.16.44.18 -- GET
> jobId=321ad13e-d97b-46e8-9e04-25100f52e2b0&command=queryAsyncJobResult&response=json
> 2021-07-14 16:08:54,483 DEBUG [c.c.n.NetworkServiceImpl]
> (API-Job-Executor-4:ctx-975d9732 job-324 ctx-831a584b) (logid:321ad13e)
> trying to update the state of the service provider id=37 on physical
> network: 206 to state: 

Re: User certificate - Cloudmonkey API keys?

[Slavka Peleva]

Hi Jeremy,

As far as I understand, from your second screenshot get into the View Users
-> required user-> user menu and there is an option to generate keys

Best regards,
Slavka

On Fri, Jun 25, 2021 at 12:45 PM Jeremy Hansen  wrote:

> It seems to have a problem when I use a certificate with a passphrase.
> Using -nodes seems to work.  I don’t understand though since the form in
> the interface has a place to put your passphrase.
>
> What I’m trying to do here is use Cloudmonkey with api keys, but I see
> nothing in Cloudstack to generate these keys:
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI#CloudStackcloudmonkeyCLI-Gettingstarted
>
> Maybe this is referencing an older version of Cloudstack?  Nothing in the
> users section from what I can see mentions anything about generating api
> keys.
>
>
>
>
> I see nothing about generating api keys.
>
> -jeremy
>
>
> On Jun 25, 2021, at 12:30 AM, Daan Hoogland 
> wrote:
>
> Jeremy,
> It seems to me you are creating a certificate request with that command
> and not a certificate. What file(s) did you try to upload?
> Google "creating keys and certificates" to get some clues about how to
> create those.
> regards,
>
> On Thu, Jun 24, 2021 at 9:57 AM Jeremy Hansen  wrote:
>
>> I’m trying to understand how to generate a user certificate.  I can’t
>> seem to find very much information.
>>
>>
>>
>> I tried:
>>
>> openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365
>>
>> but the output just results in an error:
>>
>>
>> Any clues?
>>
>> Thanks
>> -jeremy
>>
>>
>
> --
> Daan
>
>
>

Re: Snapshots are not working after upgrading to 4.15.0

[Slavka Peleva]

Hi all,

I've compared the delete of snapshots between 4.13 and 4.15.1. The main
difference is that when picking the snapshot strategy in 4.13, the deletion
is handled by XenserverSnapshotStrategy (renamed DefaultSnapshotStrategy in
the newer versions), and for 4.15.1 is handled by
StorageSystemSnapshotStrategy. The difference is that the first one deletes
the snapshot chain in secondary storage, the second deletes the snapshot
only on the primary (Ceph) storage. Gabriel, if you are aware of the
problem, can you correct me if I'm wrong?

Best regards,
Slavka

On Thu, Jun 17, 2021 at 4:23 PM Gabriel Bräscher 
wrote:

> Hi Andrei,
>
> I appreciate all the efforts and the help in narrowing down this issue. It
> looks similar and probably it is related to bug #4797 indeed.
> This bug is for some time to be fixed and I perfectly understand why you
> are not happy.
>
> I am speaking for myself here and I am not the Release Manager (RM) of
> 4.15.1.0 but In my point of view, this does not necessarily impact on
> blocking 4.15.1.0.
>
> Fixing it has been proving a bit trickier and also requires manual tests
> with different environment configurations and some time to debug and
> develop.
> I myself had no time to fix it for 4.15.1.0 thus decided to not hold
> 4.15.1.0 as it would mean that many users would not have several bug fixes
> due to this one.
>
> To give some context. I work for a hosting company that has been
> contributing to bug fixes and new features for a long time.
> We even fixed bugs that do not impact us directly (e.g. issues that affect
> storage systems we do not use, or a hypervisor we do not use, etc).
> This means that I, as a contributor, sometimes have less time for some
> tasks than other ones.
>
> With that said, I will be re-checking this issue soon(ish) but I cannot
> guarantee that I will be able to bring a fix in time for 4.15.1.0.
> If any contributor has time to fix it I would be happy to help with review
> and testing.
>
> Best regards,
> Gabriel.
>
> Em qui., 17 de jun. de 2021 às 07:31, Andrei Mikhailovsky
>  escreveu:
>
> > Hi Suresh,
> >
> > This is what I've answered on the db tables:
> >
> > The table snapshots has NULL under the removed column in all
> snapshots
> > that I've
> > removed. The table snapshot_store_ref has no such column, but the
> > state shown
> > as Destroyed.
> >
> >
> > I've done some more checking under the ssvm itself, which look ok:
> >
> >
> > root@s-2536-VM:/usr/local/cloud/systemvm#
> > /usr/local/cloud/systemvm/ssvm-check.sh
> > 
> > First DNS server is  192.168.169.254
> > PING 192.168.169.254 (192.168.169.254): 56 data bytes
> > 64 bytes from 192.168.169.254: icmp_seq=0 ttl=64 time=0.520 ms
> > 64 bytes from 192.168.169.254: icmp_seq=1 ttl=64 time=0.294 ms
> > --- 192.168.169.254 ping statistics ---
> > 2 packets transmitted, 2 packets received, 0% packet loss
> > round-trip min/avg/max/stddev = 0.294/0.407/0.520/0.113 ms
> > Good: Can ping DNS server
> > 
> > Good: DNS resolves cloudstack.apache.org
> > 
> > nfs is currently mounted
> > Mount point is /mnt/SecStorage/ceb27169-9a58-32ef-81b4-33b0b12e9aa2
> > Good: Can write to mount point
> > 
> > Management server is 192.168.169.13. Checking connectivity.
> > Good: Can connect to management server 192.168.169.13 port 8250
> > 
> > Good: Java process is running
> > 
> > Tests Complete. Look for ERROR or WARNING above.
> >
> >
> > The management server does show errors like these, without any further
> > details:
> >
> > 2021-06-17 10:31:06,197 DEBUG [c.c.s.StorageManagerImpl]
> > (StorageManager-Scavenger-1:ctx-b9b038de) (logid:d96d09c4) Failed to
> delete
> > snapshot: 55183 from storage
> > 2021-06-17 10:31:06,280 DEBUG [o.a.c.s.s.SnapshotObject]
> > (StorageManager-Scavenger-1:ctx-b9b038de) (logid:d96d09c4) Failed to
> update
> > state:com.cloud.utils.fsm.NoTransitionException: Unable to transition to
> a
> > new state from Destroyed via DestroyRequested
> > 2021-06-17 10:31:06,281 DEBUG [c.c.s.StorageManagerImpl]
> > (StorageManager-Scavenger-1:ctx-b9b038de) (logid:d96d09c4) Failed to
> delete
> > snapshot: 84059 from storage
> > 2021-06-17 10:31:06,363 DEBUG [o.a.c.s.s.SnapshotObject]
> > (StorageManager-Scavenger-1:ctx-b9b038de) (logid:d96d09c4) Failed to
> update
> > state:com.cloud.utils.fsm.NoTransitionException: Unable to transition to
> a
> > new state from Destroyed via DestroyRequested
> >
> >
> > Regarding the bug 4797. I can't really comment as it has very little
> > technical details without the management log errors, etc. But
> essentially,
> > at the high level, the snapshots are not deleted from the backend in my
> > case, just like in the bug 4797.
> >
> >
> > TBH, I am very much s

Re: Snapshots are not working after upgrading to 4.15.0

[Slavka Peleva]

Hi, Andrei,

After a quick check of the code, I guess that the backup of the snapshot
fails because the secondary storage space should be less than 90%, and you
pointed that yours is 90.6% full.

Regards,
Slavka

On Mon, Jun 14, 2021 at 1:10 PM Andrei Mikhailovsky
 wrote:

> Hi Harikrishna,
>
> I've done some more testing testing just now. Please see below the answers
> to your questions/comments:
>
>
>
> - Original Message -
> > From: "Harikrishna Patnala" 
> > To: "users" 
> > Sent: Tuesday, 8 June, 2021 03:33:57
> > Subject: Re: Snapshots are not working after upgrading to 4.15.0
>
> > Hi Andrei,
> >
> > Can you check the following things and let us know?
> >
> >
> >  1.  Can you try creating a new volume and then create snapshot of that,
> to check
> >  if this an issue with old entries
>
> AM: I've done testing with a newly created image which was attached to a
> vm. The same problem happens with new images as well as old images. Please
> see the link below for the management server log.
>
>
> https://zerobin.net/?5781e4b65d9e3605#+GtIC7JBtp70Q0cw65cypJDiSyba/r/JldRsAyOI8l4=
>
>
> >  2.  For the snapshots which are failing can you check if you are seeing
> any
> >  error messages like this "Can't find an image storage in zone with less
> than".
> >  This is to check if secondary storage free space check failed.
>
>
> AM: I do not see any such message in the logs. tried grepping the logs for
> a couple of weeks and nothing comes up. Having said this, the secondary
> storage is about 90.6% full.
>
>
> >  3.  For the snapshots which are failing and if it is delta snapshot can
> you
> >  check if its parent's snapshot entry exists in "snapshot_store_ref"
> table with
> >  'parent_snapshot_id' of the current snapshot with 'store_role' "Image".
> This is
> >  to find the secondary storage where the parent snapshot backup is
> located.
> >
>
> AM: all snapshots are failing, not just selective few. Some volumes are
> brand new, as I've indicated above, others do have previous snapshots. I
> only have a single secondary storage, so all snaps should be in one place.
>
>
>
>
> > Regards,
> > Harikrishna
> > 
> > From: Andrei Mikhailovsky 
> > Sent: Monday, June 7, 2021 7:00 PM
> > To: users 
> > Subject: Snapshots are not working after upgrading to 4.15.0
> >
> > Hello everyone,
> >
> > I am having an issue with volume snapshots since I've upgraded to
> 4.15.0. None
> > of the volumes are being snapshotted regardless if the snapshot is
> initiated
> > manually or from the schedule. The strange thing is that if I manually
> take the
> > snapshot, the GUI shows Success status, but the Storage>Snapshots show
> an Error
> > status. Here is what I see in the management server logs:
> >
> > 2021-06-07 13:55:20,022 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01)
> Done
> > executing com.cloud.vm.VmWorkTakeVolumeSnapshot for job-86143
> > 2021-06-07 13:55:20,024 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> > (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01)
> Remove
> > job-86143 from job monitoring
> > 2021-06-07 13:55:20,094 DEBUG [o.a.c.s.s.SnapshotServiceImpl]
> > (BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Failed to copy
> snapshot
> > com.cloud.utils.exception.CloudRuntimeException: can not find an image
> stores
> > at
> >
> org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:271)
> > at
> >
> org.apache.cloudstack.storage.snapshot.DefaultSnapshotStrategy.backupSnapshot(DefaultSnapshotStrategy.java:171)
> > at
> >
> com.cloud.storage.snapshot.SnapshotManagerImpl$BackupSnapshotTask.runInContext(SnapshotManagerImpl.java:1238)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
> > at
> >
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> > at
> >
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> > at
> >
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> > at
> >
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> > at java.base/java.lang.Thread.run(Thread.java:829)
> > 2021-06-07 13:55:20,152 DEBUG [c.c.s.s.SnapshotManagerImpl]
> > (BackupSnapshotT

Re: Meet the CloudStack Community: Who is NEXT?

[Slavka Peleva]

Great to hear that, Rohit, even if you don't complete the book ;) And
Andrija will survive the interview 😇

I can't wait to watch the interviews with you :)

Kind regards,
Slavka

Re: Meet the CloudStack Community: Who is NEXT?

[Slavka Peleva]

Hi Ivet, all,

The video with Gabriel was great! I hope these people don't get mad at
me for involving them in this, but I'll be happy to hear something
from Rohit, Daan or Andrija (mixed with his sense of humor) :)

Best regards,

Slavka


On Fri, Jun 11, 2021 at 11:30 AM Ivet Petrova 
wrote:

> Hello all, and Happy Friday!
>
> I hope you are ready for the upcoming weekend. You have seen a few videos
> on the ACS channel which are under the Meet the Community Series.
> To make this videos more interesting for the community, I wanted to ask
> all of you: Who will you nominate for the next videos on the channel?
> If you think that you know a community member, who is inspiring and will
> share a great story, please nominate him for the video series!
>
> Look forward to hear your opinion!
>
> Kind regards,
>
>
>
>
>

Re: UEFI-Boot with Windows VM, attach ISO failes

[Slavka Peleva]

Hi, Daan, Udo,

I've already opened a PR for this
https://github.com/apache/cloudstack/pull/5072

Kind regards,
Slavka

On Fri, Jun 4, 2021 at 10:40 AM Daan Hoogland 
wrote:

> I think you hit a limitation of the system  Udo,
> Can you enter an issue on github, please?
> please add the hypervisor type and make to the ticket as well.
>
> On Wed, Jun 2, 2021 at 4:37 PM Udo Müller  wrote:
>
> > Oh i forgot: I am using 4.15.1 SNAPSHOT
> >
> > Am 02.06.21 um 16:36 schrieb Udo Müller:
> > > Hi guys,
> > >
> > > next thing i stumple upon:
> > >
> > > I have a VM which is setup from a windows categorized ISO and boottype
> > > UEFI.
> > >
> > > I can create and run the VM. But if i detach the ISO and want to
> > > attach another one i get the following error:
> > >
> > >
> >
> [{"com.cloud.agent.api.Answer":{"result":"false","details":"org.libvirt.LibvirtException:
> >
> > > Interner Fehler: No device with bus 'ide' and target 'hdc'. cdrom and
> > > floppy device hotplug isn't supported by
> > > libvirt","wait":"0","bypassHostMaintenance":"false"}}]
> > >
> > > Thats correct because the VM is create with a SATA cdrom.
> > >
> > >
> > > What do i have to do to be able to reattach ISO files?
> > >
> > >
> > > Regards Udo
> > >
> >
>
>
> --
> Daan
>

Re: 4.15.1 Snapshot UEFI Legacy: Unable to start VM due to Unsupported Configuration: IDE controllers are unsupported for this QEMU binary or machine type

[Slavka Peleva]

Hi Udo,

I saw where is the problem, the OS type of your ISO is "Other (32 bit)" on
which CloudStack sets "ide" for bus.
'sata' is set on Windows OS types;
'virtio' on these -  Ubuntu, Fedora ,CentOS,Red Hat Enterprise Linux,Debian
GNU/Linux,FreeBSD,Oracle,Other PV;
'scsi' on "Other PV Virtio-SCSI" OS types;
the rest gets 'ide' for bus

Regards,
Slavka

On Tue, Jun 1, 2021 at 6:24 PM Udo Müller  wrote:

> Hi Slavka,
>
> Deployment is done via WebUI. In this case i choose the target host
> (since only this one has debug enabled), then choose service, disk and
> network offering, activate advanced boot options and check UEFI Legacy.
>
> After setting the name the vm is started.
>
> The XML of the VM is attached.
>
> There you see
>
> 
>
> But the VM will work with sata instead of ide. I tested it by defining a
> VM via virt-manager and choosing sata for the bus type.
>
> See also:
>
> https://bugs.launchpad.net/nova/+bug/1831538
>
> Regards Udo
>
>
> Am 01.06.21 um 16:16 schrieb Slavka Peleva:
> > Hi Udo,
> >
> > Could you please share more information about the deployment of a VM?
> > Are you creating a new instance from ISO or a template? Also, can you set
> > the DEBUG level at the agent, and is it possible to share the XML that
> > CloudStack sends to libvirt (it's in the
> > /var/log/cloudstack/agent/agent.log)?
> >
> > One more question did you update and the management with the 4.15.1.0
> > version?
> >
> > Kind regards,
> > Slavka
> >
> > On Tue, Jun 1, 2021 at 4:33 PM Udo Müller  wrote:
> >
> >> Hi guys,
> >>
> >>
> >> I played around with cloudstack 4.15 and UEFI boot until someone here
> >> pointed me to a PR which fixes the problem with the missing q35 chipset.
> >>
> >> Thats the reason why I just installed the 4.15.1 SNAPSHOT.
> >>
> >> Now I get the following problem:
> >>
> >> Unable to start VM on Host... due to Unsupported Configuration: IDE
> >> controllers
> >> are unsupported for this QEMU binary or machine type
> >>
> >> I am using cloudstack on CentOS 7.9 with
> >>
> >> # rpm -qa | egrep "(qemu|libvirtd|OVMF|cloudstack)"
> >> *cloudstack*-agent-4.15.1.0-SNAPSHOT.20210601.el7.x86_64
> >> *qemu*-kvm-ev-2.12.0-44.1.el7_8.1.x86_64
> >> ipxe-roms-*qemu*-20180825-3.git133f4c.el7.noarch
> >> libvirt-daemon-driver-*qemu*-4.5.0-36.el7.x86_64
> >> *OVMF*-20180508-6.gitee3198e672e2.el7.noarch
> >> *qemu*-img-ev-2.12.0-44.1.el7_8.1.x86_64
> >> *cloudstack*-common-4.15.1.0-SNAPSHOT.20210601.el7.x86_64
> >> *qemu*-kvm-common-ev-2.12.0-44.1.el7_8.1.x86_64
> >>
> >> 1) Is the PR regarding the q35 chipset already included in the SNAPSHOT?
> >> I guess yes, because with 4.15.0 and i440 chipset the VM could be
> >> created and was running.
> >>
> >> 2) What do I have to change inside my settings to switch from IDE to
> >> SCSI or SATA?
> >>
> >> Regards Udo
> >>
>

Re: 4.15.1 SNAPSHOT: cant create users to account

[Slavka Peleva]

Hi Udo,

I was able to reproduce the problem with the new UI. With the old UI, you
can create a user. You can open an issue on GitHub for the problem

Regards,
Slavka

On Tue, Jun 1, 2021 at 6:46 PM Udo Müller  wrote:

> Oops
>
>
> now the screenshots are attached.
>
> Regards udo
>
> Am 01.06.21 um 17:43 schrieb Udo Müller:
> > Oh and btw: The Add user-Popup is rendered wrong in Safari, but is
> > working fine in Chrome and Firefox.
> >
> > See attached screenshots.
> >
> > Is it possible for me to change anything to get this back to work?
> >
> > Regards Udo
> >
> >
> > Am 01.06.21 um 17:33 schrieb Udo Müller:
> >> Hi all,
> >>
> >> The following was working with 4.15.0.
> >>
> >>
> >> Status quo: 4.15.1 SNAPSHOT, database new initialized. Configuration
> >> done with the same settings as 4.15.0
> >>
> >>
> >> i am trying to add a user to the account admin. So i click on
> >>
> >> Accounts -> admin -> View Users -> Add User
> >>
> >> Popup Window opens fine.
> >>
> >>
> >> - When i enter all required fields (username, password 2x, email,
> >> first and last name) and hit ok, i get the error, that the parameter
> >> "account" is missing.
> >>
> >> - When i do like above and then click on the drop-down field Domain
> >> it is empty. Same for drop-down Account.
> >>
> >>
> >> Means i cant create users to accounts which is absolutely needed for
> >> my application.
> >>
> >>
> >> management.log
> >>
> >> 2021-06-01 15:31:27,334 DEBUG [c.c.a.ApiServlet]
> >> (qtp1630678941-3995:ctx-cff2deda) (logid:0a4b2d51) ===START===
> >> 192.168.7.244 -- POST  command=createUser&response=json
> >> 2021-06-01 15:31:27,339 DEBUG [c.c.a.ApiServer]
> >> (qtp1630678941-3995:ctx-cff2deda ctx-f77a5abe) (logid:0a4b2d51) CIDRs
> >> from which account 'Acct[a7e89cef-c2ca-11eb-8de2-525400f5bc6b-admin]'
> >> is allowed to perform API calls: 0.0.0.0/0,::/0
> >> 2021-06-01 15:31:27,341 INFO  [c.c.a.ApiServer]
> >> (qtp1630678941-3995:ctx-cff2deda ctx-f77a5abe) (logid:0a4b2d51)
> >> Unable to execute API command createuser due to missing parameter
> >> account
> >>
> >> apilog.log
> >>
> >> 2021-06-01 15:31:27,342 INFO  [a.c.c.a.ApiServer]
> >> (qtp1630678941-3995:ctx-cff2deda ctx-f77a5abe) (logid:0a4b2d51)
> >> (userId=2 accountId=2 sessionId=node0cacgcc2ki0zr1kjau5c1p59w511)
> >> 192.168.7.244 -- POST command=createUser&response=json 431 Unable to
> >> execute API command createuser due to missing parameter account
> >>
> >>
>

Re: 4.15.1 Snapshot UEFI Legacy: Unable to start VM due to Unsupported Configuration: IDE controllers are unsupported for this QEMU binary or machine type

[Slavka Peleva]

Hi Udo,

Could you please share more information about the deployment of a VM?
Are you creating a new instance from ISO or a template? Also, can you set
the DEBUG level at the agent, and is it possible to share the XML that
CloudStack sends to libvirt (it's in the
/var/log/cloudstack/agent/agent.log)?

One more question did you update and the management with the 4.15.1.0
version?

Kind regards,
Slavka

On Tue, Jun 1, 2021 at 4:33 PM Udo Müller  wrote:

> Hi guys,
>
>
> I played around with cloudstack 4.15 and UEFI boot until someone here
> pointed me to a PR which fixes the problem with the missing q35 chipset.
>
> Thats the reason why I just installed the 4.15.1 SNAPSHOT.
>
> Now I get the following problem:
>
> Unable to start VM on Host... due to Unsupported Configuration: IDE
> controllers
> are unsupported for this QEMU binary or machine type
>
> I am using cloudstack on CentOS 7.9 with
>
> # rpm -qa | egrep "(qemu|libvirtd|OVMF|cloudstack)"
> *cloudstack*-agent-4.15.1.0-SNAPSHOT.20210601.el7.x86_64
> *qemu*-kvm-ev-2.12.0-44.1.el7_8.1.x86_64
> ipxe-roms-*qemu*-20180825-3.git133f4c.el7.noarch
> libvirt-daemon-driver-*qemu*-4.5.0-36.el7.x86_64
> *OVMF*-20180508-6.gitee3198e672e2.el7.noarch
> *qemu*-img-ev-2.12.0-44.1.el7_8.1.x86_64
> *cloudstack*-common-4.15.1.0-SNAPSHOT.20210601.el7.x86_64
> *qemu*-kvm-common-ev-2.12.0-44.1.el7_8.1.x86_64
>
> 1) Is the PR regarding the q35 chipset already included in the SNAPSHOT?
> I guess yes, because with 4.15.0 and i440 chipset the VM could be
> created and was running.
>
> 2) What do I have to change inside my settings to switch from IDE to
> SCSI or SATA?
>
> Regards Udo
>

Re: CSEUG Virtual - Session Recordings

[Slavka Peleva]

Thanks for sharing, Ivet,

The event was great! Many thanks to all that participated in it! :)

Kind regards,
Slavka

On Tue, Jun 1, 2021 at 11:27 AM Ivet Petrova 
wrote:

> Hi All and Happy Tuesday :)
>
> If you have missed CSEUG Virtual or some talks out of it, I am happy to
> share that this week we will publish the recordings on the official Apache
> CloudStack YouTube channel.
> The videos will come live this and next week on an instant premier on the
> channel.
>
> If you still have not subscribed to ACS channel on YouTube, now is the
> time to do so, to be notified when the videos come live:
>
> Watch the videos here:
> https://www.youtube.com/watch?v=Ph-NQv80j0k&list=PLnIKk7GjgFlbG2W3lRW9Evjy2Vtg_HKHX
>
> Kind regards,
>
>
>
>
>

Re: cloudstack 4.15: UEFI boot, chipset q35

[Slavka Peleva]

Hi Udo,

Unfortunately, I don't know the exact date. I guess it will be announced in
a few days.
Here is the thread of the discussion of its release
https://www.mail-archive.com/dev@cloudstack.apache.org/msg95593.html

Regards,
Slavka

On Mon, May 31, 2021 at 10:59 PM Udo Müller  wrote:

> Hi Slavka,
>
> Thx for your answer. I found that already and thought it is included in my
> download of 4.15.0
>
> Is a date for 4.15.1 known already?
>
> Regards Udo
>
> Gruß Udo Müller
>
> > Am 31.05.2021 um 18:42 schrieb Slavka Peleva
> :
> >
> > Hi Udo,
> >
> > There is a fix of this problem with UEFI legacy boot mode, which is
> > included in version 4.14.1.0, and will also be included in 4.15.1.0
> > PR 4576
> >
> > <https://github.com/apache/cloudstack/pull/4576>
> > Best regards,
> > Slavka
> > <https://github.com/apache/cloudstack/pull/4576>
> >
> >> On Mon, May 31, 2021 at 5:58 PM Udo Müller  wrote:
> >>
> >> Hi guys,
> >>
> >> i have set up a cloudstack 4.15 with a KVM cluster and i try to get UEFI
> >> legacy boots running.
> >>
> >> The VM itself boots fine but i cant get a console via cloudstack or
> >> virt-manager
> >>
> >> Guest has not initialized the graphics
> >>
> >> Checking the XML of the VM i can see:
> >>
> >> # virsh dumpxml 48 | egrep "(domain type|arch|loader|nvram)"
> >> 
> >> hvm
> >>  >> type='pflash'>/usr/share/OVMF/OVMF_CODE.secboot.fd
> >>  >>
> >>
> template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/c8e95c63-34d5-40f9-88ca-ad37f87db345.fd
> >>
> >>
> >> But this is not what i expect:
> >>
> >> hvm
> >>
> >> should be sth like
> >>
> >> hvm
> >>
> >>
> >> It looks like cloudstack isnt generating the correct XML. What is needed
> >> to make cloudstack manager generate the correct XML containing the
> >> supported chipset?
> >>
> >>
> >> System: CentOS 7.9
> >>
> >> # rpm -qa | grep cloudstack
> >> cloudstack-common-4.15.0.0-1.el7.x86_64
> >> cloudstack-management-4.15.0.0-1.el7.x86_64
> >> cloudstack-cli-4.15.0.0-1.el7.x86_64
> >>
> >>
> >> Agent: CentOS 7.9
> >>
> >> # rpm -qa | grep cloudstack
> >> cloudstack-common-4.15.0.0-1.el7.x86_64
> >> cloudstack-management-4.15.0.0-1.el7.x86_64
> >> cloudstack-cli-4.15.0.0-1.el7.x86_64
> >>
> >>
> >>
> >> The needed
> >>
> >>
>
>

Re: cloudstack 4.15: UEFI boot, chipset q35

[Slavka Peleva]

Hi Udo,

There is a fix of this problem with UEFI legacy boot mode, which is
included in version 4.14.1.0, and will also be included in 4.15.1.0
PR 4576


Best regards,
Slavka


On Mon, May 31, 2021 at 5:58 PM Udo Müller  wrote:

> Hi guys,
>
> i have set up a cloudstack 4.15 with a KVM cluster and i try to get UEFI
> legacy boots running.
>
> The VM itself boots fine but i cant get a console via cloudstack or
> virt-manager
>
>  Guest has not initialized the graphics
>
> Checking the XML of the VM i can see:
>
> # virsh dumpxml 48 | egrep "(domain type|arch|loader|nvram)"
> 
>  hvm
>   type='pflash'>/usr/share/OVMF/OVMF_CODE.secboot.fd
>  
> template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/c8e95c63-34d5-40f9-88ca-ad37f87db345.fd
>
>
> But this is not what i expect:
>
>  hvm
>
> should be sth like
>
>  hvm
>
>
> It looks like cloudstack isnt generating the correct XML. What is needed
> to make cloudstack manager generate the correct XML containing the
> supported chipset?
>
>
> System: CentOS 7.9
>
> # rpm -qa | grep cloudstack
> cloudstack-common-4.15.0.0-1.el7.x86_64
> cloudstack-management-4.15.0.0-1.el7.x86_64
> cloudstack-cli-4.15.0.0-1.el7.x86_64
>
>
> Agent: CentOS 7.9
>
> # rpm -qa | grep cloudstack
> cloudstack-common-4.15.0.0-1.el7.x86_64
> cloudstack-management-4.15.0.0-1.el7.x86_64
> cloudstack-cli-4.15.0.0-1.el7.x86_64
>
>
>
> The needed
>
>

Re: CSEUG Virtual - May 27th, 2021

[Slavka Peleva]

Thanks, Ivet, Giles,

This is a cool idea to have a virtual event! We from StorPool will be happy
to join it

Best regards,
Slavka

On Thu, Apr 1, 2021 at 11:16 AM Ivet Petrova 
wrote:

> Hello,
>
> The registration for CSEUG Virtual is now open:
> https://zoom.us/webinar/register/3216172602723/WN_-zsXhTq_Ttu1Ktz82my06Q
>
> Let’s make the first online event great together!
>
> Kind regards,
>
>
> ivet.petr...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
> On 31 Mar 2021, at 17:41, Ivet Petrova  ivet.petr...@shapeblue.com>> wrote:
>
> Hello,
>
> The CSEUG has not met since Berlin in February 2020.
>
> For that reason, on May 27th Giles and myself are organising CloudStack
> European User Group Virtual. The event will be completely online, starting
> from 13 CET time to 17.30 CET time. (Check your time zone here<
> https://www.worldtimebuddy.com/?qm=1&lid=2643743,2950159,727011,1273294&h=2643743&date=2021-5-27&sln=12-17&hf=0
> >)
>
> We look for volunteers who want to join with talks and present their
> stories with CloudStack.
> This will be the first virtual event and although the pandemic and
> everything, we hope it will bring some great spirit, option to meet again
> and support the community and CloudStack as a project.
>
> Is anybody interested to do a talk? The slots will be just 30 minutes so
> that they can fit the people with busy agenda.
>
> Kind regards,
>
>
> ivet.petr...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
>

Re: Congratulations to Gabriel - CloudStack PMC Chair

[Slavka Peleva]

Congratulations, Gabriel! I wish you all the best with the new role!

On Thu, Mar 18, 2021 at 12:35 PM Daan Hoogland 
wrote:

> parabens e successo, Gabriel.
>
> On Thu, Mar 18, 2021 at 10:50 AM Abhishek Kumar <
> abhishek.ku...@shapeblue.com> wrote:
>
> > Congrats Gabriel 👍
> > 
> > From: Paul Angus 
> > Sent: 18 March 2021 02:40
> > To: d...@cloudstack.apache.org ;
> > users@cloudstack.apache.org 
> > Cc: priv...@cloudstack.apache.org 
> > Subject: Congratulations to Gabriel - CloudStack PMC Chair
> >
> > Hi All CloudStack enthusiasts!
> >
> >
> >
> > Please join me in congratulating Gabriel for becoming the next CloudStack
> > PMC Chair.
> >
> > Congratulations Gabriel, very well deserved!
> >
> >
> >
> > I would also like to thank Sven for his great work of the past year!
> >
> >
> >
> >
> >
> >
> >
> > Kind regards
> >
> >
> >
> > Paul Angus
> >
> >
> >
> >
> > abhishek.ku...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >
>
> --
> Daan
>

Re: Congratulations to Sven - Apache Software Foundation Member

[Slavka Peleva]

Congratulations, Sven! Wishing you success with the new role!

On Thu, Mar 18, 2021 at 11:49 AM David Jumani 
wrote:

> Congratulations Sven!
> 
> From: Paul Angus 
> Sent: Thursday, March 18, 2021 2:43 AM
> To: d...@cloudstack.apache.org ;
> users@cloudstack.apache.org 
> Subject: Congratulations to Sven - Apache Software Foundation Member
>
> Hi All,
>
>
>
> More great news.
>
>
>
> Please join me in congratulating Sven,  for being made a Member of the
> Apache Software Foundation.
>
>
>
> Congratulations Sven, keep up the good work!
>
>
>
> Kind regards
>
>
>
> Paul Angus
>
>
>
>
> david.jum...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

Re: Cloudstack developer training

[Slavka Peleva]

Hi Giles,
Thanks for sharing and many thanks to the people who worked on it!
ShapeBlue shared part of it with me a year and a half ago, and these
resources were very helpful for my first steps in CloudStack.

Kind regards,
Slavka

On Fri, Feb 26, 2021 at 11:14 PM Alireza Eskandari 
wrote:

> Hi Giles,
> As a CloudStack user, I spent lots of time in the code to figure out how
> different parts work and find the root cause of bugs that I face.
> I also tried to install CloudStack as a project in eclipse and run it
> directly from eclipse from some old documents.
> I have learned some courses in Java to enable myself to contribute to the
> CloudStack codebase.
> But each time I look at the code and its sub-projects, my mind is blown up!
> I thought maybe it is because I don't have any practical java development
> experience yet but a clear document about the code itself could make
> everything easier to understand.
> I appreciate your valuable work. It is something that I have looked for
> many times!
> Regards,
>
> On Fri, Feb 26, 2021 at 7:13 PM Giles Sirett 
> wrote:
>
> > Hi all
> >
> > One of the biggest challenges with Cloudstack is learning its
> architecture
> > and codebase  - its big and its complicated. Onboarding new software
> > engineers can be a daunting process.
> > For the last 2 years, we at ShapeBlue have built up a set of resources to
> > help us with onboarding on new engineers who will be working on
> Cloudstack.
> >
> > This has evolved into a self-study course that we call "hackerbook"- the
> > logic being that it's a training course that gets engineers hands-on
> > hacking in the code ASAP.  It's a mix of videos, exercises and other
> > resources.
> >
> > Today, we've opensourced this resource in order to make it available to
> > anybody who may want to learn to develop on Cloudstack.
> >
> > Feedback and improvement PRs will be warmly accepted
> >
> > Its currently sitting in a shapeblue repo, happy to move under ASF if
> > anybody thinks that's important
> >
> > https://github.com/shapeblue/hackerbook
> >
> > Happy Hacking
> >
> > Kind regards
> > Giles
> >
> >
> > giles.sir...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >
>