Xen users - Aug 2009 - Xend problem

An error displayed while running virt-manager or virt-install 
[root@HPCNL-SR-2 init.d]# virt-install
ERROR    unable to connect to ''localhost:8000'': Connection
refused
Traceback (most recent call last):
  File "/usr/sbin/virt-install", line 780, in <module>
    main()
  File "/usr/sbin/virt-install", line 530, in main
    conn = cli.getConnection(options.connect)
  File "/usr/lib/python2.6/site-packages/virtinst/cli.py", line 127,
in getConnection
    return libvirt.open(connect)
  File "/usr/lib/python2.6/site-packages/libvirt.py", line 159, in
open
    if ret is None:raise libvirtError(''virConnectOpen()
failed'')
libvirtError: unable to connect to ''localhost:8000'':
Connection refused

on running this command netstat | grep 8000 i found nothing running on 8000
port.
My xm commands are running since i have started xend.
What should be run by xend on port 8000? Is my xend not running properly What
stops me to create new VMs using virt-manager and virt-install?

This is what my xend.log file shows



	
	
	
	
	
	

[2009-08-29 12:00:26 2108] INFO
(SrvDaemon:220) Xend exited with status 0.

[2009-08-29 12:00:26 2604] INFO
(SrvDaemon:332) Xend Daemon started

[2009-08-29 12:00:26 2604] INFO
(SrvDaemon:336) Xend changeset: Thu Aug 20 08:30:24 2009 +0100
19740:7a57911ff09e.

[2009-08-29 12:00:26 2604] INFO
(XendNetwork:114) Not recreating missing unmanaged network br0
[2009-08-29 12:00:28 2604] DEBUG
(XendDomainInfo:140) XendDomainInfo.recreate({''max_vcpu_id'':
7,
''cpu_time'': 115479526956L, ''ssidref'': 0,
''hvm'': 0, ''shutdown$

[2009-08-29 12:00:28 2604] INFO
(XendDomainInfo:158) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000. at /local/domain/0

[2009-08-29 12:00:28 2604] DEBUG
(XendDomain:452) Adding Domain: 0

[2009-08-29 12:00:28 2604] DEBUG
(XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch

[2009-08-29 12:00:28 2604] DEBUG
(XendDomain:386) number of vcpus to use is 0

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: VBD.set_device not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: VBD.set_type not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: session.get_all_records not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: event.get_record not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: event.get_all not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: VIF.get_network not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: VIF.set_device not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: VIF.set_MAC not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: VIF.set_MTU not found

[2009-08-29 12:00:29 2604] WARNING
(XendAPI:701) API call: debug.get_all not found

[2009-08-29 12:00:29 2604] INFO
(XMLRPCServer:156) Opening Unix domain socket XML-RPC server on
/var/run/xend/xen-api.sock; authentication has been disabled $

[2009-08-29 12:00:29 2604] INFO
(XMLRPCServer:156) Opening Unix domain socket XML-RPC server on
/var/run/xend/xmlrpc.sock.


Any suggestions? 

Regards,
Fasiha Ashraf


      See the Web&#39;s breaking stories, chosen by people like you. Check
out Yahoo! Buzz. http://in.buzz.yahoo.com/

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 08/29/2009 03:45 AM Fasiha Ashraf wrote:
> An error displayed while running virt-manager or virt-install
> [root@HPCNL-SR-2 init.d]# virt-install
> ERROR    unable to connect to ''localhost:8000'':
Connection refused
> 
> ....
>
> libvirtError: unable to connect to ''localhost:8000'':
Connection refused
This looks like a regular networking/security configuration issue, i.e.,
the connection is *refused*.  I would check in /etc/hosts.allow and
/etc/hosts.deny on that "localhost" and see what the settings are
there,
perhaps put a line something like

ALL: LOCAL

just to see if that removes the error message and allows the
establishment of the connection on 8000.  If it does, then you''ll
probably want to go back to hosts.allow and crank down the permissions
more tightly... how tightly is going to depend upon your particular
circumstances.

If the above doesn''t work, don''t be surprised...
there''s quite a few
security measures in place on systems these days.

> 
> on running this command netstat | grep 8000 i found nothing running on
> 8000 port.
> ....
Not surprising, since, as the error message above said, the connect on
port 8000 was not permitted.


hth,
ken, xen noob

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users