This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Booting problem of Xen-4.0.1 on Fedora 13 using Intel ch

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Booting problem of Xen-4.0.1 on Fedora 13 using Intel chipset & processor
From: Jagadish Nadimpalli <jagadish.nadimpalli@xxxxxxxxxxxxxxxxxx>
Date: Tue, 21 Sep 2010 19:34:11 +0530
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 21 Sep 2010 07:04:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100921134340.GB28556@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimQZGhtLA-FFbLPLPo-BUbB0wcKwqi4nWAa7E8t@xxxxxxxxxxxxxx> <20100921134340.GB28556@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I have taken the hypervisor using "wget http://pasik.reaktio.net/fedora/xen-4.0.1-1.fc14.src.rpm". I think it is latest version.

Thanks & Regards,

On Tue, Sep 21, 2010 at 7:13 PM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
On Tue, Sep 21, 2010 at 09:47:40AM +0530, Jagadish Nadimpalli wrote:
> Hi,
> I am facing a problem in booting Xen-4.0.1 on Fedora 13. The Xen RPM
> installation is successful but when I try to boot from DOM0 Kernel, it
> fails. Other details of my machine are as follows.
> (1) Kernel version
> (2) Chipset - Intel 82Q35
> (3) Processor - Intel Core2 Duo CPU E8400 @ 3.00GHz
> The error and the call trace are as follows.
> Xen call trace
> ==========
> xsave_init + 0x6d/0x1f0

I think that got fixed in the latest hypervisor - is there an updated version of the Xen RPM?
Where did you get the Xen RPM from?

Xen-devel mailing list