All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Ludvig <michal@logix.cz>
To: xen-devel@lists.xensource.com
Subject: Re: Porting 2.0.7 to newer linux kernel
Date: Wed, 01 Mar 2006 16:01:56 +1300	[thread overview]
Message-ID: <44050EA4.9070002@logix.cz> (raw)
In-Reply-To: <440424D3.50607@logix.cz>

Michal Ludvig wrote:
> Hi there,
> 
> I'm trying to port Xen 2.0.7 to a more recent kernels than the last 
> supported 2.6.12. Why? Because my server is far far away and I'm not 
> going to remotely upgrade Xen 2.0 to Xen 3.0 and then fly over there to 
> fix it. And after all it's a good coding excercise ;-)
> 
> Anyway, going in small steps, thus doing 2.6.13 first. After half a day 
> of work it finally compiles but an attempt to create domain with this 
> kernel ends up with "Error: Error creating domain: (0, 'Error')" and the 
> domain is still present in xm list:

All right, I got a little bit further. Now the domain gets successfully 
created but the kernel dies immediately:

~# xm create -c bobek-x2
Using config file "/etc/xen/bobek-x2".
Started domain bobek-x2, console on port 9608
************ REMOTE CONSOLE: CTRL-] TO QUIT ********

************ REMOTE CONSOLE EXITED *****************
~#

Could someone advise me where is the very first entry point in the 
kernel that gets executed once the domain is created? Since there is no 
useful content in arch/xen/boot I'm somehow lost as to where the kernel 
starts.

Thanks for any pointers!

Michal

  reply	other threads:[~2006-03-01  3:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 10:24 Porting 2.0.7 to newer linux kernel Michal Ludvig
2006-03-01  3:01 ` Michal Ludvig [this message]
2006-03-01 10:47   ` Keir Fraser

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=44050EA4.9070002@logix.cz \
    --to=michal@logix.cz \
    --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.