From owner-freebsd-xen@freebsd.org  Mon May  9 11:12:32 2016
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14545B34F1C
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  9 May 2016 11:12:32 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 984B51EC8
 for <freebsd-xen@FreeBSD.org>; Mon,  9 May 2016 11:12:31 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49BCUBi097988
 for <freebsd-xen@FreeBSD.org>; Mon, 9 May 2016 11:12:31 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-xen@FreeBSD.org
Subject: [Bug 209327] Under XenServer 6.5 - Live Migration results in a
 Kernel Panic when the VM 'Lands' on the other Node
Date: Mon, 09 May 2016 11:12:31 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: royger@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209327-23905-D32pIfY2yx@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209327-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-209327-23905@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 11:12:32 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209327

Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |royger@freebsd.org

--- Comment #2 from Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> ---
Sadly I don't seem to be able to reproduce this using Open Source Xen on my
hardware.

I've sent a patch to update the FreeBSD version that's used for testing with
Open Source Xen to 10.3, the test cluster contains quite a lot of different
hardware, so it might be able to trigger it.

The crash itself looks quite weird, it seems to be caused by the IPIs that =
are
sent to CPUs in order to setup the PV timers (xentimer_resume). Also vector=
 30
is used to deliver security exceptions [0], which I don't even know how they
are triggered...

Anyway, will get back when I have more information about this.

[0] http://wiki.osdev.org/Exceptions

--=20
You are receiving this mail because:
You are the assignee for the bug.=