similar to: patch pull request (to xen-4.0-testing)

# HG changeset patch # User Shriram Rajagopalan <rshriram@cs.ubc.ca> # Date 1302544427 25200 # Node ID fefe3359ab726e634c00704eadeacfcf30b70c07 # Parent 697ac895c11c6d5d82524de56796cee98fded2a5 remus: fix incorrect error handling for switch_qemu_logdirty in checkpoint code c/s 22275: "tools: cleanup domain save switch_qemu_logdirty callback" introduced a whole bunch of error code

Use PM_FREEZE, PM_THAW and PM_RESTORE power events for suspend/resume/checkpoint functionality, instead of PM_SUSPEND and PM_RESUME. Use of these pm events fixes the Xen Guest hangup when taking checkpoints. When a suspend event is cancelled (while taking checkpoints once/continuously), we use PM_THAW instead of PM_RESUME. PM_RESTORE is used when suspend is not cancelled. See

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

I noted a possible problem restoring a machine. In xc_domain_restore (xc_domain_restore.c) if it''s not the last checkpoint we set O_NONBLOCK flag (search for fcntl) that we can call pagebuf_get or just load other pages (see following "goto loadpages;" line). Now we could ending up calling xc_tmem_restore/xc_tmem_restore_extra (xc_tmem.c) which call read_extract (xc_private.c)

flight 10413 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10413/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 3 host-install(3) broken test-amd64-i386-win 8 guest-saverestore fail REGR. vs. 10201 test-i386-i386-win 8 guest-saverestore fail REGR. vs. 10201

flight 7341 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/7341/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 7285 build-amd64 4 xen-build fail REGR. vs. 7285 build-i386-oldkern 4 xen-build fail REGR. vs. 7285

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

flight 11929 xen-unstable running [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/11929/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl-qemuu-winxpsp3 <none executed> queued test-amd64-amd64-xl-qemuu-winxpsp3 <none executed> queued test-amd64-amd64-xl-qemuu-win7-amd64

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now

I have a IBM System x3600 series server with UEFI. I managed to compile the xen EFI (xen-4.2-unstable.efi). The machine is currently running Ubuntu with grub2. I can see a grubx64.efi in /boot/efi/EFI/ubuntu/grubx64.efi Where should I put the xen efi ? I tried creating a efi/EFI/xen/xen-4.2-unstable.efi and added it as a boot option using efibootmgr. All I get in that case is a blank screen. I

I tried to create a domain with drbd based disk as the backend "drbd:<resourcename>,..," and I get a "unknown disk type" error. I can spin out a patch if needed, but just wanted to know apriori if this was left out for any specific reason. shriram _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi All, I want to test REMUS over XEN, I would like to know the basic steps to be followed . I have installed xen4.1 on debian and i didn''t find any command related to remus, is there any steps which i have to carry out? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I''m doing my master research and I need to adapt remus code. Now... I wanna get the checkpoint size (memory + disk) on each period. Does someone know what function does this? I think some *fd *object''s function in remus code could just get the memory size. Does someone help me? Thanks _______________________________________________ Xen-devel mailing list

I noticed recently that there is no real easy way to get the kernel driver for blktap working in mainline. I''ve pulled down the source from Daniel Stodden''s linux git tree on xensource, but it looks like it''s for debian and I''m running Fedora 14, so I''m trying to sort it out. I run the 3.1.x kernel and don''t want to go back to the 2.6.32 that

F.Y.I >>> "Tian, Kevin" <kevin.tian@intel.com> 08.11.27. 11:50 >>>Sorry for a typo. I did mean domU instead of dom0. :-) The point here is that time_resume will sync to new system time and wall clock at restore, and thus pv guest should be able to continue... Xen system time is not wallclock time which just counts up from power up. As Keir points out, only its

I just did a ./configure and then make on a fresh debian 6.0 64-bit install. ./configure caught most of the missing dependencies except the following, which caused compilation failures. 1. libncurses5-dev (I get errors from tools/misc, concerning gtraceview) 2. bin86 & bcc & iasl - during firmware compilation 3. python-dev (from tools/python/xen/lowlevel/xc) I am not sure if I was doing

Hi, The following patch series fixes hangup after creating checkpoint on Xen. The Linux Xen guest can be saved the state to restore later, and also created snapshot like checkpoint via the hypervisor. But, when the snapshot is created for the PV guest, it will hangup. We added ''PMSG_CANCEL'' message and ''cancel'' handler in dev_pm_ops struct in the pm-linux

# HG changeset patch # User Bastian Blank <waldi@debian.org> # Date 1201284962 -3600 # Node ID 11b2e8baa6bf93b8ec4b3b4fe0256d2ce34f2699 # Parent 31adb5c972d03e45cb746cd2305126ea2571282f Use VPATH instead of symlinks for libelf inclusion into libxenctrl. Signed-off-by: Bastian Blank <waldi@debian.org> diff -r 31adb5c972d0 -r 11b2e8baa6bf tools/libxc/Makefile ---

Hi Ian,  Can you please backport the following Remus related patches: http://xenbits.xen.org/hg/xen-unstable.hg/rev/13ec53a59a42 http://xenbits.xen.org/hg/xen-unstable.hg/rev/29d81623dc14 http://xenbits.xen.org/hg/xen-unstable.hg/rev/b04e57ec4671 http://xenbits.xen.org/hg/xen-unstable.hg/rev/62c0dfc9efbf http://xenbits.xen.org/hg/xen-unstable.hg/rev/ecff559bf474

Le 24/09/2013 19:00, Thomas Goirand a ?crit : > Please don't think this way. > > I work daily on 79 packages to maintain OpenStack in Debian: > > http://qa.debian.org/developer.php?login=openstack-devel at lists.alioth.debian.org If you go that way, I could say that you're blocking my work on 214 packages in Debian: