Red Hat Bugzilla – Bug 1290844
[Debian] provide libvirt >= 1.2.17 for vdsm >= 4.17.13
Last modified: 2016-12-28 10:37:33 EST
Description of problem:
Debian Jessie currently has libvirt 1.2.9.
In order to have memory hotplug working we need a newer version.
Moving to Milan since he's porting vdsm to Debian
The best way to handle this would be to coordinate with Debian Libvirt Maintainers to make an official jessie backport of libvirt. Let's see whether the overall jessie backport is worth the effort (i.e. whether there's a real demand for that from users) after I finish the Vdsm packaging for unstable.
Moving to 4.0, though I suggest closing if not handled.
oVirt 4.0 beta has been released, moving to RC milestone.
Do we want to keep monitoring our Debian support here, or switch to some other (Debian related) bug database?
Are we ever going to handle this, or should I CLOSE-DEFERRED this?
I don't think it makes sense tracking Debian packaging here. We have removed Debian packaging from Vdsm since it was completely broken. It's better to track the Debian packaging effort directly in Debian and/or on ovirt-devel mailing list. The intent-to-package bug for Vdsm in Debian is https://bugs.debian.org/668538, this is what we start with. If we manage to make a working Vdsm Debian package, its bugs should be reported to Debian BTS. So I'd suggest closing the Debian packaging bugs in Vdsm Bugzilla.