Bug 683371 - [RFE] Do not set up virbr0 by default
Summary: [RFE] Do not set up virbr0 by default
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 554476
TreeView+ depends on / blocked
 
Reported: 2011-03-09 09:53 UTC by J.H.M. Dassen (Ray)
Modified: 2018-11-14 16:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-11 02:35:07 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Legacy) 42186 0 None None None Never

Description J.H.M. Dassen (Ray) 2011-03-09 09:53:52 UTC
2. What is the nature and description of the request?

no /etc/libvirt/qemu/networks/default.xml after install of libvirt

   3. Why does the customer need this? (List the business requirements here)

They start libvirt, their network configuration breaks.

   4. How would the customer like to achieve this? (List the functional requirements here)

remove post script

   5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.

remove post script

   6. Is there already an existing RFE upstream or in Red Hat bugzilla?

Not that I've seen

   7. How quickly does this need resolved? (desired target release)

ASAP, 5.8 ?

   8. Does this request meet the RHEL Inclusion criteria (please review)

Yes

   9. List the affected packages

libvirt

  10. Would the customer be able to assist in testing this functionality if
implemented?

absolutely.

Comment 7 RHEL Program Management 2011-06-20 22:36:20 UTC
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.

Comment 10 RHEL Program Management 2011-08-11 02:35:07 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.


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