[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen 3.4.2 on kernel 2.6.32.8 on Lenny


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Dot Yet <dot.yet@xxxxxxxxx>
  • Date: Wed, 24 Feb 2010 23:13:32 -0500
  • Delivery-date: Wed, 24 Feb 2010 20:14:39 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=UPtupGhuEk434omPMj4abmxJpbvrZFJj5IWQmE8UIlVR2r/sJtDQHq+NIujH8eUSJL ZcoEhcg+Cal1qLwi1ubw1rn/2FamfZz8HTQBAQ26imXS/Lm2KWmHB9HpabMoKcfVSRVI FOcOm7Qpa4bZlDjK+OZ+tQ5RzHoicxw2HB0Og=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

OK. I fixed that issue. I had to load module xen-evtchn. By default
the system was loading module evtchn, whose name has been changed.

thx anyways,
dot yet


On Wed, Feb 24, 2010 at 10:08 PM, Dot Yet <dot.yet@xxxxxxxxx> wrote:
> Hi Everyone,
>
> Thanks for all the inputs. I am trying to work with Jeremy's
> repository with xen 3.4.2 source.
>
> The compilation for kernel 2.6.31.6 as well as xen happens fine. The
> system boots fine too. But xend does not start. Earlier, it was
> complaining about /proc/xen/capabilities not being present, fixed that
> error by adding xenfs to /etc/fstab.
>
> Now, its giving the following error about port 111. I noticed that
> portmap service is running on that port. Can you help me find whats
> wrong here?
>
> Any help is appreciated.
>
> [2010-02-24 21:58:27 4266] INFO (SrvDaemon:332) Xend Daemon started
> [2010-02-24 21:58:27 4266] INFO (SrvDaemon:336) Xend changeset: unavailable.
> [2010-02-24 21:58:27 4266] INFO (XendNetwork:114) Not recreating
> missing unmanaged network tmpbridge
> [2010-02-24 21:58:29 4266] ERROR (SrvDaemon:349) Exception starting
> xend ((111, 'Connection refused'))
> Traceback (most recent call last):
>  File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py",
> line 341, in run
>    servers = SrvServer.create()
>  File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvServer.py",
> line 251, in create
>    root.putChild('xend', SrvRoot())
>  File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvRoot.py",
> line 40, in __init__
>    self.get(name)
>  File "/usr/lib/python2.5/site-packages/xen/web/SrvDir.py", line 84, in get
>    val = val.getobj()
>  File "/usr/lib/python2.5/site-packages/xen/web/SrvDir.py", line 52, in getobj
>    self.obj = klassobj()
>  File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvNode.py",
> line 30, in __init__
>    self.xn = XendNode.instance()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line
> 949, in instance
>    inst.save()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line
> 484, in save
>    self.save_networks()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line
> 499, in save_networks
>    for network_uuid in XendNetwork.get_all()])
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendBase.py", line
> 102, in get_record
>    for key in keys])
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendNetwork.py",
> line 196, in get_VIFs
>    vms = XendDomain.instance().get_all_vms()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line
> 1778, in instance
>    inst.init()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line
> 113, in init
>    xstransact.Mkdir(XS_VMROOT)
>  File "/usr/lib/python2.5/site-packages/xen/xend/xenstore/xstransact.py",
> line 355, in Mkdir
>    complete(path, lambda t: t.mkdir(*args))
>  File "/usr/lib/python2.5/site-packages/xen/xend/xenstore/xstransact.py",
> line 361, in complete
>    t = xstransact(path)
>  File "/usr/lib/python2.5/site-packages/xen/xend/xenstore/xstransact.py",
> line 29, in __init__
>    self.transaction = xshandle().transaction_start()
>  File "/usr/lib/python2.5/site-packages/xen/xend/xenstore/xsutil.py",
> line 18, in xshandle
>    xs_handle = xen.lowlevel.xs.xs()
> Error: (111, 'Connection refused')
> [2010-02-24 21:58:30 4265] INFO (SrvDaemon:220) Xend exited with status 1.
>
>
> thx,
> dot yet
>
>
> On Tue, Feb 23, 2010 at 2:29 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> On Tue, Feb 23, 2010 at 10:53:04AM -0500, Robbie A. Garrett wrote:
>>> Hello,
>>> perhaps I missed something I see no xen options in menuconfig when i pull 
>>> down the kernel from xen/master
>>>
>>> The command i did was
>>> git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git 
>>> xen/master  which brought down a directory of xen/master.
>>>
>>> When I run make  menuconfig it does show 2.6.31.6 as the kernel version 
>>> which i think is correct..  but again I see no xen options.
>>>
>>
>> Please see:
>> http://wiki.xensource.com/xenwiki/XenParavirtOps
>>
>> for more information about how to compile and what options to choose.
>>
>> -- Pasi
>>
>>> ________________________________________
>>> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
>>> [xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Pasi Kärkkäinen 
>>> [pasik@xxxxxx]
>>> Sent: Tuesday, February 23, 2010 4:53 AM
>>> To: Dot Yet
>>> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
>>> Subject: Re: [Xen-users] Xen 3.4.2 on kernel 2.6.32.8 on Lenny
>>>
>>> On Mon, Feb 22, 2010 at 10:12:32PM -0500, Dot Yet wrote:
>>> > Hi Everyone,
>>> >
>>> > I am trying to compile Xen 3.4.2 on kernel 2.6.32.8 on Debian 5.
>>> >
>>> > Seems I am missing something simple here, and seek your help.
>>> >
>>> > I downloaded the kernel source from kernel.org and xen's source from 
>>> > xen.org
>>> >
>>> > Compiled kernel in its own directory, included 'XEN' and/or 'PARAVIRT'
>>> > related options in the .config file and built bzImage and modules. It
>>> > compiles fine with no errors.
>>> >
>>> > Then, compiled xen's source. That downloaded kernel 2.6.18 from
>>> > mercurial, and built happened successfully. Next, I installed this xen
>>> > build and rebooted the node. So far so good. Then, I installed the
>>> > newly built kernel 2.6.32.8 and pointed xen to that kernal, thinking
>>> > that it should come back with the new kernel after the reboot. Turns
>>> > out that is not the case. It did not boot correctly and did not show
>>> > any messages on the console too.
>>> >
>>> > Now, I am a bit confused about if my approach was in the right
>>> > direction or not.
>>> >
>>> > All I want to do is to run recent Xen (3.4.2) with the recent kernel 
>>> > (2.6.32.x).
>>> >
>>> > Can you please point me in the right direction?
>>> >
>>>
>>> Upstream Linux 2.6.32.8 kernel from kernel.org doesn't support
>>> running as Xen dom0. It only supports running as Xen domU (guest).
>>>
>>> You need to get the 2.6.31.6 kernel from Jeremy's git tree (xen/master 
>>> branch),
>>> it has dom0 support included.
>>>
>>> xen/next branch has 2.6.32 kernel.
>>>
>>> See:
>>> http://wiki.xensource.com/xenwiki/XenParavirtOps
>>>
>>> and:
>>> http://wiki.xensource.com/xenwiki/XenDom0Kernels
>>>
>>> -- Pasi
>>>
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.