[Pkg-libvirt-maintainers] Bug#770191: virt-manager new VM wizard not showing summary/customization page

[Roberto C. Sánchez]

On Thu, Feb 26, 2015 at 12:31:55PM -0500, Roberto C. Sánchez wrote:
> I also note that in Step 1, the wizard does show a text entry field to
> allow me to name the VM, resulting in libvirt assigning an arbitrary
> name.
> 

That should have "the wizard does not show a text entry field".

In any event, I was looking into this and I noticed something.  When I
first launch the "Create a new virtual machice" wizard, an exception is
raised:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1088, in netdev_changed
    obj = self.conn.get_net(key)
  File "/usr/share/virt-manager/virtManager/connection.py", line 685, in get_net
    return self.nets[uuid]
KeyError: 'c0c7254e-96fe-8b9a-68c8-d6aa7966d3bb'

Looking at connection.py, it seems like the problem is that the nets
dictionary never gets populated.  The _update_nets function starts at
line 1097:

    def _update_nets(self, dopoll):
        if not dopoll or not self.is_network_capable():
            return {}, {}, self.nets
        return pollhelpers.fetch_nets(self._backend, self.nets.copy(),
                    (lambda obj, key: vmmNetwork(self, obj, key)))

I am not sure why it never gets populated, but when I option the
connection details for this particular server (which is running Xen), I
see that in virtual networks, only 'default' is listed, and it isn't
started.  The fact that it is not started is fine because I don't want
NAT networking in my case.  My networking is configured according to the
Debian wiki page for Xen[0], except that I have a static IP
configuration and the device is named br0 instead of xenbr0.

I am then able to proceed through the steps until step 4.  At step 4, I
am not able to select "Allocate entire disk now" and hovering over it
shows a tool tip of "Disk format 'None' does not support full
allocation".

Clicking on "Forward" at step 4 results in the same exception being
raised.  However, while the window contents remain the same, the text at
the top does change to "Step 5 of 5" and the button at the bottom right
changes to "Finish".  It looks like what is happening is that the
exception is being triggered when it tries to enumerate the networks so
that advanced options can allow the user to choose the network device.

Clicking "Finish" does result in the VM being created (with a default
name of debianwheezy), but then the display disconnects (I am running
virt-manager on my workstation (running jessie) and connecting to the
server (running wheezy) using a xen+tls:// connection.  The reson the
display does not show up is because I was not able to check the
"customize" in the fifth step to modify the VNC to listen on all
interfaces.

When I log directly into the server and run virt-manager there (ssh with
X forwarding) I can connect to the new VM, but all I see is the BIOS
POST message and at the bottom it says "No bootable device.  Powering
off in 30 seconds."

If there is something I can do that might help figure this out, please
let me know.

Regards,

-Roberto

[0] https://wiki.debian.org/Xen#Configure_Networking

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20150227/cbb851d9/attachment.sig>