[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Booting problem of Xen-4.0.1 on Fedora 13 using Intel chipset & processor
On Tue, Sep 21, 2010 at 10:38:41AM -0400, Konrad Rzeszutek Wilk wrote: > On Tue, Sep 21, 2010 at 07:34:11PM +0530, Jagadish Nadimpalli wrote: > > Hi, > > > > 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. > > Mr. Pasi, > > I think you might need to upgrade that source RPM. I remember Intel folks > posting > a patch for XSAVE and it broke some machines. There was a workaround, but I > don't remember > the details (post vacation amnesia :-). > Hehe. That's actually just a copy of the official Fedora src.rpm :) Michael: Do you feel comfortable with adding some bugfix patches from xen-4.0-testing.hg to fedora xen-4.0.1-2 rpms? I think at least earlier Fedora xen rpms had (extra) patches applied to fix bugs.. -- Pasi > > > > Thanks & Regards, > > Jagadish > > > > 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.6.33.3-85.fc13.x86_64. > > > > (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 Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |