Hi,
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
xc.domain_pause(self.domid)
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!
Thanks!
--
Juan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
