On Sat, Jul 10, 2021 at 6:55 PM <branimirp@gmail.com> wrote:
Hi Nir
Thank you for your explanation.
Can I ask you if you can explain this a bit further? I performed and experiment and installed ovirt + a hypervisor on 2 VMs (on the hypervisor VM I enabled nested virtualization) - both based on Rocky Linux following the official oVirt instructions for 4.4.7. No problems there - I also created a vm and successfully ran it.
How did you install ovirt 4.4.7, when we require qemu-kvm >= 5.2.0? I see this in vdsm.spec: %if 0%{?rhel} >= 8 %if 0%{?centos} # 4.4 Advanced virt stream on CentOS 8 Requires: qemu-kvm >= 15:5.2.0 %else # 4.4, AV 8.4 - https://bugzilla.redhat.com/1948532 Requires: qemu-kvm >= 15:5.2.0-15.module+el8.4.0+10650+50781ca0 %endif #centos %endif #rhel Maybe you install an old rc version, before we updated the requirement?
Based on this, Rocky - at the moment - replaces CentOS8 just nicely. And while libvirt installed is libvirt-7.0.0-14.1.el8.x86_64 and comes from CentOS8 advanced virt repo, qemu on the hypervisor machine is qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e.x86_64 not 5.2.0 and comes from Rocky's repos. Does it mean that, once CentOS8 reaches EOL at the end of this year, we should only hope that Rocky releases libvirt-7.0.0 in their advanced-virt repo?
A snippet from oVirt GUI - hypervisor properties:
OS Version: RHEL - 8.4 - 30.el8 OS Description: Rocky Linux 8.4 (Green Obsidian) Kernel Version: 4.18.0 - 305.7.1.el8_4.x86_64 KVM Version: 4.2.0 - 48.module+el8.4.0+534+4680a14e LIBVIRT Version: libvirt-7.0.0-14.1.el8
This version is good enough for ovirt 4.4.7.
and confirmation:
# rpm -q qemu-kvm qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e.x86_64
This version does not support features expected by vdsm. I wonder how you have new libvirt with old qemu. - qemu-img convert does not support the --bitmaps option, used to copy bitmaps created during incremental backup when moving disks. - qemu-img bitmap sub command is not available. use to add, remove and merge bitmaps in various flows - qemu-nbd does not support --allocation-depth option. Use to report holes in qcow2 images. - there may be other missing features that libvirt 7.0.0 depends on You may have luck with flows that do not use the missing features. Nir