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:44:10 +0200	[thread overview]
Message-ID: <e93748857942d5adc9867b655fd20dc2@dupond.be> (raw)
In-Reply-To: <26892804-d3a3-8b53-ee3c-4f1fa800977d@suse.com>

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 
:)

Thanks
Jean-Louis

Op 2017-07-04 14:40, schreef Juergen Gross:
> On 04/07/17 13:54, Jean-Louis Dupond wrote:
>> Hi All,
>> 
>> We had some issues with BSOD's on Windows at startup when using some 
>> old
>> Xen drivers inside Windows.
>> Now when we upgrade to the most recent 4.9.x kernel. The issue seems 
>> to
>> be resolved.
>> 
>> Could it be that the following commit fixes the issue:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d582d236dc1f9085e741affc72e9ba061a67c2
>> 
>> ?
>> 
>> As far as I can see it only breaks Xen < 4.0. But could it be it also
>> breaks Windows VM's with old Xen drivers?
> 
> Umm, I don't get it.
> 
> Are you using Windows or Linux? Above commit is for the Linux kernel
> running as HVM domain. It shouldn't be able to modify behavior of a
> Windows guest at all.
> 
> 
> Juergen

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

  reply	other threads:[~2017-07-04 12:44 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 [this message]
2017-07-04 12:51     ` Juergen Gross
2017-07-04 12:58       ` Jean-Louis Dupond

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=e93748857942d5adc9867b655fd20dc2@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).