All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Julio C. Ortega" <jortega@onuva.com>
To: xen-devel@lists.xensource.com
Subject: Re: Problems with Xend on ia64.
Date: Thu, 10 Feb 2011 18:16:18 -0430	[thread overview]
Message-ID: <4D546ABA.10107@onuva.com> (raw)
In-Reply-To: <20110126112506.14232f3p04bca5s0@correo.onuva.com>


[-- Attachment #1.1: Type: text/plain, Size: 3853 bytes --]

El 26/01/11 11:25, Julio C. Ortega wrote:
> Hello all.
> 
> As per my last emails to the list i was able, (thanks Shin'ya) to build
> Xen 4.0.1 (and 4.0.2-rcX) on ia64.
> 
> After a long battle building various releases (all pertaining 4.0.x
> series) on a BL870c Integrity blade (itanium2) i cannot make Xend run
> (kernel 2.6.18.8-xen boots normally and without errors, apparently) but
> Xend gives out permission errors. (Like the build was more recent than
> the tools and etc.) believe me, i've rebuilded tools, kernes, stubdom,
> uninstalled, built from scratch, reinstalled....  you name it so as to
> prevent this permission error without results.
> 
> I've struggling digging info on how to sucessfully make Xend start, so
> far i've tried literally everything i've found, al also digged heavily
> in this list archives.
> 
> I've trying in two different systems (one has debian 6.0 and other
> debian 5.0),im building with gcc-4.1 in both of them, and the build
> completes _normally_ and _without errors_ after i apply the patches that
> Shin'ya and other contributors have posted for ia64 on 4.0.1 and 4.0.2-rcX
> 
> I'll attach the running kernel dmesg, and the xend.log. Also, an strace
> of xend starting.
> 
> (disregard the qla2xxx messages, as i have to reorganize the storage and
> enclosure after Xen works ;) )

Hello again folks.

Continuing on this work, i had to consider building 3.4.

3.4 release stable didn't work also builded fine, and all, but have to
consider building other so, i followed this HOWTO[1] and it builded fine
(3.5 from ia64-unstable) , but the "Permission Denied" error changed
somewhat, i'll post it:


[2011-02-10 17:11:18 4150] INFO (SrvDaemon:332) Xend Daemon started
[2011-02-10 17:11:18 4150] INFO (SrvDaemon:336) Xend changeset: Mon Jun
29 11:26:05 2009 +0900 19848:5839491bbf20.
[2011-02-10 17:11:18 4150] ERROR (SrvDaemon:349) Exception starting xend
((13, 'Permission denied'))
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
1014, in instance
    inst = XendNode()
  File "usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line 92,
in __init__
    self.other_config["xen_pagesize"] = self.xeninfo_dict()["xen_pagesize"]
  File "usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line 940,
in xeninfo_dict
    return dict(self.xeninfo())
  File "usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line 883,
in xeninfo
    info['xen_scheduler'] = self.xenschedinfo()
  File "usr/lib/python2.5/site-packages/xen/xend/XendNode.py", line 873,
in xenschedinfo
    sched_id = self.xc.sched_id_get()
Error: (13, 'Permission denied')
[2011-02-10 17:11:19 4149] INFO (SrvDaemon:220) Xend exited with status 1.

Dom0 boots with 2.6.18.8-xen, no apparent errors, but the xend daemon
fails to start. Any pointers would be greatly appreciated.

This is an ia64 build on Debian 5.0.8 'lenny' with GCC 4.1.2

[1]: http://www.gelato.unsw.edu.au/IA64wiki/PaulDavies/XenIA64Howto


-- 
------------------------------------
Julio C. Ortega
ONUVA
http://www.onuva.com


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  parent reply	other threads:[~2011-02-10 22:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 15:55 Problems with Xend on ia64 Julio C. Ortega
2011-01-26 16:31 ` Pasi Kärkkäinen
2011-01-26 16:56   ` Julio C. Ortega
2011-01-26 17:05     ` Pasi Kärkkäinen
2011-01-26 18:31       ` Julio C. Ortega
2011-01-26 16:58   ` Julio C. Ortega
2011-02-10 22:46 ` Julio C. Ortega [this message]
2011-02-11  8:38   ` Pasi Kärkkäinen
2011-02-11 20:59     ` Julio C. Ortega
2011-02-11 21:22       ` Dan Magenheimer
2011-02-11 21:45         ` Julio C. Ortega
2011-02-14  4:55 ` KUWAMURA Shin'ya
2011-02-14 13:31   ` Julio C. Ortega
2011-02-15  8:32     ` KUWAMURA Shin'ya
2011-02-15 12:34       ` Julio C. Ortega

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D546ABA.10107@onuva.com \
    --to=jortega@onuva.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.