[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1219693601.27921.172.camel@localhost.localdomain>
Date: Mon, 25 Aug 2008 20:46:41 +0100
From: Ian Campbell <ijc@...lion.org.uk>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Sally-Anne Edwards <sallyanne.edwards@...glemail.com>,
linux-kernel@...r.kernel.org
Subject: Re: Fwd: domU lenny not working: BUG: unable to handle kernel
paging request at e7437cc0
On Mon, 2008-08-25 at 12:35 -0700, Jeremy Fitzhardinge wrote:
> I haven't see this oops before, but I think the code in question
> correlates to:
>
> bret = RING_GET_RESPONSE(&info->ring, i);
> id = bret->id;
> req = (struct request *)info->shadow[id].request;
>
> which suggests the backend driver is passing back a bogus request ID.
>
> What's your host environment?
I believe it's a 64 bit Etch kernel running on a Lenny domain 0. I
wonder if that kernel doesn't write the protocol field in xenstore so
the 64 bit backend Sally-Anne is using cannot talk to the 32 bit
frontend correctly.
Sally, can you run xenstore-ls on the domain's path
(/local/domain/<domid>). Is there a protocol field in the vbd entry?
If not can you try starting the domain in the paused state (xm create
-p) and use xenstore-write to fill in the protocol node in the frontend
to "x86_32-abi". e.g.
xenstore write /local/domain/<domid>/device/vbd/<nr>/protocol x86_32-abi
before unpausing.
I thought the tools did this (so expected the Lenny tools to be correct)
but looking at the code it seems it is the domain 0 kernel which does
it.
Ian.
--
Ian Campbell
Success is getting what you want; happiness is wanting what you get.
Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)
Powered by blists - more mailing lists