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

Re: [Xen-devel] Kernel bug from 3.0 (was phy disks and vifs timing out in DomU)

On 26/08/2011 15:26, Konrad Rzeszutek Wilk wrote:
> On Thu, Aug 25, 2011 at 09:31:46PM +0100, Anthony Wright wrote:
>> Hi Konrad - any progress on this - it's a bit of a show stopper for me.
> What is interesting is that it happens only with 32-bit guests and with
> not-so fast hardware: Atom D510 for me and in your case MSI MS-7309 
> motherboard
> (with what kind of processor?). I've a 64-bit hypervisor - not sure if you
> are using a 32-bit or 64-bit.
> I hadn't tried to reproduce this on the Atom D510 with a 64-bit Dom0.
> But I was wondering if you had this setup before - with a 64-bit dom0?
> Or is that really not an option with your CPU?
The processor for the system I'm having problems with is an "AMD Athlon
II X2 250", I've attached the cpuinfo output. It's a 64 bit processor
that supports HVM. I run everything as 32 bit and use
paravirtualisation, so that I can work with a wide range of systems, so
we have a 32 bit Dom0 running 32 bit DomUs using paravirtualisation on a
64 bit processor that supports HVM.

As an experiment I've spent my day building a 64 bit dom0 kernel, which
I then discovered also needs a 64 bit Xen. I built a 64 bit Xen, but the
32 bit xen tools don't seem to want to work with the 64 bit xen, and at
that point things started going wrong since I trying to switch the
entire system to 64 bit is going to be very painful (all the xen tools,
all the libraries and all the other applications that rely on those
libraries). Is there a simple way to get the 32 bit xen tools to control
a 64 bit xen and dom0 kernel, or am I stuck?

Attachment: cpuinfo
Description: Text document

Xen-devel mailing list



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