This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH] [LIBXC] Getting extended VCPU context fails (on x86-

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [LIBXC] Getting extended VCPU context fails (on x86-64)
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Tue, 27 Nov 2007 00:28:47 -0500
Delivery-date: Mon, 26 Nov 2007 21:29:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
With cs16462 migration fails on x86-64 due to libxc not being able to
retrieve the extended VCPU context. The size identifier of the structure
is not initialized and xen refuses to give the context in
xen/arch/x86/domctl.c line 712.

I am not entirely sure whether this size identifier should be surrounded
by #ifdefs for x86 and x86-64?

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Attachment: libxc_ext_vcpucontext_size.diff
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] [LIBXC] Getting extended VCPU context fails (on x86-64), Stefan Berger <=