[virt-tools-list] Virt-manager just sits at Connecting...

[Greg Teiber]

Cole, you're being an amazing resource.  Thank you.  

It's centos7

rpm -q virt-manager gtk3 pygobject3

virt-manager-1.2.1-8.el7.noarch
gtk3-3.14.13-16.el7.x86_64
pygobject3-3.8.2-6.el7.x86_64

-Greg

-----Original Message-----
From: Cole Robinson [mailto:crobinso at redhat.com] 
Sent: Thursday, January 14, 2016 5:54 PM
To: Greg Teiber; virt-tools-list at redhat.com
Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting...

On 01/14/2016 04:57 PM, Greg Teiber wrote:
> I'm using VNC to get to the desktop on a physical server.  
> 
> I tried it with su - and no joy.  So I tried virt-manager --debug
> 
> I got back a couple pages of this: 
> 
> " Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/baseclass.py", line 135, in wrap_func
>     self.disconnect(id_list[0])
>   File "/usr/share/virt-manager/virtManager/baseclass.py", line 96, in disconnect
>     ret = GObject.GObject.disconnect(self, handle)
>   File "/usr/lib64/python2.7/site-packages/gi/overrides/GObject.py", line 429, in wrapper
>     return func(_get_instance_for_signal(obj), *args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/gi/types.py", line 113, in function
>     return info.invoke(*args, **kwargs)
> TypeError: argument instance: Expected GObject.Object, but got PyCObject"
> 
> That's an obvious problem, but I'm not sure what direction to go in repairing it.
> 

Me neither, that's a new one to me. What version of centos is this? Please
provide:

rpm -q virt-manager gtk3 pygobject3

Thanks,
Cole

> -Greg
> 
> -----Original Message-----
> From: Cole Robinson [mailto:crobinso at redhat.com]
> Sent: Thursday, January 14, 2016 10:56 AM
> To: Greg Teiber; virt-tools-list at redhat.com
> Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting...
> 
> On 01/14/2016 11:51 AM, Greg Teiber wrote:
>> I'll give the google route a shot.
>>
>> I su, and become root in the terminal.  Then type virt-manager.  
>>
>> [sa at vm02 ~]$ su
>> Password:
> 
> For one thing you pretty much never want to run plain 'su' if trying 
> to launch a modern desktop app. Use 'su -', which invokes a full login 
> shell, giving root it's own environment, etc. This has caused issues 
> with virt-manager in the past
> 
> Also, are you at the physical machine, or running over ssh ?
> 
>> [root at vm02 sa]# virt-manager
>>
>> I have tried running virt-manager and giving it the root password when it opens.  I get the same result, where it just sits there "Connecting..."
>>
> 
> Try running virt-manager --debug and see what output it shows when it hangs, maybe there's some obvious error that needs fixing.
> 
>>
>>
>> -----Original Message-----
>> From: Cole Robinson [mailto:crobinso at redhat.com]
>> Sent: Thursday, January 14, 2016 10:45 AM
>> To: Greg Teiber; virt-tools-list at redhat.com
>> Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting...
>>
>> On 01/14/2016 11:39 AM, Greg Teiber wrote:
>>> Hello Everyone,
>>>
>>>  
>>>
>>> I didn't see an archive search function...  So here we go. 
>>>
>>
>> There isn't one. But if you google 'virt-tools-list <your question>' 
>> it's pretty close
>>
>>>  
>>>
>>> When I open virt-manager it opens up, and sits there with "QEMU/KVM 
>>> - Connecting..."  And doesn't advance.
>>>
>>> When I first installed this machine, VMM was able to open, and I was 
>>> able to create guests.  However, I was unable to view their consoles.
>>> After rebooting the host, now VMM seems unable to connect.
>>>
>>>  
>>>
>>> I've verified that qemu is running.  If I do virsh - connect 
>>> qemu:///system list  I do see the list of created guests.  And I can 
>>> even start them from the command line.
>>>
>>> I'm running centos 7.  The console I'm logged into is a non privileged user. 
>>> I open a terminal and launch VMM as root. 
>>>
>>
>> How are you launching it as root? Exact command please. sudo, su, su -, su -c, etc.
>>
>> Generally running a UI app as root from a regular desktop session can cause all sorts of issues with dbus access. Better to run virt-manager as a regular user, then feed it your root password via the polkit prompt.
>>
>> - Cole
>>
>