Bug 502995
Summary: | virt-manager virtual network wizard should not require an IP address | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Peter Bieringer <pb> |
Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | 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
which GUI? virt-manager? Maybe a screenshot would help explain why you mean by "does not work"? 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. Okay, thanks - moving upstream since it's not a very common case See also bug #501912 Current upstream provides an option to disable DHCP when creating a new virtual network. Closing as UPSTREAM. |