|
Bugzilla – Full Text Bug Listing |
| Summary: | libvirt : Virtual Manager : Unable to connect to qemu/kvm | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | John Shand <jshand2013> |
| Component: | Virtualization:Tools | Assignee: | virt-bugs list <virt-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | guillaume.gardet, jfehlig, jshand2013, oliver, raija.ruuska |
| Version: | Current | Flags: | jfehlig:
needinfo?
(jshand2013) |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
all services on machine
journalctl log 1 journalctl log 2 journalctl log 3 y2logs just in case system unit as at 20-06-23 virsh connection log OK and not OK cases log |
||
|
Description
John Shand
2023-06-17 20:44:44 UTC
Created attachment 867654 [details]
all services on machine
Created attachment 867655 [details]
journalctl log 1
Created attachment 867656 [details]
journalctl log 2
Created attachment 867657 [details]
journalctl log 3
Created attachment 867658 [details]
y2logs just in case
Operating System: openSUSE Tumbleweed 20230616 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 7.2 GiB of RAM Graphics Processor: AMD Radeon R5 Graphics Manufacturer: Acer Product Name: Aspire A315-21G System Version: V1.12 I have the same problem. I noticed that after the shutdown reset, qemu/kvm works once, but after that it doesn't work anymore. Reboot doesn't help with this. Maybe something is left undone? This problem came after the update below. Operating System: openSUSE Tumbleweed 20230616 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 Processors: 16 x AMD Ryzen 9 5900HX with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: MINIPC PN52 this issue seems fixed in this version of tumbleweed: Operating System: openSUSE Tumbleweed 20230617 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 7.2 GiB of RAM Graphics Processor: AMD Radeon R5 Graphics Manufacturer: Acer Product Name: Aspire A315-21G System Version: V1.12 Should this be closed now? Even the same programs do not work on my computer. What additional information would you like? (In reply to John Shand from comment #8) > this issue seems fixed in this version of tumbleweed: > > Operating System: openSUSE Tumbleweed 20230617 > KDE Plasma Version: 5.27.5 > KDE Frameworks Version: 5.107.0 > Qt Version: 5.15.10 > Kernel Version: 6.3.7-1-default (64-bit) > Graphics Platform: X11 > Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G > Memory: 7.2 GiB of RAM > Graphics Processor: AMD Radeon R5 Graphics > Manufacturer: Acer > Product Name: Aspire A315-21G > System Version: V1.12 > > Should this be closed now? Forget this message. i was wrong. it allowed me to start kvm/qemu once after a reboot. when i shutdown and started computer gain, it wasn't working Created attachment 867682 [details]
system unit as at 20-06-23
For this release:
Operating System: openSUSE Tumbleweed 20230617
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.7-1-default (64-bit)
Graphics Platform: X11
Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G
Memory: 7.2 GiB of RAM
Graphics Processor: AMD Radeon R5 Graphics
Manufacturer: Acer
Product Name: Aspire A315-21G
System Version: V1.12
(In reply to John Shand from comment #11) > Created attachment 867682 [details] > system unit as at 20-06-23 From this output, at the system level I see you have modular daemons (virtqemud, virtstoraged, virtneworkd, etc) enabled and libvirtd disabled. That's fine and the preferred Tumbleweed setup these days. How are you connecting with virt-manager? Are you running it as your user but connecting to qemu:///system? Or are you connecting to the session daemons? For more info about modular vs monolithic daemons and system vs session operating modes see https://libvirt.org/daemons.html Using the system mode, are you able to connect with virsh? E.g. 'virsh -c qemu:///system list --all'? If so, does 'virsh -c qemu:///system net-list --all' work? Created attachment 867703 [details]
virsh connection log
with my normal user account i have added the user to the libvirt user/group. this usually works I usually use qemu/kvm via virt-manager with my own (raija) username, but it doesn't work now. raija@kone1:~> raija@kone1:~> virsh -c qemu:///system list --all ^C raija@kone1:~> sudo virsh -c qemu:///system list --all ^C raija@kone1:~> virt-manager raija@kone1:~> (virt-manager:23131): dbind-WARNING **: 03:15:20.314: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ^C raija@kone1:~> sudo virt-manager raija@kone1:~> (virt-manager:23160): Gtk-WARNING **: 03:15:32.286: cannot open display: ^C raija@kone1:~> raija@kone1:~> virsh net-list --all Nimi Tila Automaattikäynnistys Pysyvä ---------------------------------------------- raija@kone1:~> virsh net-start default virhe: verkon ”default” hakeminen epäonnistui virhe: Network not found: no network with matching name 'default' raija@kone1:~> Created attachment 867704 [details]
OK and not OK cases log
The first start of the virtual manager 21.6.2023 04:11:02, which works OK.
The second start 04:11:52 where the connection does not work to the quest.
Hello, I have the same problem. Installed versions: libvirt-libs-9.4.0-3.1 virt-manager-4.1.0-9.1 Even after booting the system virt-manager can't connect. I have to restart libvirtd before virt-manager connects to my VMs: systemctl restart libvirtd I think this is the same problem as in https://bugzilla.suse.com/show_bug.cgi?id=1212480 (In reply to Oliver Schwabedissen from comment #18) > I think this is the same problem as in > https://bugzilla.suse.com/show_bug.cgi?id=1212480 Oops, copy/paste mistake. Link should read https://bugzilla.suse.com/show_bug.cgi?id=1212195 (In reply to Oliver Schwabedissen from comment #19) > Oops, copy/paste mistake. Link should read > https://bugzilla.suse.com/show_bug.cgi?id=1212195 I'd say this is a duplicate of https://bugzilla.suse.com/show_bug.cgi?id=1212396. In bug#1212195 we're working on the correct enabling of systemd socket units between the monolithic and modular libvirt daemons. Actually, I'm going to close this as a duplicate. Those experiencing the problem in this bug, please try the systemd packages in https://build.opensuse.org/request/show/1094372, or wait for the updated systemd to makes its way to TW. *** This bug has been marked as a duplicate of bug 1212396 *** |