From: Yasir Assam <mail@endlessvoid.com>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6
Date: Fri, 12 Mar 2010 13:22:31 +1100 [thread overview]
Message-ID: <4B99A567.8060400@endlessvoid.com> (raw)
In-Reply-To: <226923.49277.qm@web56105.mail.re3.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1927 bytes --]
I don't know what you mean by "load 2.6.32.9 required CS back ported"
Yasir
> Try the most recent 3.4.3 and load 2.6.32.9 required CS back ported.
>
> --- On *Thu, 3/11/10, Yasir Assam /<mail@endlessvoid.com>/* wrote:
>
>
> From: Yasir Assam <mail@endlessvoid.com>
> Subject: Re: [Xen-devel] current xen/stable 2.6.32.9 failed
> upgrade from 2.6.31.6
> To: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Thursday, March 11, 2010, 6:25 PM
>
> I had this problem too a couple of days back (2.6.32.9 dom0 on Xen
> 3.4.2 - screen blank on boot). I didn't try 3.4.3rc3 but went
> straight to 4.0.0-rc6 and it booted ok.
>
> Yasir
>> On Mon, Mar 08, 2010 at 03:16:15PM -0800, Jeremy Fitzhardinge wrote:
>>
>>> On 03/07/2010 03:31 PM, Josip Rodin wrote:
>>>
>>>>> but when you update the dom0 kernel to current xen/master 2.6.31.6, it crashes?
>>>>>
>>>>>
>>>> When I update it to current xen/stable 2.6.32.9. (I put that bit in the
>>>> subject only, sorry.)
>>>>
>>> So 2.6.31.6 is OK on the 3.4.3rc3? It's just the new dom0 which fails?
>>>
>> Yes.
>>
>> (Sorry for the delay in further testing, I'm still waiting for users to
>> ACK a new downtime.)
>>
>>
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG -www.avg.com
>> Version: 9.0.733 / Virus Database: 271.1.1/2731 - Release Date: 03/09/10 06:33:00
>>
>>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> </mc/compose?to=Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2736 - Release Date: 03/11/10 18:33:00
>
>
[-- Attachment #1.2: Type: text/html, Size: 3903 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-12 2:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100306115833.GA28039@orion.carnet.hr>
[not found] ` <20100306132711.GK2580@reaktio.net>
2010-03-07 23:31 ` current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6 Josip Rodin
2010-03-08 23:16 ` Jeremy Fitzhardinge
2010-03-09 9:01 ` Josip Rodin
2010-03-11 23:25 ` Yasir Assam
2010-03-11 23:40 ` Boris Derzhavets
2010-03-12 2:22 ` Yasir Assam [this message]
2010-03-12 7:14 ` Pasi Kärkkäinen
2010-03-12 11:28 ` Boris Derzhavets
2010-03-12 21:41 ` Yasir Assam
2010-03-11 15:08 ` Josip Rodin
2010-03-11 19:24 ` Pasi Kärkkäinen
2010-03-12 11:41 ` Josip Rodin
2010-03-12 12:09 ` Josip Rodin
2010-03-23 23:18 ` Josip Rodin
2010-03-23 23:22 ` Josip Rodin
2010-03-24 5:10 ` Jeremy Fitzhardinge
2010-03-24 8:37 ` Josip Rodin
2010-03-12 13:02 ` 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=4B99A567.8060400@endlessvoid.com \
--to=mail@endlessvoid.com \
--cc=bderzhavets@yahoo.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 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.