xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Louis Dupond <jean-louis@dupond.be>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Question about "xen: Revert commits da72ff5bfcb0 and 72a9b186292d"
Date: Tue, 04 Jul 2017 14:58:57 +0200	[thread overview]
Message-ID: <e79c0eb110b538b2e04550847ab69e17@dupond.be> (raw)
In-Reply-To: <f42ab765-c161-36e7-1e12-5bdb608a054c@suse.com>

Op 2017-07-04 14:51, schreef Juergen Gross:
> On 04/07/17 14:44, Jean-Louis Dupond wrote:
>> Hi Juergen,
>> 
>> We run Xen as dom0 with Windows domU's.
>> 
>> Now with older 4.9.x kernels, we had BSOD's when we booted a domU with
>> old Xen drivers in it.
>> With the newest kernel (4.9.34), this seems to be resolved.
>> 
>> I was wondering what caused this. And that patch triggered my 
>> attention :)
> 
> No, I don't think this patch can be the reason.
> 
> Which was the latest dom0 kernel causing failure? Or could it be you
> upgraded the hypervisor or Xen tools at the same time and the kernel
> version just doesn't matter?
> 
> 
> Juergen

We switched from 3.18 -> 4.9 (using CentOS VIRT), and started to see the 
issue.
If we just upgrade the kernel to latest 4.9, it works fine again.

So something broke it, but its fixed now ...
Was just wondering what caused it exactly :)

Jean-Louis

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-07-04 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 11:54 Question about "xen: Revert commits da72ff5bfcb0 and 72a9b186292d" Jean-Louis Dupond
2017-07-04 12:40 ` Juergen Gross
2017-07-04 12:44   ` Jean-Louis Dupond
2017-07-04 12:51     ` Juergen Gross
2017-07-04 12:58       ` Jean-Louis Dupond [this message]

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=e79c0eb110b538b2e04550847ab69e17@dupond.be \
    --to=jean-louis@dupond.be \
    --cc=jgross@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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).