| 2024-02-02 22:04:05 |
trya uuum |
description |
I've tested a bit libvirt on ubuntu 22.04
In systemd unit for libivirt there is a line
Environment=LIBVIRTD_ARGS="--timeout 120"
which makes libvirtd shut down if no active requests exist for 2 minutes.
In libvirt there's a concept of storage pools. They can be set to start automatically on daemon start. It's visible in "virsh pool-list" output
$ virsh pool-list
Name State Autostart
-------------------------------------------
default active yes
When libvirt shuts down automatically and then is started afterwards, ceph-backed pools are not started automatically. This is not a huge problem -- we would just need to add "pool start" commands to our application in every place where images from the pool are used. But it breaks the existing workflow.
Overall, this bug doesn't really affect me, because I don't use ubuntu 24.04 in production. I simply wanted to give some feedback.
Thank you all for your time and work on packaging libvirt and qemu for ubuntu! |
I've tested a bit libvirt on ubuntu 24.04
In systemd unit for libivirt there is a line
Environment=LIBVIRTD_ARGS="--timeout 120"
which makes libvirtd shut down if no active requests exist for 2 minutes.
In libvirt there's a concept of storage pools. They can be set to start automatically on daemon start. It's visible in "virsh pool-list" output
$ virsh pool-list
Name State Autostart
-------------------------------------------
default active yes
When libvirt shuts down automatically and then is started afterwards, ceph-backed pools are not started automatically. This is not a huge problem -- we would just need to add "pool start" commands to our application in every place where images from the pool are used. But it breaks the existing workflow.
Overall, this bug doesn't really affect me, because I don't use ubuntu 24.04 in production. I simply wanted to give some feedback.
Thank you all for your time and work on packaging libvirt and qemu for ubuntu! |
|
