Bug 738758

Summary: RFE: should allow editing of virtual network details (address ranges, etc)
Product: [Community] Virtualization Tools Reporter: Eric Blake <eblake>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, dougsland, hbrock, ibaldo, jforbes, jik, tselios.petros, virt-maint, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-26 17:20:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Blake 2011-09-15 18:04:17 UTC 
Description of problem:
On a new host, I want to set up my default network to use 192.168.123.0/24 instead of the default 192.168.122.0/24 to match network topology decisions already in effect elsewhere in my home network.  But while virt-manager makes this look possible (see bug 738751), there is currently no support for making this edit with the gui; and I must drop to virsh.

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-5.fc16.noarch

How reproducible:
100%

Steps to Reproduce:
1. Edit->Connection Details of a qemu connection
2. Select the "Virtual Networks" tab, and look at the Network: field
3. Try editing the Network field

Actual results:
nothing happens

Expected results:
I should be able to change 122 to 123, and restart the network with the new parameters, all without having to drop to virsh.

Additional info:
Found during Fedora Virt Test Day:
https://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization
Comment 1 Cole Robinson 2012-01-18 16:42:13 UTC 
Not really relevant for a fedora backport so moving to upstream tracker
Comment 2 Cole Robinson 2013-09-29 16:32:36 UTC 
Networks can be renamed in upstream virt-manager now. Someone could use that infrastructure as a launching point for implementing more XML changing in the UI
Comment 3 Cole Robinson 2015-04-09 16:44:38 UTC 
*** Bug 1171192 has been marked as a duplicate of this bug. ***
Comment 4 Cole Robinson 2015-04-09 16:48:15 UTC 
Bug 1171192 was asking for option to edit network 'domain' field
Comment 5 Peter Tselios 2018-03-01 19:14:07 UTC 
This RFE is open for 7 years. Is there any possibility to see this implemented? 
I would really like to have all network management from the GUI as well.
Comment 6 Cole Robinson 2018-03-01 19:26:36 UTC 
I've been thinking about a different approach WRT this stuff, and probably just adding a raw XML editing screen. I'll need to experiment with it though

There's so many config options nowadays that going down the road of picking and choosing what to expose for editing in the UI is an endless treadmill of stuff with a generally small audience of users for the majority of bits.
Comment 7 Peter Tselios 2018-03-01 21:40:19 UTC 
First of all, I am happy that this is not a dead RFE. If I may. Why don't you start with something simple, like for example the option to create networks and/or modify the IP ranges? 

This will cover the most basic needs. And then we will see :)
Comment 8 Cole Robinson 2018-03-01 21:53:48 UTC 
There's already an option for creating networks, there's a whole wizard devoted to it. Click the + button on the network page
Comment 9 Peter Tselios 2018-03-04 17:43:40 UTC 
Correct. But not for editing the network! At least no option that I found.
Comment 10 Cole Robinson 2020-01-26 17:20:31 UTC 
virt-manager 2.2.0 has a tab for editing the raw XML of network objects (and all other objects). That is our planned solution for editing network details like this and other fields. Closing as CURRENTRELEASE