similar to: read extended-info signature failed

xen_changeset : Sun Apr 16 15:45:57 2006 +0100 9629:07408313ce33 /var/log/xend.log: [2006-04-19 20:42:09 xend] DEBUG (balloon:126) Balloon: free 1348; need 521; done. [2006-04-19 20:42:09 xend] DEBUG (XendCheckpoint:148) [xc_restore]: /usr/lib/xen/bin/xc_restore 11 20 42 133120 1 2 [2006-04-19 20:42:10 xend] ERROR (XendCheckpoint:227) xc_linux_restore start: max_pfn = 20800

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 first of all, thank you for a great project i really enjoy! ok, now here comes the bug report... i''m trying to test xen migration capabilities, with xen-3.1, hand compilled, fetched from mercurial repository. my setup looks like this - x86_64 dom0, x86_32p dom0, x86_32p domU. when trying to migrate from 64 to 32 bit dom0 i''m

I''m having issues with HVM live migration and every xen version I''ve tried - 3.0.1, 3.1.x, 3.3.0 and 3.3.1. Migrations will fail intermittently with messages like this on the receiving hypervisor: [2009-02-02 11:35:19 12629] DEBUG (XendCheckpoint:264) [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 4 2 3 1 1 1 [2009-02-02 11:35:19 12629] INFO (XendCheckpoint:403)

I encounter PV domain restore failure on r14770. Are you guys aware of this? ======================================================================== [2007-04-10 09:57:24 4664] DEBUG (balloon:113) Balloon: 754076 KiB free; need 65536; done. [2007-04-10 09:57:24 4664] DEBUG (XendCheckpoint:220) [xc_restore]: /usr/lib/xen/bin/xc_restore 24 4 1 2 0 0 0 [2007-04-10 09:57:24 4664] INFO

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

Hi I have a setup where I have an eth2 10GB interface setup a loop back between two dell 1950 servers. I have enabled VT in the bios. The eth0 interface is on a 1GB network. I am using an iscsi shared drive for the HVM image. I have followed the instruction provided in http://www.osrg.net/kemari/usage.html Now once everything is setup: After launching the HVM, I execute the following

Package: xen-utils-common Version: 3.2.0-2 Severity: normal When I was trying to migrate (xm migrate) a guest from one host to another, it simply fails. On the source host the virtual machine gets destroyed without any warning message - on the destination host I see the following error message in /var/log/xen/xend.log [2009-03-10 08:01:22 9846] ERROR (XendCheckpoint:52) read_exact: EOF trying

Hi all I get problem here when I try resume a vm. I do this: xm new VM xm start VM xm suspend VM Everything normal. No errors. But when I try resume the VM: xm resume VM I get this error: [2010-05-06 12:29:59 2040] ERROR (XendCheckpoint:357) /usr/lib/xen/bin/xc_restore 28 2 3 4 1 1 1 0 failed Traceback (most recent call last): File

Hi all I get problem here when I try resume a vm. I do this: xm new VM xm start VM xm suspend VM Everything normal. No errors. But when I try resume the VM: xm resume VM I get this error: [2010-05-06 12:29:59 2040] ERROR (XendCheckpoint:357) /usr/lib/xen/bin/xc_restore 28 2 3 4 1 1 1 0 failed Traceback (most recent call last): File

I have several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution

Hi, i do some tests with restoring HVM winxp-domU''s. Even, if i restore a saved DomU from a ramdisk, the Restoring-process has only a bandwidth about 23MB/sec: Here a example restoring an 512MB HVM opensuse10.3 DomU ...... [2008-05-07 22:40:12 3314] DEBUG (XendCheckpoint:218) restore:shadow=0x5, _static_max=0x20000000, _static_min=0x0, [2008-05-07 22:40:12 3314] DEBUG (balloon:132)

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 Severity: normal Tags: squeeze -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-i386 depends on

Hi, I''m running a two node xen-Cluster with CentOS 5.3. I''m using gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP for Dom0 (xen 3.0.3). Live migration works fine as long as the DomU guest is running CentOS 5.3 or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is running the current 2.6.9-78.0.17.EL.cern kernel, the migration

Hardware: Dell Poweredge R510 (32G ram, 8 CPU- Xeon) 64bit - xen 4.0.1 stable 64bit - 2.6.32.18 dom0 (.config attached) running Ubuntu 10.04 32 bit - 2.6.18.8 domU (.config attached) running ubuntu 8.04 domU has 3 tap2 disks, on lvm snapshots. domU has 2G mem, 2 VCPU workload on domU - ssh + top running, destroy domain -- This works . But, If i run a heavier workload say postgres db (just

Hi, Live migration was working well for me with 3.1. Recently I move to 3.2, and now live migration does not work anymore. Here is what i obtain on source node : ---- xm migrate --live webdav node2 Error: /usr/lib/xen-3.2-1/bin/xc_save 26 6 0 0 1 failed Usage: xm migrate <Domain> <Host> [...] ---- And in the xend.log (still on the source node) : ---- [2008-03-03 10:12:52 15205] INFO

hi, I have 2 servers running xen 3.2 on ubuntu 8.0.4.1 (64-bit) installed from the repositories (2.6.24-22-xen) with Intel-Quadcore CPU''s. The setup is based on http://www.asplund.nu/xencluster/xen-cluster-howto.html. I can start the domU (ubuntu 8.0.4.1 (64-bit)) on each server without problems. But when I start the live-migration with xm migrate dummy xen2 --live the migration

Hello everyone, for research purposes I''m working on Xen 3.0.3 and trying to make some modifications to Xen migration. By looking at the documentation, I''ve learned that the part I''m interesting in are handled by two binaries (xc_save and xc_restore), so I thought about modifying just this two binaries instead of recompiling the whole Xen everytime, so what I do is just

[PATCH 6/8] HVM save restore: guest memory handling Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> add support for save/restore HVM guest memory diff -r bb1c450b2739 tools/libxc/xc_hvm_restore.c --- a/tools/libxc/xc_hvm_restore.c Thu Jan 11 21:03:11 2007 +0800 +++ b/tools/libxc/xc_hvm_restore.c Thu Jan 11 21:05:45 2007 +0800 @@ -31,6 +31,40 @@ #include <xen/hvm/ioreq.h>

Hi all, I''m having some problem migrating a simple domU between two hosts. Short question: xm migrate (live or not) fails even though either host is capable of running the VM. Error seems to be: "not a valid guest state file: pfn count read" Long question: I have two boxes (devvmdevvmhost1 and devvmhost2) running xen 3.0.3 (RHEL 5), they are attached to a Dell MD3000 unit