similar to: Understanding error messages - bugs?

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, 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)

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

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

Hi, I''ve tried to do "xm save" on my Windows XP guest, which runs by ioemu. When I did this, #xm save 6 /xenimages/snapshot1 Error: /usr/lib/xen/bin/xc_save 10 19 6 0 0 0 failed xend.log: [2006-10-06 16:34:22 xend] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib/xen/bin/xc_save 10 19 6 0 0 0 [2006-10-06 16:34:23 xend] ERROR (XendCheckpoint:227) Couldn''t map

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

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 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

Hi... I have some difficulty to migrate a VM with Windows 2003 Server installed... I have two servers with DRBD as a Storage Server between this both servers. When I try migrate I get this error: [2010-05-05 11:32:15 3165] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 29 1 0 0 5 [2010-05-05 11:32:15 3165] INFO (XendCheckpoint:423) xc_save: failed to get the suspend evtchn port

Hello, i have two xen hosts servers configured to support migration of domus, but when i try to migrate, the command never ends, i can see on the remote server the machine with xm list but the machine is not accesible, and on the own server i see migrating-{machine_name} and i have access to it. Every server have one nic, with public ip (that is using with xenbr0), and i have a virbr0 configured

Hello, When I snapshot a vm( hvm centos ) the first time, it succeed. There is a snapshot file on disk and the vm is running. But when I do it the second time, it fail for timeout. what''s wrong with it? This error happened when I used xen-4.0.1-rc5 and kernel-2.6.31.13. Today I update to xen-4.0.1 and kernel-2.6.32.25, it is with the same wrong. Error message:

Hello, When I snapshot a vm( hvm centos ) the first time, it succeed. There is a snapshot file on disk and the vm is running. But when I do it the second time, it fail for timeout. what''s wrong with it? This error happened when I used xen-4.0.1-rc5 and kernel-2.6.31.13. Today I update to xen-4.0.1 and kernel-2.6.32.25, it is with the same wrong. Error message:

-----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)

Just wondering if this is a known bug? Trying to migrate the VM off to a diff dom0 results in the below error. Other VMs migrated off fine (started at around the same time as this vm) and I''ve tried a few different target servers, all resulting in the same thing. [2011-09-13 13:48:24 3996] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 29 77 0 0 1 [2011-09-13

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

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

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

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

Hi Sriram, Once again, thanks for your timely reply.... I tested as your suggesstion and i found that i don''t have any file in the location "/var/lib/xen" [root@globushead xen]# pwd /var/lib/xen [root@globushead xen]# ls -ll total 0 Further i tested the command "xm save " and results as follows Terminal 1: xm save -c TestVM1 TestVM1.chkpt