Cloudstack DB using 3 Node Galrea Cluster.

Hi Community, I need some suggestions on using 3 node Mariadb *Galera Cluster or percona xtradb* for Cloudstack Databases. In My setup the Databases are behind a LB and write happens only to a single node With new Cloudstack 4.18.1 install initial database migration is always failing because

Re: [D] EVPN-VXLAN - IPv6 via SLAAC [cloudstack]

GitHub user tobzsc added a comment to the discussion: EVPN-VXLAN - IPv6 via SLAAC Finally, we found the problem which is related to VXLAN flags. When IPv6 multicast packets enter our fabric the VXLAN packet somehow gets the flags `0x0a00` instead of `0x0800`, which is being ignored by the

Re: Experience on GPU Support?

Another way to deal with it is to use KVM agent hooks (this is my code implemented specifically to deal with GPUs and VM-dedicated drives): https://github.com/apache/cloudstack/blob/8f6721ed4c4e1b31081a951c62ffbe5331cf16d4/agent/conf/agent.properties#L123 You can implement the logic in Groovy to

Re: KVM VM consoles connection timing out due to authentication failure

Hi Kapil, If you run CloudStack in FIPS-mode, it does not work for now. According to https://qemu-project.gitlab.io/qemu/system/vnc-security.html#with-passwords Password authentication is not supported when operating in FIPS 140-2 compliance mode as it requires the use of the DES cipher.

Re: Experience on GPU Support?

Another way to deal with it is to use KVM agent hooks: https://github.com/apache/cloudstack/blob/8f6721ed4c4e1b31081a951c62ffbe5331cf16d4/agent/conf/agent.properties#L123 You can implement the logic in Groovy to modify XML during the start to support extra devices out of CloudStack management.

Re: Experience on GPU Support?

Hi Bryan! We are using here but in a different way, customized for our environment and using how it is possible the features of CloudStack. In documentation we can see support for some GPU models a little bit old today. We are using pci passthrough. All hosts with GPU are configured to boot with

RE: VMware Import Timeout

That setting is currently set to 8 hours, but I agree, that is for the conversion process. I can connect to vCenter from the management server. Nothing is being blocked there. In the management server logs I can see each VM, disk and networking information being pulled one at a time. The

Re: VMware Import Timeout

I think the setting you tried to change is convert.vmware.instance.to.kvm.timeout, but that has to do with the conversion process itself. If you try with telnet or curl from the shell of the Cloudstack management server, can you reach the VCenter? On 2024-02-22 15:35, Kevin Seales wrote: We

Re: CKS Storage Provisioner Info

Hi Community/Vivek, I created a discussion form on github discussion. Kindly check the information at https://github.com/apache/cloudstack/issues/8695 Thanks and Regards, Bharat Saini [signature_2677501444] From: Vivek Kumar Date: Friday, 23 February 2024 at 12:50 PM To:

Re: [D] Changing compute offering / scaling VM and root disk [cloudstack]

GitHub user NuxRo added a comment to the discussion: Changing compute offering / scaling VM and root disk @DaanHoogland perhaps `resizeVolume` is the culprit here. GitHub link: https://github.com/apache/cloudstack/discussions/8578#discussioncomment-8565785 This is an automatically sent