Red Hat Bugzilla – Bug 457878
Shouldn't launch network creator if not connected to hypervisor.
Last modified: 2009-12-14 16:10:20 EST
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.
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?
Created attachment 316913 [details]
virt-manager.log as requested
Hmm, that attachment unzipped fine, but the log seems to be only garbage. Not sure what happened. Can you repost?
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.
Created attachment 317091 [details]
Don't set 'net add' button sensitive if not connected to hypervisor.
Equivalent functionality currently upstream.
QE ack for RHEL5.3.
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.