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] issue moving guest from 3.2 to 4.01

To: Xen-Users List <xen-users@xxxxxxxxxxxxxxxxxxx>, Xen-Devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] issue moving guest from 3.2 to 4.01
From: chris <tknchris@xxxxxxxxx>
Date: Wed, 22 Dec 2010 13:59:40 -0500
Delivery-date: Wed, 22 Dec 2010 11:01:08 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=qN3R6qdubdW8QexXRnFiYH49LM/VexiOcfJHZjRcvV4=; b=xK2D3CqL6O/GnIS1ZRj/iAoJsNnR3nNLdsrKvqsOtlBHq8IHQl0q0hKfyspE6oUxT5 reoJzH8+yH+g7oWUX7+bjad6eIGcaTtS7fIqQU0th6tszSsfOqrN3BPEoDJ6ruqKhpug d3qSGYpfp7dvFlC431ZiUlR4NjN863tlWjiR4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tBVR4OgLh6k7s3gVQyr0KNMgaRKnDZPCz+s/akHY0NazM7Qlf9bZhQKbHF6f1Dw56k JWgz/KKrNwIm4/uOW52S46o9hx4dDE2MjT8+thZFSzYcWlRmqEl2T/ZxyTlzqg5DByKS dmXl4kBZuwZ5a99E6Phhjz17W8waIRN/cXGgc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I have a pv linux guest which works perfectly on 3.2 and when I moved
the guest to the new server (debian squeeze, xen 4.0.1) I cannot start
it, I get the following error:

# xm create vm-customer.cfg
Using config file "./vm-customer.cfg".
Error: (1, 'Internal error', 'launch_vm: SETVCPUCONTEXT failed (rc=-1)\n')

here is my domain config:


I assumed that it was due to the domU kernel not being compatible with
the hypervisor so i replaced them with the domU kernel from squeeze
but I still get the same error.
A quick google returns a post about someone starting 100 domains and
this occuring on the 101st domain, however in this case this is the
first vm im putting on this machine so I don't think it is related.

Has anyone had this issue? Any idea how I can debug this? I tried
setting vcpus=1 and cpus=1 just to see if it wanted those directives
but it doesnt seem to make any difference

Xen-devel mailing list