From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>
Subject: Re: pvops0 kernel 2.6.32.x still does not boot if x > 18, shouldn't that be fixed for release of Xen 4.0.2/4.1
Date: Mon, 21 Mar 2011 14:37:26 +0100 [thread overview]
Message-ID: <4D875496.7050807@hfp.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1103161435170.3382@kaball-desktop>
On 16.03.2011 15:36, Stefano Stabellini wrote:
>> sorry to be persistent, but the problem that pvops0 kernel 2.6.32.x
>> still does not boot if x> 18 on my machines (and on many other
>> machines, see this mailing list) is not solved yet.
>> Shouldn't this be a great focus of debugging and fixing?
>> What is the point of having releases for 4.0.2 or 4.1 if I don't have a
>> dom0 kernel?
>> The last time I tried it was with snapshot 892d2f052e97.
> can you try this simple patch please?
Yes, I can confirm that this patch seems to help. I tried snapshot
ea954f6 (current commit as of now). With the patch it does boot and
first runs of Xen VMs seem all OK. Without the patch it does not boot.
Is this the official fix? Any side-effects?
Regards Andreas
next prev parent reply other threads:[~2011-03-21 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 10:43 pvops0 kernel 2.6.32.x still does not boot if x > 18, shouldn't that be fixed for release of Xen 4.0.2/4.1 Andreas Kinzler
2011-03-14 11:48 ` Pasi Kärkkäinen
2011-03-15 10:26 ` Andreas Kinzler
2011-03-15 10:37 ` Pasi Kärkkäinen
2011-03-16 14:36 ` Stefano Stabellini
2011-03-21 13:37 ` Andreas Kinzler [this message]
2011-03-21 18:33 ` Stefano Stabellini
2011-03-16 22:23 ` sven
2011-04-12 17:03 ` Pasi Kärkkäinen
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=4D875496.7050807@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=jeremy@goop.org \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).