Python-virtinst tools do not work on Mageia 1, due to a incorrect patch causing python errors : + virt-install --connect=qemu:///system --network=bridge:br0 --initrd-inject=/export/fed-minimal.ks '--extra-args=ks=file:/fed-minimal.ks console=tty0 console=ttyS0,115200' --name=f15testbox --disk /var/lib/libvirt/images/f15testbox.img,size=20 --ram 2048 --vcpus=2 --check-cpu --accelerate --hvm --location= --nographics Traceback (most recent call last): File "/usr/sbin/virt-install", line 36, in <module> import virtinst File "/usr/lib/python2.7/site-packages/virtinst/__init__.py", line 32, in <module> from Guest import Guest, XenGuest File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 40, in <module> import DistroInstaller File "/usr/lib/python2.7/site-packages/virtinst/DistroInstaller.py", line 31, in <module> import OSDistro File "/usr/lib/python2.7/site-packages/virtinst/OSDistro.py", line 1019 versionfile = fetcher.acquireFile("VERSION", progresscb) The patch have been removed from the package. As the package is noarch, just a test on one arch should be sufficient. See also bug 1028. See also http://kashyapc.wordpress.com/2011/08/18/unattended-guest-install-with-a-local-kickstart/ for a quick blog post on how to use it. Advisory A patch to add the support of Mageia on python-virtinst have been found to be incorrect. This update fix the package by disabling the patch.
*** Bug 2594 has been marked as a duplicate of this bug. ***
CC: (none) => stormi
Should add a requires libvirt-utils. I can't test this on my old i586 system, as I get ERROR Host does not support virtualization type 'hvm'
CC: (none) => davidwhodgins
Why add a requires ? python-virtinst can be used on remote libvirtd so a local libvirt installation is not needed ( ie, you can run python-virtinst on i586, and do the computing on a remote system ).
When I first tried to run virt-install, it failed, as it couldn't connect to libvirtd. I had to install libvirt-utils and start the libvirtd service, before it tried to run, though it then failed due to my old cpu not supporting virtualization. I didn't realize it could connect to a libvirtd on a remote system. Thanks for the clarification.
Also, as stormi discovered, libvirtd ( and the aformentioned script ) do not work if qemu s not installed ( again, libvirt can use xen, vbox, or lxc, so there is no requires on anything ), so test if it is installed ( the error message is the same as you ). Any system less than 3/4 years old should be ok ( I run it on my 2008 macbook, for the reference ).
This took some fiddling but tested ok x86_64 using the link given. As it is noarch is this sufficient?
CC: (none) => eeeemail
(In reply to comment #6) > This took some fiddling but tested ok x86_64 using the link given. > > As it is noarch is this sufficient? Per the policy, no, but if we allow ourselves to do an exception, given that it works on x86_64 and given the nature of the patch misc has applied, I think it is safe to push it now.
While I can't actually run the program, I can confirm that it installs ok on i586, and only fails on my system due to the cpu not supporting virtualization. Can someone from the sysadmin team push the srpm python-virtinst-0.500.6-4.1.mga1.src.rpm from Core Updates Testing to Core Updates. Advisory: python-virtinst, a python module for starting Xen guest installations, in Mageia 1 contains a patch that prevents the module from running. This update fixes the package by disabling the patch.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
The RPM summary of this package in Mageia 1, "Python modules for starting Xen guest installations" is wrong (that of cauldron is better: "Python modules for starting libvirt based guest installations") This doesn't block the current update, it only changes the advisory: Advisory: In Mageia 1 python-virtinst, a collection of python modules for starting libvirt based guest installations, contains a Mageia-specific patch that prevents the module from running. This update fixes the package by disabling the patch.
update pushed.
Status: NEW => RESOLVEDCC: (none) => dmorganecResolution: (none) => FIXED