Bug 502995 - virt-manager virtual network wizard should not require an IP address
virt-manager virtual network wizard should not require an IP address
Product: Virtualization Tools
Classification: Community
Component: virt-manager (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Berrange
Depends On:
  Show dependency treegraph
Reported: 2009-05-28 03:25 EDT by Peter Bieringer
Modified: 2010-03-16 13:20 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-24 14:57:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Bieringer 2009-05-28 03:25:30 EDT
Description of problem:
Setup of a new switch in GUI requires IPv4 address, but this should be optional because since new version, such interface is also working without IPv4.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Setup new switch without IPv4 address

Actual results:
Does not work

Expected results:

Note also that GUI does not reflect the real settings of current configured switches.

While config is 

# more /etc/libvirt/qemu/networks/IPv6internal.xml 
  <bridge stp='on' forwardDelay='0' />
  <ip address='' netmask=''>
      <range start='' end='' />

(note, IPv4 settings commented out), the GUI still shows this entries, looks like such information is stored a 2nd time on the box.
Comment 1 Mark McLoughlin 2009-05-28 03:39:42 EDT
which GUI? virt-manager?

Maybe a screenshot would help explain why you mean by "does not work"?
Comment 2 Peter Bieringer 2009-05-28 06:05:02 EDT
Yes, the virt-manager, you cannot leave the fields empty. Filling the IPv4 fields is mandatory. Perhaps it would be good to add a switch box "enable IPv4 DCHP" on this interface and if enabled, then IPv4 fields have to be filled, otherwise not.
Comment 3 Mark McLoughlin 2009-06-04 10:29:45 EDT
Okay, thanks - moving upstream since it's not a very common case

See also bug #501912
Comment 4 Cole Robinson 2009-09-24 14:57:10 EDT
Current upstream provides an option to disable DHCP when creating a new virtual network. Closing as UPSTREAM.

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