[Bug 1001446] New: virt-manager does not work on leap 42.2
http://bugzilla.suse.com/show_bug.cgi?id=1001446 Bug ID: 1001446 Summary: virt-manager does not work on leap 42.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: meissner@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I updated from 13.2 to Leap 42.2 Beta ... I can connet virt.manager to libvirtd, but on starting the VM I get: Fehler beim Starten der Domain: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1404, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1035, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c1
--- Comment #1 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c2
James Fehlig
i enabled virtlogd.socket and started it, then it worked.
not sure if that should be a dependency of virt-manager.service or similar
More like the libvirtd unit. This was fixed upstream by http://libvirt.org/git/?p=libvirt.git;a=commit;h=839a060890d8b2408c0ea20e3c5... But that commit wasn't quite right and further refined by http://libvirt.org/git/?p=libvirt.git;a=commit;h=f496ce1df35df7498bd3d9d7e11... In theory this bug affects SLE12 SP2 as well, since 42.2 packages are copied from there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c3
James Fehlig
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c4
Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c5
--- Comment #5 from James Fehlig
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c6
--- Comment #6 from Ludwig Nussel
Do you think this bug has sufficient priority to include the fixes for SP2 GMC? If so, I can submit and the fixes will be propogated to 42.2. If not, a 42.2 fix will have to wait until the first SP2 maintenance cycle for libvirt.
Please submit anyways. If it gets rejected for GA we can still reroute it to 42.2 directly. Just let me know if you need the fast path. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1001446
http://bugzilla.suse.com/show_bug.cgi?id=1001446#c7
James Fehlig
Please submit anyways. If it gets rejected for GA we can still reroute it to 42.2 directly. Just let me know if you need the fast path.
Ok, submitted - SR#121664. Closing the bug for now. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com