Bug 2215823 - Hang when attempting to connect to qemu:///system
Summary: Hang when attempting to connect to qemu:///system
Keywords:
Status: CLOSED DUPLICATE of bug 2213660
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 38
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-19 03:31 UTC by alex
Modified: 2023-06-20 03:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-19 03:43:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Debug output (13.97 KB, text/plain)
2023-06-19 03:32 UTC, alex
no flags Details

Description alex 2023-06-19 03:31:36 UTC
When I attempt to connect to qemu:///system, the connection status is stuck at "Connecting..." after I authenticate. This was working fine previously and I don't know what caused it to stop working.

Reproducible: Always

Steps to Reproduce:
1. Create a QEMU/KVM connection with qemu:///system as the URI.
2. Attempt to activate the connection.
Actual Results:  
I'm prompted to enter my password as expected, but after I do so the connection status still shows "Connecting..." and it never completes.

Expected Results:  
The connection is activated and I can see the guests.

Version: 4.1.0-2.fc38

Comment 1 alex 2023-06-19 03:32:54 UTC
Created attachment 1971489 [details]
Debug output

Comment 2 alex 2023-06-19 03:43:05 UTC
It started working after I rebooted. I didn't update any packages since the last boot so I don't know why it wasn't working.

Comment 3 Daniel Berrangé 2023-06-19 07:59:45 UTC
Potentially you hit this https://bugzilla.redhat.com/show_bug.cgi?id=2213660

Comment 4 alex 2023-06-20 03:18:38 UTC
That appears to be the case, thank you.

*** This bug has been marked as a duplicate of bug 2213660 ***


Note You need to log in before you can comment on or make changes to this bug.