From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Constantin Dunayev <constantin_@list.ru>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: RHEL (CentOS, Oracle Liux) kernel 2.6.32-358 does not start at XCP
Date: Thu, 7 Mar 2013 14:39:24 +0000 [thread overview]
Message-ID: <5138A69C.6090902@citrix.com> (raw)
In-Reply-To: <20130307141348.GY8912@reaktio.net>
On 07/03/13 14:13, Pasi Kärkkäinen wrote:
> On Thu, Mar 07, 2013 at 02:26:10PM +0400, Constantin Dunayev wrote:
>> Hi, everyone,
>> Two days ago I have filed a bug to Red Hat
>> [1]https://bugzilla.redhat.com/show_bug.cgi?id=918239
>>
> That bug is marked as private, so it's not visible to other people.
>
>> The problem is, that new RHEL-6.4's kernel 2.6.32-358 does not start at
>> HVM on Xen Cloud Platform 1.6 (maybe, also affected XenServer 6.1)
>> I have tested kernels -358 from CentOS, Oracle and -356 from Red Hat both
>> i686 and x86_64 at 2 different server hardware
>> The sympthoms: kernel does not boot at all, does not produce any log;
>> previous (all 2.6.32-279 and 2.6.32-220), and Oracle's kernel-uek work
>> perfectly.
>>
>> Andrew Jones from Red Hat advised me to ask, does anybody else have this
>> issue?
>>
> Did you try booting the domU kernel with "earlyprintk=xen console=hvc0" cmdline options?
>
> -- Pasi
Or alternatively, start with pause-on-crash, and use xenctx with the
appropriate symbol table.
~Andrew (who also unable to view the bug ticket)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-03-07 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 10:26 RHEL (CentOS, Oracle Liux) kernel 2.6.32-358 does not start at XCP Constantin Dunayev
2013-03-07 14:13 ` Pasi Kärkkäinen
2013-03-07 14:39 ` Andrew Cooper [this message]
2013-03-07 14:46 ` Pasi Kärkkäinen
2013-03-08 12:08 ` Andrew Jones
2013-03-08 12:28 ` Andrew Jones
2013-03-08 12:55 ` Pasi Kärkkäinen
2013-03-08 15:36 ` Andrew Cooper
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=5138A69C.6090902@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=constantin_@list.ru \
--cc=pasik@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.