[virt-tools-list] Virtual Machine Manager UI not launching on CentOS 7

Aravind Kamble arvind.kamble at gmail.com
Fri Sep 6 06:10:09 UTC 2019


I was able to fix this problem by deleting the folder
/usr/share/virt-manager and then reinstalling virt-manager. Now I am able
to launch virt-manager and work with it.

Thanks for help

On Fri, Sep 6, 2019 at 11:11 AM Aravind Kamble <arvind.kamble at gmail.com>
wrote:

> Hi Pavel,
>
> Thanks for the help. I re-installed virt-manager just as you suggested. It
> got installed. But when I try to launch it I am getting following error
>
> Error starting Virtual Machine Manager: cannot import name vmmDetails
>
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virt-manager", line 291, in <module>
>     main()
>   File "/usr/share/virt-manager/virt-
> manager", line 239, in main
>     from virtManager.engine import vmmEngine
>   File "/usr/share/virt-manager/virtManager/engine.py", line 41, in
> <module>
>     from .details import vmmDetails
> ImportError: cannot import name vmmDetails
>
> Can you please help me fixing this?
>
>
> Thanks,
> Aravind
>
> On Thu, Sep 5, 2019 at 7:18 PM Pavel Hrdina <phrdina at redhat.com> wrote:
>
>> On Thu, Sep 05, 2019 at 04:53:23PM +0530, Aravind Kamble wrote:
>> > Hi All,
>>
>> Hi,
>>
>> >  I am a new user of virt-manager. I installed Virtual Machine Manager
>> > (1.5.0-1.el7)on CentOS 7 machine. I was able to launch the UI and work
>> with
>> > it properly.
>> >  I saw latest version of virt-manager 2.2.1 on the site
>> > https://virt-manager.org/ . I tried to install it by downloading from
>> >
>> https://virt-manager.org/download/sources/virt-manager/virt-manager-2.2.1.tar.gz
>> >  I unzipped the file and executed the command "python3.6 setup.py
>> install".
>> > It tried installing but exited out after printing the message "running
>> > install_egg_info". Please find the full output attached with this mail.
>>
>> My first future advice would be never install software into your OS in
>> any way than distribution packager, in CentOS case yum/rpm.  It is not
>> trivial to remove all the files installed by make install or setup.py
>> install as the files are not tracked by anything.
>>
>> >  After this when I tried to launch Virtual Machine Manager from
>> > Applications->System Tools-->Virtual Machine Manager, I don't see it
>> > launched.
>> >  If I try to launch it via command line I get the following
>> >
>> >
>> > [root at Mordor aravind]# virt-manager
>> > Traceback (most recent call last):
>> >   File "/usr/share/virt-manager/virt-manager", line 19, in <module>
>> >     from virtinst import BuildConfig
>> >   File "/usr/share/virt-manager/virtinst/__init__.py", line 42, in
>> <module>
>> >     _set_libvirt_error_handler()
>> >   File "/usr/share/virt-manager/virtinst/__init__.py", line 32, in
>> > _set_libvirt_error_handler
>> >     import libvirt
>> > ModuleNotFoundError: No module named 'libvirt'
>> >
>> >
>> > I do have libvirt installed.
>>
>> This means that there is missing python libvirt module.  There is only
>> libvirt-python package which provides only python 2.7 files and I
>> checked that there is no libvirt-python3.6 nor python3.6-libvirt in EPEL
>> so you would have to build it by yourself.
>>
>> virt-manager-1.5.0 is python 2 only and since virt-manager-2.0 we
>> switched to python3 only.
>>
>> > [root at Mordor aravind]# rpm -qa | grep libvirt
>> > libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-config-network-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.12.x86_64
>> > libvirt-gobject-1.0.0-1.el7.x86_64
>> > libvirt-daemon-driver-qemu-4.5.0-10.el7_6.12.x86_64
>> > libvirt-client-4.5.0-10.el7_6.12.x86_64
>> > libvirt-glib-1.0.0-1.el7.x86_64
>> > libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.12.x86_64
>> > libvirt-gconfig-1.0.0-1.el7.x86_64
>> > libvirt-daemon-driver-lxc-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-secret-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.12.x86_64
>> > libvirt-bash-completion-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-interface-4.5.0-10.el7_6.12.x86_64
>> > libvirt-python-4.5.0-1.el7.x86_64
>> > libvirt-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-network-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-4.5.0-10.el7_6.12.x86_64
>> > libvirt-libs-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.12.x86_64
>> > libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.12.x86_64
>> >
>> > Please help me restoring the working version of Virtual Machine or
>> making
>> > this new version work.
>>
>> To make the new virt-manager work you would have to build libvirt-python
>> bindings for python3.6 by yourself and install it into your system which
>> I would not recommend.
>>
>> To fix your old virt-manager you can try:
>>
>>     yum reinstall virt-install virt-manager virt-manager-common
>>
>> which should replace all required files to fix the distribution version.
>>
>> Pavel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20190906/c06179dd/attachment.htm>


More information about the virt-tools-list mailing list