From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Miguel Clara <miguelmclara@gmail.com>
Cc: "port-xen@netbsd.org" <port-xen@netbsd.org>,
xen-devel@lists.xensource.com, chegger@amazon.de
Subject: Re: [Xen-devel] Fwd: Xen 4.3 Netbsd
Date: Thu, 23 May 2013 16:48:22 +0200 [thread overview]
Message-ID: <519E2C36.10500@citrix.com> (raw)
In-Reply-To: <CADGo8CUSqOdcroPzkap670Qycm2LW7VB0HhXRiGDdEbD0j3zTw@mail.gmail.com>
On 23/05/13 13:09, Miguel Clara wrote:
> I'm testing xen 4.3 on netbsd and I was able to build the kernel and
> tools successfully (after 2 minor fixes see more here:
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01482.html), I
> was also able to install the tools.
>
> However I'm getting a strange problem and I'm not sure even how to debug it...
>
> While booting with:
>
> menu=NetBSD Xen:load /netbsd.xen console=pc;multiboot /xen.gz dom0_mem=256M
>
> I get a very stange screen with something like:
>
> 08cF60 0000000000000000000d43...... (see attached screenshot, I have
> no other way to "copy it form the console")
>
> Seems to be hexa code.... no panic, no reboot, my guess is that the
> problem is wiht the Dom0 kernel, but this was the one I was using for
> xen-4.1 and xen-4.2, I was downloaded a new file
> (ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-6.1/amd64/binary/kernel/netbsd-XEN3_DOM0.gz)
> I wonder if this is not compatible with xen-4.3.
>
> I never saw this kind of error, I wonder if you add any luck booting?
>
> I've tried with netbsd 6.0.1 and them upgrade to 6.1, and get the same result!
You will have to setup a serial console in order to obtain a log,
without that it is impossible to say what's going on.
next prev parent reply other threads:[~2013-05-23 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADGo8CX=DuLKKvW2HZ0-hZx3k6YFTXKW3gRdUO=RidDVW8dLbA@mail.gmail.com>
2013-05-23 11:09 ` Fwd: Xen 4.3 Netbsd Miguel Clara
2013-05-23 14:48 ` Roger Pau Monné [this message]
2013-05-25 1:07 ` [Xen-devel] " Miguel Clara
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=519E2C36.10500@citrix.com \
--to=roger.pau@citrix.com \
--cc=chegger@amazon.de \
--cc=miguelmclara@gmail.com \
--cc=port-xen@netbsd.org \
--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.