It worked when I tested in Ubuntu with the following qemu/libvirt:
~# qemu-system-x86_64 --version
QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu6~ppa0)
~# libvirtd --version
libvirtd (libvirt) 6.6.0
I will check if there has been any regressions in qemu.
Maybe the best would be to extrac
Hello all,
If you did not get the chance to join the CloudStack Collaboration Conference
live, I am happy to share that we have started uploading the event videos
online.
All the recordings from the event will be uploaded in the official ACS YouTube
Channel here:
https://www.youtube.com/watch?
Hi Seth,
The endpointe.url is only required by the cluster autoscaler and CloudStack
Kubernetes provider.
The cluster should still come up successfully even if the value is incorrect.
It just means that those two features will not work
From: Rohit Yadav
Sent: Tu
Hi Seth,
It depends what failures you're getting, if it's related to endpointe pl fix
the global setting with your API URL (for ex. I'm using
http://192.168.1.10:8080/client/api). If you're using a domain name, ensure
that's globally resolvable or at least by the DNS server configured for your
tanks Jorge,
Can you describe this in a github issue, please?
On Mon, Nov 22, 2021 at 7:53 PM Jorge Luiz Correa
wrote:
> Same difficulty here. The way it worked was defining the truststore
> globally. Just after that I defined the ldap configuration inside a domain.
>
> Using API:
>
> cmk -p use
HI all!
CS 4.16 + XCP-NG 8.2
Do new versions (4.15/4.16) support S3 Secondary Storage?
When I try to add new SS I see 3 available types - NFS, SMB/CIFS, Swift
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются
конфиденциальными и предназначены исключительно для использова
Hi Wei,
Unfortunately, neither systemvm, nor any other vm, is starting due to the
message: libvirt.LibvirtException: unsupported configuration: io uring is not
supported by this QEMU binary
In one LAB I have a custom kernel: 5.4.129-1.el8.elrepo.x86_64 and libvirtd
(libvirt) 7.6.0 with qemu 6.
Good to know you have solved the problem. Thanks for the update.
-Wei
On Mon, 22 Nov 2021 at 20:44, Seth Lyons wrote:
> I resolved this myself by turning off the firewall in CentOS and just
> using Ip tables
>
>
>
> Seth
>
> -Original Message-
> From: Seth Lyons
> Sent: Friday, Novembe
Hi Piotr,
Could you please check if all your management servers, cloudstack agents,
and system vms (SSVM/CPVM) are running with 4.16.0.0 ?
It's mostly like your SSVM is not 4.16.0.0.
When processing HandleConfigDriveIsoCommand, SSVM with the old version
returns Answer (not HandleConfigDriveIsoAnsw
