Engage. Your Community

Korora 25 and Virt-Manager unable to create new virtual machine

Hello guys, I have installed virt-manager using the following commands : dnf -y install qemu-kvm libvirt virt-install bridge-utils virt-manager

The problem that I am encountering, is whenever I try to create a new VM, I am getting an error message: Error launching manager: Constructor returned NULL.

"Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 903, in _do_show_create
    self._get_create_dialog().show(src.topwin, uri)
  File "/usr/share/virt-manager/virtManager/create.py", line 200, in show
    self._reset_state(uri)
  File "/usr/share/virt-manager/virtManager/create.py", line 367, in _reset_state
    self._undo_finish_cursor(self.topwin)
  File "/usr/share/virt-manager/virtManager/create.py", line 2178, in _undo_finish_cursor
    Gdk.Cursor.new(Gdk.CursorType.TOP_LEFT_ARROW))
TypeError: constructor returned NULL"

I restarted my machine, then the error gone but when I tried to create another VM, the same error message appear. I ran journalctl -xe to see what's going on and here's what I found:

"Jan 05 23:40:09 skawt.linux nautilus-autostart.desktop[1799]: Could not connect to unix socket. [Errno 2] No such file or directory
Jan 05 23:40:09 skawt.linux nautilus-autostart.desktop[1799]: Socket: /run/user/1000/ownCloud/socket <=> /ownCloud/socket"

Any suggestions will be highly appreciated.

I've tested on my system and can't reproduce your problem. I usually install virt-manager with dnf install kvm virt-manager libvirt if that helps. I only had a Korora iso to test with.

What operating system were you trying to install? Did you select the correct system in virt-manager? I find it is better to turn off auto-detect and set it myself. Is there plenty of disk space on the target drive for the VM?

By the way I edited your post by putting the quoted output in a code box. That makes it much easier to read. You can see the formatting options by clicking on the question mark above the reply box.

Hi Ozjd, thanks for the suggestion. I tried that way but I am still getting the same error message. I was able to install RHEL 7 on the VM but when I tried to create another VM, the same error message popped up.

I usually install virt-manager via:

CODE:


sudo dnf install @virtualization

sudo systemctl start libvirtd

sudo systemctl enable libvirtd


Ensure your system is up to date and all of the necessary services are enabled / started. Also you may need to enable some options in the BIOS for virtualization.

I'd refer to this for troubleshooting virtualization problems: https://fedoraproject.org/wiki/How_to_debug_Virtualization_problems

^ Thanks, I will check that page. I am able to create some VMs one session at a time. If I want to add another, I have to logout/restart my machine before I can add a new one.

How many cores does your CPU have? if you're giving out more cores than your CPU can offer you're going to get errors.

I have 4 cores on my cpu, 8GB RAM.

I tried plugging in my bootable flash drive and try virt-manager on Live version. I am not getting any errors there. There's something in the socket when I started the service of libvirtd which might be connected to this error

"Jan 05 23:40:09 skawt.linux nautilus-autostart.desktop[1799]: Could not connect to unix socket. [Errno 2] No such file or directory
Jan 05 23:40:09 skawt.linux nautilus-autostart.desktop[1799]: Socket: /run/user/1000/ownCloud/socket <=> /ownCloud/socket

Probably I messed with reinstalling the packages. I tried it several times via dnf remove and dnf install. I'll dig down and see if the problem will be fixed.

Please Log In to participate with the community.