Bug 1014554 - RFE: network: add API to restart virtual networks and preserve VM connectivity
Summary: RFE: network: add API to restart virtual networks and preserve VM connectivity
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
: 1022042 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-02 10:51 UTC by Daniel Berrangé
Modified: 2020-11-03 16:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-03 16:39:27 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Daniel Berrangé 2013-10-02 10:51:14 UTC 
Description of problem:
Currently if you update a virtual network you may well have to destroy & start it again. While this is fine for some types of network, for bridge based networks, this means any active VMs are lost.

It ought to be possible to add a 'virNetworkRestart' command which does the same as virNetworkDestroy + virNetworkCreate, while preserving the veths attached to the bridge.
Comment 1 Cole Robinson 2016-04-10 15:08:54 UTC 
*** Bug 1022042 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Berrangé 2020-11-03 16:39:27 UTC 
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.
Note You need to log in before you can comment on or make changes to this bug.