You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something to consider maybe is that mysql-connector-python-py3's deb is (currently) not supplied for trixie, so I had to grab the bookworm version; see #12252
We're a debian shop, and we want to try to stay that way
Usage of the latest debian was just part of the wider update cycle for us
We do plan to use cloudstack with debian in the future, but this depends on how well it would support debian and proxmox, which are the technologies we seem to be staying with for a while.
@ShadowJonathan i am about to push debian as our main hypervisor os, let's see how testing goes. I rendered a small testsuite which does vm lifecycles in parallel etc, i will update about the results
Debian 13 ships OpenJDK 21, i used the Adoptium OpenJDK 17 Packages. Apart from that, i was able to add the Trixie host without any further hacks or modifications. The Ubuntu installation instructions apply to Debian as well, i am currently using the shapeblue packages.
Update: this is our new main hypervisor os, if anyone wants to exchange operations experience feel free to get in touch with me
Debian 13 ships OpenJDK 21, i used the Adoptium OpenJDK 17 Packages. Apart from that, i was able to add the Trixie host without any further hacks or modifications. The Ubuntu installation instructions apply to Debian as well, i am currently using the shapeblue packages.
Update: this is our new main hypervisor os, if anyone wants to exchange operations experience feel free to get in touch with me
Hi, I am not able to get trixie as kvm hosts to work, the agent just start and crashes when I try to add as cluster host. Do you think it is due to openJDK21? I need to use OpenJDK 17?
Hi @chunkyen ! I use OpenJDK 21 on Ubuntu 24.04 on KVM hosts. I use this version because it is installed together with Linstor (hyperconvergence). I have been using it for more than a year, and up to the present moment, I have not seen any problem in the agent's operation that would be related to this.
Hi @chunkyen ! I use OpenJDK 21 on Ubuntu 24.04 on KVM hosts. I use this version because it is installed together with Linstor (hyperconvergence). I have been using it for more than a year, and up to the present moment, I have not seen any problem in the agent's operation that would be related to this.
Thank you @SviridoffA. I tried using OpenJDK21 (which was also install as part of Cloudstack Agent install since it is the default Java version in Trixie), although the install went well, trying to add this to a 4.22 management cluster will cause it to crash loop.
Maybe @jgotteswinter can share more details on how to make the CloudStack agent work in 4.22.
Cheers
Hi @chunkyen ! I use OpenJDK 21 on Ubuntu 24.04 on KVM hosts. I use this version because it is installed together with Linstor (hyperconvergence). I have been using it for more than a year, and up to the present moment, I have not seen any problem in the agent's operation that would be related to this.
Thank you @SviridoffA. I tried using OpenJDK21 (which was also install as part of Cloudstack Agent install since it is the default Java version in Trixie), although the install went well, trying to add this to a 4.22 management cluster will cause it to crash loop. Maybe @jgotteswinter can share more details on how to make the CloudStack agent work in 4.22. Cheers
As i said, i am using Adoptiums OpenJDK 17 Packages on the compute nodes. Works fine for me. I did not yet migrate the management servers to debian.
Hi, even if I use OpenJDK17, the result is the same, when adding trixie KVM to management server, it alwyas end with " Unable to create attache for agent: Seq 0-0:" on the management server side, and the agent reply is missing info when replying to server "[cloud.agent.Agent] (Agent-Handler-2:[]) (logid:) Process agent startup answer, agent [id: 0, uuid: , name: ] connected to the server"
Hi, even if I use OpenJDK17, the result is the same, when adding trixie KVM to management server, it alwyas end with " Unable to create attache for agent: Seq 0-0:" on the management server side, and the agent reply is missing info when replying to server "[cloud.agent.Agent] (Agent-Handler-2:[]) (logid:) Process agent startup answer, agent [id: 0, uuid: , name: ] connected to the server"
agent.properties after trying to add host as follow:
Note the missing LibvirtComputingResource.name and LibvirtComputingResource.uuid
keystore.passphrase redacted
Additionally, the add host failure notification pop up with the following message:
"Unable to add the host: Cannot find the server resources at http://<server.fq.dn>"
@weizhouapache I tested the current 4.22 branch (4.22.2.0-SNAPSHOT) end to end on clean Debian 13.6 installs:
management server with the stock MariaDB 11.8 and OpenJDK 21
two KVM hosts with the stock libvirt 11.3, QEMU 10.0 and OpenJDK 21
NFS primary and secondary storage, advanced zone, 4.22.0 systemvm template
The packages were built from the unmodified 4.22 branch on Debian 13 with JDK 21 (tests skipped).
Works
cloudstack-setup-databases on MariaDB 11.8, cloudstack-setup-management, management server and usage server on Java 21
cloudstack-agent installs with no extra steps, hosts added and Up
SSVM and CPVM up, template registration, VM deploy, stop/start/reboot, console
volume attach/detach, volume snapshot, volume and template from snapshot
VM snapshot with memory, revert and delete
isolated network with VR, public IP, firewall and port forwarding
VPC with a tier, VPC without tiers
live migration and host maintenance (guest VMs, VR and CPVM evacuated), agent and management server restart
Needs fixing
MySQL connector. cloudstack-management depends on python3-mysql.connector | mysql-connector-python-py3 and neither can be installed on Debian 13. The step from cloudstack-documentation#610 does not help here anymore: the MySQL trixie repo has no Python connector, and the bookworm mysql-connector-python-py3 8.4.0 package depends on python3-distutils, which Debian 13 dropped. The only way I found was pip install --break-system-packages mysql-connector-python==8.4.0 plus a dummy package to satisfy the dependency. The connector is only used by python/lib/cloudutils/db.py, cloud-update-xenserver-licenses and scripts/util/migrate-dynamicroles.py, and Debian 13 ships python3-pymysql and python3-mysqldb. Would moving these scripts to one of those be acceptable?
Marvin on 4.22 cannot be installed on Python 3.13 because PyCrypt does not build. marvin: use pycryptodome instead of PyCrypt #13594 changed it to pycryptodome on main only. Could it be backported to 4.22?
I can help with PRs for 1 and 4 and with the compatibility matrix docs once there is agreement on the approach.
@weizhouapache I tested the current 4.22 branch (4.22.2.0-SNAPSHOT) end to end on clean Debian 13.6 installs:
management server with the stock MariaDB 11.8 and OpenJDK 21
two KVM hosts with the stock libvirt 11.3, QEMU 10.0 and OpenJDK 21
NFS primary and secondary storage, advanced zone, 4.22.0 systemvm template
The packages were built from the unmodified 4.22 branch on Debian 13 with JDK 21 (tests skipped).
Works
cloudstack-setup-databases on MariaDB 11.8, cloudstack-setup-management, management server and usage server on Java 21
cloudstack-agent installs with no extra steps, hosts added and Up
SSVM and CPVM up, template registration, VM deploy, stop/start/reboot, console
volume attach/detach, volume snapshot, volume and template from snapshot
VM snapshot with memory, revert and delete
isolated network with VR, public IP, firewall and port forwarding
VPC with a tier, VPC without tiers
live migration and host maintenance (guest VMs, VR and CPVM evacuated), agent and management server restart
Needs fixing
MySQL connector. cloudstack-management depends on python3-mysql.connector | mysql-connector-python-py3 and neither can be installed on Debian 13. The step from cloudstack-documentation#610 does not help here anymore: the MySQL trixie repo has no Python connector, and the bookworm mysql-connector-python-py3 8.4.0 package depends on python3-distutils, which Debian 13 dropped. The only way I found was pip install --break-system-packages mysql-connector-python==8.4.0 plus a dummy package to satisfy the dependency. The connector is only used by python/lib/cloudutils/db.py, cloud-update-xenserver-licenses and scripts/util/migrate-dynamicroles.py, and Debian 13 ships python3-pymysql and python3-mysqldb. Would moving these scripts to one of those be acceptable?
Marvin on 4.22 cannot be installed on Python 3.13 because PyCrypt does not build. marvin: use pycryptodome instead of PyCrypt #13594 changed it to pycryptodome on main only. Could it be backported to 4.22?
I can help with PRs for 1 and 4 and with the compatibility matrix docs once there is agreement on the approach.
@nagaboinaramgopal
debian 13 is actually working well with cloudstack 4.23.0
please refer to #13980 (comment)
(marvin node is oraclelinux 9, not debian 13)
@weizhouapache I tested the current 4.22 branch (4.22.2.0-SNAPSHOT) end to end on clean Debian 13.6 installs:
management server with the stock MariaDB 11.8 and OpenJDK 21
two KVM hosts with the stock libvirt 11.3, QEMU 10.0 and OpenJDK 21
NFS primary and secondary storage, advanced zone, 4.22.0 systemvm template
The packages were built from the unmodified 4.22 branch on Debian 13 with JDK 21 (tests skipped). Works
cloudstack-setup-databases on MariaDB 11.8, cloudstack-setup-management, management server and usage server on Java 21
cloudstack-agent installs with no extra steps, hosts added and Up
SSVM and CPVM up, template registration, VM deploy, stop/start/reboot, console
volume attach/detach, volume snapshot, volume and template from snapshot
VM snapshot with memory, revert and delete
isolated network with VR, public IP, firewall and port forwarding
VPC with a tier, VPC without tiers
live migration and host maintenance (guest VMs, VR and CPVM evacuated), agent and management server restart
Needs fixing
MySQL connector. cloudstack-management depends on python3-mysql.connector | mysql-connector-python-py3 and neither can be installed on Debian 13. The step from cloudstack-documentation#610 does not help here anymore: the MySQL trixie repo has no Python connector, and the bookworm mysql-connector-python-py3 8.4.0 package depends on python3-distutils, which Debian 13 dropped. The only way I found was pip install --break-system-packages mysql-connector-python==8.4.0 plus a dummy package to satisfy the dependency. The connector is only used by python/lib/cloudutils/db.py, cloud-update-xenserver-licenses and scripts/util/migrate-dynamicroles.py, and Debian 13 ships python3-pymysql and python3-mysqldb. Would moving these scripts to one of those be acceptable?
Marvin on 4.22 cannot be installed on Python 3.13 because PyCrypt does not build. marvin: use pycryptodome instead of PyCrypt #13594 changed it to pycryptodome on main only. Could it be backported to 4.22?
I can help with PRs for 1 and 4 and with the compatibility matrix docs once there is agreement on the approach.
@nagaboinaramgopal debian 13 is actually working well with cloudstack 4.23.0 please refer to #13980 (comment) (marvin node is oraclelinux 9, not debian 13)
Activity
ShadowJonathan commentedon Jan 5, 2026
Something to consider maybe is that
mysql-connector-python-py3's deb is (currently) not supplied for trixie, so I had to grab the bookworm version; see #12252The file to watch is https://repo.mysql.com/apt/debian/dists/trixie/mysql-tools/binary-amd64/Packages; last updated 27 oct 2025 (according to the index)
jgotteswinter commentedon Jan 7, 2026
How much testing has been done with trixie so far? Any known issues apart the mysql-connector-python-py3 package?
I added it to our bootserver today, testing with acs will start tomorrow.
DaanHoogland commentedon Jan 8, 2026
@jgotteswinter , I don’t think anybody but @ShadowJonathan is busy with this yet.
ShadowJonathan commentedon Jan 8, 2026
And my testing/usage of it is only because;
We do plan to use cloudstack with debian in the future, but this depends on how well it would support debian and proxmox, which are the technologies we seem to be staying with for a while.
jgotteswinter commentedon Jan 8, 2026
@ShadowJonathan i am about to push debian as our main hypervisor os, let's see how testing goes. I rendered a small testsuite which does vm lifecycles in parallel etc, i will update about the results
jgotteswinter commentedon Jan 8, 2026
Debian 13 ships OpenJDK 21, i used the Adoptium OpenJDK 17 Packages. Apart from that, i was able to add the Trixie host without any further hacks or modifications. The Ubuntu installation instructions apply to Debian as well, i am currently using the shapeblue packages.
Update: this is our new main hypervisor os, if anyone wants to exchange operations experience feel free to get in touch with me
chunkyen commentedon Jan 26, 2026
Hi, I am not able to get trixie as kvm hosts to work, the agent just start and crashes when I try to add as cluster host. Do you think it is due to openJDK21? I need to use OpenJDK 17?
SviridoffA commentedon Jan 26, 2026
Hi @chunkyen ! I use OpenJDK 21 on Ubuntu 24.04 on KVM hosts. I use this version because it is installed together with Linstor (hyperconvergence). I have been using it for more than a year, and up to the present moment, I have not seen any problem in the agent's operation that would be related to this.
chunkyen commentedon Jan 27, 2026
Thank you @SviridoffA. I tried using OpenJDK21 (which was also install as part of Cloudstack Agent install since it is the default Java version in Trixie), although the install went well, trying to add this to a 4.22 management cluster will cause it to crash loop.
Maybe @jgotteswinter can share more details on how to make the CloudStack agent work in 4.22.
Cheers
jgotteswinter commentedon Jan 27, 2026
As i said, i am using Adoptiums OpenJDK 17 Packages on the compute nodes. Works fine for me. I did not yet migrate the management servers to debian.
chunkyen commentedon Jan 30, 2026
Hi, even if I use OpenJDK17, the result is the same, when adding trixie KVM to management server, it alwyas end with " Unable to create attache for agent: Seq 0-0:" on the management server side, and the agent reply is missing info when replying to server "[cloud.agent.Agent] (Agent-Handler-2:[]) (logid:) Process agent startup answer, agent [id: 0, uuid: , name: ] connected to the server"
jgotteswinter commentedon Jan 30, 2026
can you show your agent properties?
chunkyen commentedon Feb 1, 2026
agent.properties after trying to add host as follow:
Note the missing LibvirtComputingResource.name and LibvirtComputingResource.uuid
keystore.passphrase redacted
Additionally, the add host failure notification pop up with the following message:
"Unable to add the host: Cannot find the server resources at http://<server.fq.dn>"
4 remaining items
rootnomad commentedon Sep 11, 2026
@weizhouapache I tested the current 4.22 branch (4.22.2.0-SNAPSHOT) end to end on clean Debian 13.6 installs:
The packages were built from the unmodified 4.22 branch on Debian 13 with JDK 21 (tests skipped).
Works
Needs fixing
MySQL connector. cloudstack-management depends on
python3-mysql.connector | mysql-connector-python-py3and neither can be installed on Debian 13. The step from cloudstack-documentation#610 does not help here anymore: the MySQL trixie repo has no Python connector, and the bookwormmysql-connector-python-py38.4.0 package depends onpython3-distutils, which Debian 13 dropped. The only way I found waspip install --break-system-packages mysql-connector-python==8.4.0plus a dummy package to satisfy the dependency. The connector is only used bypython/lib/cloudutils/db.py,cloud-update-xenserver-licensesandscripts/util/migrate-dynamicroles.py, and Debian 13 shipspython3-pymysqlandpython3-mysqldb. Would moving these scripts to one of those be acceptable?Live migration fails out of the box with
unable to connect to server at <host>:16509: Connection refused, because libvirtd does not listen. With the one line from kvm: set LIBVIRTD_ARGS so libvirtd listens on Debian and Ubuntu hosts #14153 it migrates in both directions and host maintenance works.Building the debs on Debian 13:
dpkg-checkbuilddepsfails on the JDK line (Debian 13 only has openjdk-21, and openjdk-21-jdk does not provide java17-sdk) and on the MySQL connector.ERR_OSSL_EVP_UNSUPPORTED(webpack 4). It works withNODE_OPTIONS=--openssl-legacy-provider.marvin-<version>.tar.gz, sodebian/rulesstops atcp Marvin-*.tar.gz. Packaging: accept normalized Marvin archive names #13793 fixes this; I left the test results there.Marvin on 4.22 cannot be installed on Python 3.13 because PyCrypt does not build. marvin: use pycryptodome instead of PyCrypt #13594 changed it to pycryptodome on main only. Could it be backported to 4.22?
I can help with PRs for 1 and 4 and with the compatibility matrix docs once there is agreement on the approach.
weizhouapache commentedon Sep 12, 2026
@nagaboinaramgopal
debian 13 is actually working well with cloudstack 4.23.0
please refer to #13980 (comment)
(marvin node is oraclelinux 9, not debian 13)
for the mysql python connector, please refer to apache/cloudstack-documentation#678
rootnomad commentedon Sep 14, 2026
Thanks @weizhouapache , good to know it already works with 4.23.0, Thanks