similar to: Live migration problem with xen 3.2

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

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:

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

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

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 folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

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

Dear all: I am trying to migrate a WinXP HVM (64M memory) from a machine (sender) to another machine (receiver) through AoE disk, however, there are some errors when do the following command: (My xen version is xen-4.0.1-rc5.hg, kernel 2.6.31.13, xen xen-4.0.1-rc6-pre, Both sender and receiver are the same xen version) xm migrate --live domain_id receiver_ip

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 been struggling through the task of moving our infrastructure over to Xen VMs. We were initially using Ubuntu packages for both dom0 and our domUs, but experienced extreme instability so we moved to CentOS, which has been much more reliable for dom0. Since we already had a bunch of Ubuntu VMs, we left them using the Ubuntu 2.4.24-19-xen kernel, but this has turned out to be

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)

-----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 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 have three Xen hosts running Xen 4.0.2 (OpenSuSE 11.4 based). I also have one ''NFS'' server with an NFS export holding VM images and configuration files. Each host has a dedicated LAN link directly to the NFS server. I have another separated NFS export for VM locking (but I had the same issues before). When I attempt to live migrate a VM, it *looks''*like

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

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''ve just uploaded 0.9.11-pre12 of the GPL PV drivers for Windows. Since -pre10 (and -pre11) I''ve fixed a heap of crashes that were plaguing xennet under load, and also rewritten the interrupt/event distribution logic to improve performance. Under windows 2003 I can now get network speeds of 1-2Gbit/second TX and 600Gbit/second RX, which is considerably better than I was

I''ve just uploaded 0.9.11-pre12 of the GPL PV drivers for Windows. Since -pre10 (and -pre11) I''ve fixed a heap of crashes that were plaguing xennet under load, and also rewritten the interrupt/event distribution logic to improve performance. Under windows 2003 I can now get network speeds of 1-2Gbit/second TX and 600Gbit/second RX, which is considerably better than I was

>/ On Mon, 2007-12-10 at 22:34 +0000, Karanbir Singh wrote: />>/ Just wondering if people had started using i386 Xen DomU's on a x86_64 />>/ dom0 machine with 5.1 as yet ? And just wondering what their experiences />>/ have been. /I thought I would chime in here with my experience. I am running a Cent5.1 x86_64 Dom0 with a Cent 5.1 x386 domU (both fully updated).