Bug 2255266 - sudo virsh --connect=qemu:///system net-start m5192_1_4 times out
Summary: sudo virsh --connect=qemu:///system net-start m5192_1_4 times out
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-19 18:54 UTC by Cagney
Modified: 2024-12-16 02:23 UTC (History)
8 users (show)

Fixed In Version: libvirt-10.6.0-6.fc41
Clone Of:
Environment:
Last Closed: 2024-12-16 02:23:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cagney 2023-12-19 18:54:53 UTC
The network xml looks like:

<network ipv6='yes'>
  <name>m5192_1_4</name>
  <bridge name='m5192_1_4'
          stp='on' delay='0'/>
  <!--
  <ip address='m5192.1.4.253'/>
    -->
</network>

adding it is ok, but it times out trying to start:

sudo virsh --connect=qemu:///system net-start m5192_1_4
error: Failed to start network m5192_1_4
error: error from service: Timeout was reached

This looks to be the interesting bit:

Thread 2 (Thread 0x7f0b157ff6c0 (LWP 1487) "rpc-virtnetwork"):
#0  0x00007f0b171d5bcd in poll () at /lib64/libc.so.6
#1  0x00007f0b1756ceb4 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f0b17513447 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x00007f0b173eb1e5 in g_dbus_connection_send_message_with_reply_sync () at /lib64/libgio-2.0.so.0
#4  0x00007f0b173eff33 in g_dbus_connection_call_sync_internal () at /lib64/libgio-2.0.so.0
#5  0x00007f0b173f02f6 in g_dbus_connection_call_sync () at /lib64/libgio-2.0.so.0
#6  0x00007f0b1771c509 in virGDBusCallMethod () at /lib64/libvirt.so.0
#7  0x00007f0b1771c91c in virFirewallDInterfaceSetZone () at /lib64/libvirt.so.0
#8  0x00007f0b147f3360 in networkAddFirewallRules () at /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so
#9  0x00007f0b147f4510 in networkStartNetwork () at /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so
#10 0x00007f0b147f4db0 in networkCreate () at /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so
#11 0x00007f0b1795f4a3 in virNetworkCreate () at /lib64/libvirt.so.0
#12 0x000055bc44efc4b4 in remoteDispatchNetworkCreateHelper.lto_priv.0 ()
#13 0x00007f0b178280c5 in virNetServerProgramDispatch () at /lib64/libvirt.so.0
#14 0x00007f0b1782eb23 in virNetServerProcessMsg () at /lib64/libvirt.so.0
#15 0x00007f0b1782ec36 in virNetServerHandleJob () at /lib64/libvirt.so.0
#16 0x00007f0b17766c45 in virThreadPoolWorker () at /lib64/libvirt.so.0
#17 0x00007f0b17765e00 in virThreadHelper () at /lib64/libvirt.so.0
#18 0x00007f0b1715c897 in start_thread () at /lib64/libc.so.6
#19 0x00007f0b171e36fc in clone3 () at /lib64/libc.so.6


Reproducible: Always

Steps to Reproduce:
Where happens every time is defined as happens once per freshly created network being started. But I've >100.



f38 was ok(ish)

Comment 1 Aoife Moloney 2024-11-13 10:18:20 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Cagney 2024-11-13 14:17:39 UTC
Good news is that upstream seem to have worked on this: https://gitlab.com/libvirt/libvirt/-/issues/588

Comment 3 Daniel Berrangé 2024-11-13 16:13:32 UTC
(In reply to Cagney from comment #2)
> Good news is that upstream seem to have worked on this:
> https://gitlab.com/libvirt/libvirt/-/issues/588

FYI the fix there is in libvirt 10.8.0, and thus will be in Fedora 42 rawhide.

Should be viable to backport Laine's commit to F41, so will leave this open to track backport possibility.

Comment 4 Fedora Update System 2024-12-14 19:24:09 UTC
FEDORA-2024-c204834f78 (libvirt-10.6.0-6.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-c204834f78

Comment 5 Fedora Update System 2024-12-15 03:06:45 UTC
FEDORA-2024-c204834f78 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c204834f78`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c204834f78

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-12-16 02:23:15 UTC
FEDORA-2024-c204834f78 (libvirt-10.6.0-6.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


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