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] read extended-info signature failed

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] read extended-info signature failed
From: Juan <cavallaro.juan@xxxxxxxxx>
Date: Mon, 11 Apr 2011 16:54:39 -0300
Delivery-date: Mon, 11 Apr 2011 12:55:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=eXeTE8hrE3ttfC61orI6do/eBX7ebG9P/YLtJD2pvJA=; b=gjIZpJ9lWtcX510HUj0pZbb2VRv34Oj31mWyr9I0SqTKvZ77mex4/7NWz8VX5b9d++ A4nH1HAvWeELjFBlZd94MBjtRxHxoenW+nAYp3zeltwd13c3cssaLNMCnYZN9LdurubA MTQKk+c+Hexz4E2LcXRjnR6T7z1sMmowUioTQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=x/SJr8msTCaEHO1WNSA7W69HlrTOnA17X3DMoFhQbntx8mGchU7QhJJV/5+2C4+EOo 1NuoDZ8Gv/BzG18MDZW8JsBNSVF82m3+eheEMJwA2dLlNcJi80K34BuYdyKR9VmbHieH h66yKrhFjZGD0LOFMDPisvU++Mc2zG+oz1lLM=
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 am new to the list although not really new to Xen - I would like to shoot you a quick one regarding the following message logged on xend.log:

DEBUG (XendCheckpoint:200) restore:shadow=0x0, _static_max=0x201, _static_min=0x201,
DEBUG (balloon:145) Balloon: 29722616 KiB free; need 525312; done.
DEBUG (XendCheckpoint:217) [xc_restore]: /usr/lib64/xen/bin/xc_restore 22 2 1 2 0 0 0
INFO (XendCheckpoint:353) xc_domain_restore start: p2m_size = 20900
INFO (XendCheckpoint:353) ERROR Internal error: read extended-info signature failed
INFO (XendCheckpoint:353) Restore exit with rc=1
DEBUG (XendDomainInfo:2189) XendDomainInfo.destroy: domid=2
ERROR (XendDomainInfo:2198) XendDomainInfo.destroy: xc.domain_destroy failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2194, in destroy
Error: (3, 'No such process')

I have traced back the error to the following code snippet in tools/libxc/xc_linux_restore.c file ~ this is Xen 3.0.3, included in RHEL 5.5:

    /* Read first entry of P2M list, or extended-info signature (~0UL). */
    if (!read_exact(io_fd, p2m_frame_list, sizeof(long))) {
        ERR("read extended-info signature failed");
        goto out;

However, I am not sure under what circumstances that _expression_ could return false & trigger the error message. Any hint will be greatly appreciated!



Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] read extended-info signature failed, Juan <=