Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 457878

Summary: Shouldn't launch network creator if not connected to hypervisor.
Product: Red Hat Enterprise Linux 5 Reporter: Russell Coker <russell>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: crobinso, gozen, jturner, riek, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 21:21:11 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:
Attachments:
Description Flags
virt-manager.log as requested
none
Don't set 'net add' button sensitive if not connected to hypervisor. none

Description Russell Coker 2008-08-05 06:15:23 UTC 
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/pdf/Virtualization.pdf

I am trying to create a new virtual network as described on pages 71 to 78 (Red Hat numbering) of the above document (that's pages 77 to 84 PDF numbering).

When I get to the stage of clicking on the "forward" button for the final time (as shown in figure 17.47) nothing happens.

For "naming your virtual network" I entered "network1" (the suggested value).  At every other screen I just click on "forward" to accept the default values.  So with the most default possible configuration it doesn't work.  I've also tried other values with the same result.
Comment 1 Cole Robinson 2008-09-16 19:54:51 UTC 
Can you provide ~/.virt-manager/virt-manager.log? I can't reproduce this. Using 'network1' and all the default values works for me.

Oh, I should ask, are you 'connected' to the xen hypervisor? As in, when you start the app, are you double clicking the 'xen' entry in the manager window first, or just going straight to host details?
Comment 2 Russell Coker 2008-09-16 22:31:15 UTC 
Created attachment 316913 [details]
virt-manager.log as requested
Comment 3 Cole Robinson 2008-09-16 23:40:41 UTC 
Hmm, that attachment unzipped fine, but the log seems to be only garbage. Not sure what happened. Can you repost?
Comment 4 Cole Robinson 2008-09-17 14:31:59 UTC 
Okay, after talking offline, it turns it virt-manager wasn't connected to the hypervisor.

Changing this bug to track disabling the Virtual Network details section if we aren't connected to the hypervisor to avoid this confusion.
Comment 5 Cole Robinson 2008-09-18 16:23:52 UTC 
Created attachment 317091 [details]
Don't set 'net add' button sensitive if not connected to hypervisor.

Equivalent functionality currently upstream.
Comment 6 Jay Turner 2008-09-19 14:43:31 UTC 
QE ack for RHEL5.3.
Comment 10 errata-xmlrpc 2009-01-20 21:21:11 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0137.html