Bug 502995

Summary: virt-manager virtual network wizard should not require an IP address
Product: [Community] Virtualization Tools Reporter: Peter Bieringer <pb>
Component: virt-managerAssignee: Daniel Berrangé <berrange>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: berrange, clalance, crobinso, hbrock, itamar, markmc, tore, veillard, virt-maint, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-24 18:57:10 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 Peter Bieringer 2009-05-28 07:25:30 UTC
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):
libvirt-0.6.2-11.fc11.i586

How reproducible:
Always

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

Actual results:
Does not work


Expected results:
Work

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

While config is 

# more /etc/libvirt/qemu/networks/IPv6internal.xml 
<network>
  <name>IPv6internal</name>
  <uuid>c6a01b49-73b2-61f0-5356-059ae90f5c5b</uuid>
  <bridge stp='on' forwardDelay='0' />
  <!--
  <ip address='192.168.100.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.100.128' end='192.168.100.254' />
    </dhcp>
  </ip>
  -->
</network>

(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 07:39:42 UTC
which GUI? virt-manager?

Maybe a screenshot would help explain why you mean by "does not work"?

Comment 2 Peter Bieringer 2009-05-28 10:05:02 UTC
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 14:29:45 UTC
Okay, thanks - moving upstream since it's not a very common case

See also bug #501912

Comment 4 Cole Robinson 2009-09-24 18:57:10 UTC
Current upstream provides an option to disable DHCP when creating a new virtual network. Closing as UPSTREAM.