similar to: Migration stalls with 2.6.26.5 kernel

Hi there, We are using latest version of XCP on 6 hosts. While issuing VM.start or VM.start_on xmlrpc functional call , it says : {''Status'': ''Failure'', ''ErrorDescription'': [''SESSION_INVALID'', ''OpaqueRef:cfb6df14-387d-40a1-cc27-d5962cba7712'']} However if I put VM.start in a loop maybe after

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

Trying to migrate a 64bit PV guest with 64GB running medium to heavy load on xen 3.4.0, it is showing lot of soft lockups. The softlockups are causing dom0 reboot by the cluster FS. The hardware has 256GB and 32 CPUs. Looking into the hypervisor thru kdb, I see one cpu in sh_resync_all() while all other 31 appear spinning on the shadow_lock. I vaguely remember seeing some thread on this while

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

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

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

Hi all, I am using Xen 4.0.0 on top of Ubuntu Lucid (amd64), with the Jeremy kernel taken from git (xen/stable-2.6.32.x branch, 2.6.32.12 when I am writing this email). This kernel is also used in my domu. I can save a domu without any problem, but restoring it may need from 2 to 5 minutes, from a 1G checkpoint file (domu has 1GB RAM). There also errors in /var/log/xen/xend.log :

Hi all, I am using Xen 4.0.0 on top of Ubuntu Lucid (amd64), with the Jeremy kernel taken from git (xen/stable-2.6.32.x branch, 2.6.32.12 when I am writing this email). This kernel is also used in my domu. I can save a domu without any problem, but restoring it may need from 2 to 5 minutes, from a 1G checkpoint file (domu has 1GB RAM). There also errors in /var/log/xen/xend.log :

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 got latest (13601) yesterday evening. This doesn''t seem to work to do Restore (at least of the Windows test-image that I''ve been using for testing previously). The VM restores reasonably OK, but it jumps to an invalid address shortly after restoring, giving a D1 blue-screen error (DRIVER_IRQL_LESS_OR_EQUAL), which turns out to be "page-fault in driver" after I

Hello again, now my xen works. But a strange thing: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2514 4 r----- 76.2 vx1 1 256 1 -b---- 6.1 vx2 2 256 1 -b---- 5.8 vx3 3 256 1 -b---- 5.3 vx4

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)

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, I am trying to see if the hypervisor can be used to detect deadlocks in the guest VMs. My goal is to detect if a guest OS is deadlocked, and if it is, then create a clone of the deadlocked OS without the locking condition, and letting the clone run. While the clone runs I am hoping to generate some hints that could tell me what caused the deadlock. I simulated a deadlock/hang

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

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: