Description of problem: libvirt cannot handle virtual network without netcf support, so when you create a VM, with virt-manager ie, you cannot finalize the creation because of network component, it says that HAL is needed. Version-Release number of selected component (if applicable): libvirt-1.0.2-7.1.mga3.src.rpm How reproducible: 1 - Create a VM with virt-manager 2 - At the last step, open advanced parameters and see the warning about HAL. So libvirt-1.0.2-8.1.mga3.src.rpm fixes that, you can create a VM to check. It's critical because end-users cannot use KVM into Mageia 3 because of that. Reproducible: Steps to Reproduce:
So libvirt-1.0.2-8.1.mga3.src.rpm is in updates/testing for now, waiting for QA testers :)
Here's the commit BTW http://svnweb.mageia.org/packages/updates/3/libvirt/current/SPECS/libvirt.spec?r1=438215&r2=438214&pathrev=438215
For my test: All is OK, vm is correctly created, and as the ip I gave it during the installation of the OS. On an i586 mageia 3
Reproduced, the HAL error is seen when hovering the mouse over the yellow warning triangle. Could you list rpm's please Sandro so it's clear what to update. Thanks.
Whiteboard: (none) => has_procedure mga3-32-ok
Of course :) SRPM: libvirt-1.0.2-8.1.mga3.src.rpm RPMs: mageia/workspace/3/libvirt/RPMS âââ i586 âââ libvirt0-1.0.2-8.1.mga3.i586.rpm âââ libvirt-debuginfo-1.0.2-8.1.mga3.i586.rpm âââ libvirt-devel-1.0.2-8.1.mga3.i586.rpm âââ libvirt-utils-1.0.2-8.1.mga3.i586.rpm âââ python-libvirt-1.0.2-8.1.mga3.i586.rpm
Thanks Sandro. Still seeing the error here, do you have to reboot or log out/in ?
oops, yes, you have to restart systemd libvirt services. libvirt and libvirt-guest
I tried those and still seeing the error :\
I still don't see it, it's annoying. Did you test on a mga3 i586?
No, i was testing mga3 64
So please try mga3 i586. I have no hardware to test 64b..
Hmm so it seems this was pushed already. The previous CVE update was still in Updates Testing when this was built :\
The bug still remains though on 32bit too, sorry Sandro. I've rebooted the machine to make sure.
Speaking with Sandro on IRC, the update allows network connection but does not remove the yellow warning triangle during configuration. Confirmed this mga3 64 so validating this update, even though it's already been pushed. Closing the bug.
Keywords: (none) => validated_updateStatus: NEW => RESOLVEDResolution: (none) => FIXEDWhiteboard: has_procedure mga3-32-ok => has_procedure mga3-32-ok mga3-64-okCC: (none) => sysadmin-bugs