$ git log -S xen_enable_nmi --source --all
commit ea9f9274bf4337ba7cbab241c780487651642d63 refs/tags/v3.16-rc6
Author: David Vrabel <david.vra...@citrix.com>
Date: Mon Jun 16 13:07:00 2014 +0200
x86/xen: no need to explicitly register an NMI callback
Remove xen_enable_nmi() to fix a 64-bit guest crash when registering
the NMI callback on Xen 3.1 and earlier.
It's not needed since the NMI callback is set by a set_trap_table
hypercall (in xen_load_idt() or xen_write_idt_entry()).
It's also broken since it only set the current VCPU's
callback.
Signed-off-by: David Vrabel <david.vra...@citrix.com>
Reported-by: Vitaly Kuznetsov <vkuzn...@redhat.com>
Tested-by: Vitaly Kuznetsov <vkuzn...@redhat.com>
** Package changed: ubuntu => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1350375
Title:
DomU crach on xen <3.2 due to NMI call
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Request from Amazon:
Our engineering team has reported that the kernel in 14.04 LTS is
making a call to NMI which in turn causes DomU instances to crash
under Xen <3.2. This affects only a particular range of kernel
versions from 3.12.25 to 3.15.6, and the kernel in 14.04 seems to be
3.14.x. There is already a patch in the mainstream kernel version to
apply that would address the situation. The probability of a DomU
crash with the current ubuntu 14.04 kernel on a Dom0 running Xen <3.2
is always. Our customers sometimes run on instance types that route
them to >3.2 Xen so this does not impact all customers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350375/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
