I''m attempting to install xen 4.0.0 in combination with slackware64 13.1. I''ve got xen and dom0 booing, but when xend is not starting. This seems to be a common problem with this combination but the soluion seems to evade my attempts at searching. I am working from the sources http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz For dom0 I''m using the kernel built when I did a make world. Should this create a workable a combination? Thanks, Jack _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Did you setup the init scripts to launch xend at boot? On Thu, Aug 5, 2010 at 10:08 AM, Jack Lowry <jrlowry376@comcast.net> wrote:> I''m attempting to install xen 4.0.0 in combination with slackware64 13.1. > I''ve got xen and dom0 booing, but when xend is not starting. > This seems to be a common problem with this combination but the soluion > seems to evade my attempts at searching. > > I am working from the sources > http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz > For dom0 I''m using the kernel built when I did a make world. > Should this create a workable a combination? > > Thanks, Jack > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Can you try starting xend by hand, or check /var/log/xen/* for any errors?> I''m attempting to install xen 4.0.0 in combination with slackware64 13.1. > I''ve got xen and dom0 booing, but when xend is not starting. > This seems to be a common problem with this combination but the > soluion seems to evade my attempts at searching. > > I am working from the sources > http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz > For dom0 I''m using the kernel built when I did a make world. > Should this create a workable a combination? > > Thanks, Jack > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes I added cd /etc/init.d/ /etc/init.d/xend start to the end of /etc/rc.d/rc.local Once I get something working I''ll revisit the init scripts creatng something more in line with the way slackware normally does stuff. Jack> Did you setup the init scripts to launch xend at boot? > > On Thu, Aug 5, 2010 at 10:08 AM, Jack Lowry <jrlowry376@comcast.net> > wrote: >> I''m attempting to install xen 4.0.0 in combination with slackware64 >> 13.1. >> I''ve got xen and dom0 booing, but when xend is not starting. >> This seems to be a common problem with this combination but the soluion >> seems to evade my attempts at searching. >> >> I am working from the sources >> http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz >> For dom0 I''m using the kernel built when I did a make world. >> Should this create a workable a combination? >> >> Thanks, Jack >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Following another suggestion I''ve started xend by hange from
/etc/init.d
directory with xend start
The contents of a freshly minted xed.log file are :
[2010-08-05 14:59:21 1770] INFO (SrvDaemon:332) Xend Daemon started
[2010-08-05 14:59:21 1770] INFO (SrvDaemon:336) Xend changeset: unavailable.
[2010-08-05 14:59:22 1770] ERROR (SrvDaemon:349) Exception starting xend
((111, ''Connection refused''))
Traceback (most recent call last):
File
"/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
line
341, in run
servers = SrvServer.create()
File
"/usr/lib64/python2.6/site-packages/xen/xend/server/SrvServer.py",
line
251, in create
root.putChild(''xend'', SrvRoot())
File
"/usr/lib64/python2.6/site-packages/xen/xend/server/SrvRoot.py",
line 40, in __init__
self.get(name)
File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line
84,
in get
val = val.getobj()
File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line
52,
in getobj
self.obj = klassobj()
File
"/usr/lib64/python2.6/site-packages/xen/xend/server/SrvNode.py",
line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line
1141, in instance
inst.save()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line
578, in save
self.save_networks()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line
594, in save_networks
for network_uuid in XendNetwork.get_all()])
File "/usr/lib64/python2.6/site-packages/xen/xend/XendBase.py", line
102, in get_record
for key in keys])
File "/usr/lib64/python2.6/site-packages/xen/xend/XendNetwork.py",
line 196, in get_VIFs
vms = XendDomain.instance().get_all_vms()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py",
line
1882, in instance
inst.init()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py",
line
114, in init
xstransact.Mkdir(XS_VMROOT)
File
"/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py",
line 355, in Mkdir
complete(path, lambda t: t.mkdir(*args))
File
"/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py",
line 361, in complete
t = xstransact(path)
File
"/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py",
line 29, in __init__
self.transaction = xshandle().transaction_start()
File
"/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xsutil.py",
line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, ''Connection refused'')
[2010-08-05 14:59:22 1769] INFO (SrvDaemon:220) Xend exited with status 1.
>
>
>> Did you setup the init scripts to launch xend at boot?
>>
>> On Thu, Aug 5, 2010 at 10:08 AM, Jack Lowry
<jrlowry376@comcast.net>
>> wrote:
>>
>>> I''m attempting to install xen 4.0.0 in combination with
slackware64
>>> 13.1.
>>> I''ve got xen and dom0 booing, but when xend is not
starting.
>>> This seems to be a common problem with this combination but the
soluion
>>> seems to evade my attempts at searching.
>>>
>>> I am working from the sources
>>> http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz
>>> For dom0 I''m using the kernel built when I did a make
world.
>>> Should this create a workable a combination?
>>>
>>> Thanks, Jack
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xensource.com
>>> http://lists.xensource.com/xen-users
>>>
>>>
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Jack Lowry wrote:> Following another suggestion I''ve started xend by hange from > /etc/init.d directory with xend start > > The contents of a freshly minted xed.log file are : > [2010-08-05 14:59:21 1770] INFO (SrvDaemon:332) Xend Daemon started > [2010-08-05 14:59:21 1770] INFO (SrvDaemon:336) Xend changeset: > unavailable. > [2010-08-05 14:59:22 1770] ERROR (SrvDaemon:349) Exception starting > xend ((111, ''Connection refused'')) > Traceback (most recent call last): > File > "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", > line 341, in run > servers = SrvServer.create() > File > "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvServer.py", > line 251, in create > root.putChild(''xend'', SrvRoot()) > File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvRoot.py", > line 40, in __init__ > self.get(name) > File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line 84, > in get > val = val.getobj() > File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line 52, > in getobj > self.obj = klassobj() > File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvNode.py", > line 30, in __init__ > self.xn = XendNode.instance() > File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line > 1141, in instance > inst.save() > File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line > 578, in save > self.save_networks() > File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line > 594, in save_networks > for network_uuid in XendNetwork.get_all()]) > File "/usr/lib64/python2.6/site-packages/xen/xend/XendBase.py", line > 102, in get_record > for key in keys]) > File "/usr/lib64/python2.6/site-packages/xen/xend/XendNetwork.py", > line 196, in get_VIFs > vms = XendDomain.instance().get_all_vms() > File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", > line 1882, in instance > inst.init() > File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", > line 114, in init > xstransact.Mkdir(XS_VMROOT) > File > "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", > line 355, in Mkdir > complete(path, lambda t: t.mkdir(*args)) > File > "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", > line 361, in complete > t = xstransact(path) > File > "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", > line 29, in __init__ > self.transaction = xshandle().transaction_start() > File > "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xsutil.py", line > 18, in xshandle > xs_handle = xen.lowlevel.xs.xs() > Error: (111, ''Connection refused'') > [2010-08-05 14:59:22 1769] INFO (SrvDaemon:220) Xend exited with > status 1. > >Do you have a xen-common init script? I think you should run it before xend.> >> >> >>> Did you setup the init scripts to launch xend at boot? >>> >>> On Thu, Aug 5, 2010 at 10:08 AM, Jack Lowry <jrlowry376@comcast.net> >>> wrote: >>> >>>> I''m attempting to install xen 4.0.0 in combination with slackware64 >>>> 13.1. >>>> I''ve got xen and dom0 booing, but when xend is not starting. >>>> This seems to be a common problem with this combination but the >>>> soluion >>>> seems to evade my attempts at searching. >>>> >>>> I am working from the sources >>>> http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz >>>> For dom0 I''m using the kernel built when I did a make world. >>>> Should this create a workable a combination? >>>> >>>> Thanks, Jack >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xensource.com >>>> http://lists.xensource.com/xen-users >>>> >>>> >> >> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Jorge Armando Medina Computación Gráfica de México Web: http://www.e-compugraf.com Tel: 55 51 40 72, Ext: 124 Email: jmedina@e-compugraf.com GPG Key: 1024D/28E40632 2007-07-26 GPG Fingerprint: 59E2 0C7C F128 B550 B3A6 D3AF C574 8422 28E4 0632 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Jack Lowry wrote: >> Following another suggestion I''ve started xend by hange from >> /etc/init.d directory with xend start >> >> The contents of a freshly minted xed.log file are : >> [2010-08-05 14:59:21 1770] INFO (SrvDaemon:332) Xend Daemon started >> [2010-08-05 14:59:21 1770] INFO (SrvDaemon:336) Xend changeset: >> unavailable. >> [2010-08-05 14:59:22 1770] ERROR (SrvDaemon:349) Exception starting >> xend ((111, ''Connection refused'')) >> xs_handle = xen.lowlevel.xs.xs() >> Error: (111, ''Connection refused'') >> [2010-08-05 14:59:22 1769] INFO (SrvDaemon:220) Xend exited with >> status 1. >> >> > Do you have a xen-common init script? I think you should run it before > xend. >No I do not have a xen-common init script _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users