error when trying to connect with virt-manager

[Jimison, Ed]

I am doing a new install of Fedora Core 6, trying to use the
virt-manager app to create fully virtualized guests on an Intel
VT-enabled system. I have read the Fedora Xen Quickstart guide and have
verified that the Xen kernel is running  (via uname -r) and that Xen is
started (via xm list). After starting virt-manager, clicking "Local Xen
host" in the Open connection box, and clicking Connect I get the
following error:

 

Unable to open a connection to the Xen hypervisor/daemon

            Verify that:

            - A Xen host kernel was booted

            - The Xen service has been started

 

Has anyone else seen this?

[Fischer, Anna]

I have the same problem, with xend + Xen kernel running and the
xend-config.sxp configured accordingly by setting either 

(xend-http-server yes) or

(xend-unix-server yes).

But still I can't get virt-manager to run. I hope someone can help
here...


________________________________

	From: fedora-xen-bounces(a)redhat.com
[mailto:[e-mail]] On Behalf Of Jimison, Ed
	Sent: 21 November 2006 23:06
	To: fedora-xen(a)redhat.com
	Subject: [Fedora-xen] error when trying to connect with
virt-manager
	
	

	I am doing a new install of Fedora Core 6, trying to use the
virt-manager app to create fully virtualized guests on an Intel
VT-enabled system. I have read the Fedora Xen Quickstart guide and have
verified that the Xen kernel is running  (via uname -r) and that Xen is
started (via xm list). After starting virt-manager, clicking "Local Xen
host" in the Open connection box, and clicking Connect I get the
following error:

	 

	Unable to open a connection to the Xen hypervisor/daemon

	            Verify that:

	            - A Xen host kernel was booted

	            - The Xen service has been started

	 

	Has anyone else seen this?

[Daniel P. Berrange]

On Wed, Nov 22, 2006 at 07:37:59AM -0000, Fischer, Anna wrote:
>  I have the same problem, with xend + Xen kernel running and the
>  xend-config.sxp configured accordingly by setting either 
>  
>  (xend-http-server yes) or 
Don't turn this on - it is a (remotely exploitable) security hole
because it makes XenD open a TCP port with no authentication checks
made upon connection :-(

>  (xend-unix-server yes). 
This is the required parameter for virt-manager.

>  But still I can't get virt-manager to run. I hope someone can
> help
>  here... 
Check in /root/.virt-manager/virt-manager.log for any errors being
reported. Also just try running 'virsh list' which is a simple 
sanity test for libvirt operating correctly.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone] -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

[Fischer, Anna]

The log says:

Wed, 22 Nov 2006 12:17:44 ERROR    Unable to open connection to
hypervisor URI 'xen': socket.gaierror (-2, 'Name or service not known') 

"virsh list" runs perfect on my system. Furthermore, a strange thing is
that while this error message window is shown when virt-manager starts
up, I can see in the background (virt-manager GUI is actually loaded
while showing the error message) that virt-manager shows Dom0 and its
CPU usage etc. correctly. So why do I get this error message then and
virt-manager shuts down?


>  -----Original Message-----
>  From: Daniel P. Berrange [mailto:[e-mail]] 
>  Sent: 22 November 2006 12:07
>  To: Fischer, Anna
>  Cc: Jimison, Ed; fedora-xen(a)redhat.com
>  Subject: Re: [Fedora-xen] error when trying to connect with 
>  virt-manager
>  
>  On Wed, Nov 22, 2006 at 07:37:59AM -0000, Fischer, Anna wrote:
>  > I have the same problem, with xend + Xen kernel running and the 
>  > xend-config.sxp configured accordingly by setting either
>  > 
>  > (xend-http-server yes) or
>  
>  Don't turn this on - it is a (remotely exploitable) security 
>  hole because it makes XenD open a TCP port with no 
>  authentication checks made upon connection :-(
>  
>  > (xend-unix-server yes).
>  
>  This is the required parameter for virt-manager.
>  
>  > But still I can't get virt-manager to run. I hope someone can help 
>  > here...
>  
>  Check in /root/.virt-manager/virt-manager.log for any errors 
>  being reported. Also just try running 'virsh list' which is a 
>  simple sanity test for libvirt operating correctly.
>  
>  Regards,
>  Dan.
>  -- 
>  |=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 
>  978 392 2496 -=|
>  |=-           Perl modules: http://search.cpan.org/~danberr/  
>              -=|
>  |=-               Projects: http://freshmeat.net/~danielpb/   
>              -=|
>  |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF 
>  F742 7D3B 9505  -=| 
>

[Daniel P. Berrange]

On Wed, Nov 22, 2006 at 12:27:01PM -0000, Fischer, Anna wrote:
>  The log says:
>  
>  Wed, 22 Nov 2006 12:17:44 ERROR    Unable to open connection to
>  hypervisor URI 'xen': socket.gaierror (-2, 'Name or service not known') 
Hmm, sounds like you have a messed up /etc/hosts file - check that
the line for '127.0.0.1' has a name 'localhost' associated with it,
eg

$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
::1             localhost.localdomain localhost


>  
>  "virsh list" runs perfect on my system. Furthermore, a strange thing is
>  that while this error message window is shown when virt-manager starts
>  up, I can see in the background (virt-manager GUI is actually loaded
>  while showing the error message) that virt-manager shows Dom0 and its
>  CPU usage etc. correctly. So why do I get this error message then and
>  virt-manager shuts down? 
Its it failing to lookup 'localhost' when opening the console for the
guest I think.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone] -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

[Fischer, Anna]

Yes, you were right. It was in fact a name resolution problem. Now it
works fine. Thanks!! 

>  -----Original Message-----
>  From: Daniel P. Berrange [mailto:[e-mail]] 
>  Sent: 22 November 2006 13:33
>  To: Fischer, Anna
>  Cc: Jimison, Ed; fedora-xen(a)redhat.com
>  Subject: Re: [Fedora-xen] error when trying to connect with 
>  virt-manager
>  
>  On Wed, Nov 22, 2006 at 12:27:01PM -0000, Fischer, Anna wrote:
>  > The log says:
>  > 
>  > Wed, 22 Nov 2006 12:17:44 ERROR    Unable to open connection to
>  > hypervisor URI 'xen': socket.gaierror (-2, 'Name or service not 
>  > known')
>  
>  Hmm, sounds like you have a messed up /etc/hosts file - check 
>  that the line for '127.0.0.1' has a name 'localhost' 
>  associated with it, eg
>  
>  $ cat /etc/hosts
>  # Do not remove the following line, or various programs # 
>  that require network functionality will fail.
>  127.0.0.1               localhost.localdomain localhost
>  ::1             localhost.localdomain localhost
>  
>  
>  > 
>  > "virsh list" runs perfect on my system. Furthermore, a 
>  strange thing 
>  > is that while this error message window is shown when virt-manager 
>  > starts up, I can see in the background (virt-manager GUI is 
>  actually 
>  > loaded while showing the error message) that virt-manager 
>  shows Dom0 
>  > and its CPU usage etc. correctly. So why do I get this 
>  error message 
>  > then and virt-manager shuts down?
>  
>  Its it failing to lookup 'localhost' when opening the console 
>  for the guest I think.
>  
>  Dan.
>  -- 
>  |=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 
>  978 392 2496 -=|
>  |=-           Perl modules: http://search.cpan.org/~danberr/  
>              -=|
>  |=-               Projects: http://freshmeat.net/~danielpb/   
>              -=|
>  |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF 
>  F742 7D3B 9505  -=| 
>