similar to: [PATCH] Janitorial work on xc_save.c

While doing migration, sometimes found suspend lock file was not unlinked in previous operations, then there is an obsolete lock file in place, which causes the current and later migration cannot get lock. That happens seldomly but do happen. After checking the source code, I found there are some places that potentially cause lock file unlinked, including: 1) in lock_suspend_event() function,

I want to add some parameters when vm is migrated. As I can see , vmm will use xc_domain_save(tools\libxc\Xc_domain_save.c) function ,and the main function of xc_save.c is responsible for inputting parameters. so I just want to know which function will use this executable file. Thanks Min Li School of Computer Science and Technology Cluster and Grid Computing Lab Services Computing Technology

stubdom: add v?errx? and v?warnx? functions Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 14a9a1629590 extras/mini-os/include/posix/err.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/extras/mini-os/include/posix/err.h Wed Aug 27 10:29:36 2008 +0100 @@ -0,0 +1,15 @@ +#ifndef _POSIX_ERR_H +#define _POSIX_ERR_H + +#include <stdarg.h> + +void err(int eval,

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1300271932 0 # Node ID 7e326d27d899a3133479c8b7c983f660cdeda48c # Parent f35234b6636a0410a7d5eaa409e98ebe59080e4f tools: do not link against unused libraries. A fair few things under tools link against libraries which they don''t even use. Most of this appears to come from copy-and-pasting previous Makefile

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The vast majority of the code is in second patch. The first patch merely changes the xenstore key name used by hvmloader to store the buffer address.

Commit-ID: d2762f07df57add3d11f50d7d20c33557303c606 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d2762f07df57add3d11f50d7d20c33557303c606 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 16:06:51 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] [BUILTIN] Use error

Commit-ID: e9dff9389660fcfca586051edc7aba890f74882e Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e9dff9389660fcfca586051edc7aba890f74882e Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 16:06:51 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: [BUILTIN] Use

Hi all, I need to make some modifications to xc_save and xc_restore to Xen 3.0.3 for research purposes. In order to avoid to recompile all the xen source at each modification I do to these binaries, I thougt to substitute the version of this two binaries which is installed in /usr/lib64/xen/bin, with a version I compile myself from the Xen source code tarball. The problem is that after doing

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when

Hi All, Does anybody have this problem when try to migrate DomU : Error: /usr/lib/xen/bin/xc_save 22 6 0 0 0 failed I use xen 4.2.2-pre compiled from sources and my machine is Ubuntu 12.04 Linux with kernel 3.2.0-29-generic. Its working perfectly, even remus with drbd support migration was running successfully before. However today after I kill the remus process with command pkill -USR1 remus

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** When live migrating a PV guest from one Lenny dom0 to another, the migration fails with the following error: libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err '/usr/lib/xen-3.2-1/bin/xc_save 28 39 0 0 1 failed') The kernel messages

# HG changeset patch # User john.levon@sun.com # Date 1161090738 25200 # Node ID 74d0bc37ec06da88b0c38a1c34c8cc95bc28bdbd # Parent 7a86cb5bb6b6e9164bec378b5fb0a270625a2452 A couple of simple compile fixes for tools/ on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/config/Linux.mk b/config/Linux.mk --- a/config/Linux.mk +++ b/config/Linux.mk @@ -21,6 +21,7 @@

got the same probleme here his somebody working on this issue ? -- Gomes do Vale Victor Cellectis SA Ingenieur Syst?mes et D?veloppements email: victor.gomes at cellectis.com Tel: 01 41 83 99 42 Fax: 01 41 83 99 03

Commit-ID: ff52f9cbec8aa6ef0c1fc4e07e8b947c41d643cf Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ff52f9cbec8aa6ef0c1fc4e07e8b947c41d643cf Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Tue, 20 Nov 2018 10:09:26 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: eval: Use

plain text document attachment (lguest64-loader.patch) I noticed that the lguest loader code for i386 was in Documentation/lguest. Well, that's fine (I guess) but it can't just be for i386. So I made a separate directory to put the loader code in. So now we have: Documentation/lguest/i386/... for the lguest i386 loader. and Documentation/lguest/x86_64/... for the lguest x86_64

plain text document attachment (lguest64-loader.patch) I noticed that the lguest loader code for i386 was in Documentation/lguest. Well, that's fine (I guess) but it can't just be for i386. So I made a separate directory to put the loader code in. So now we have: Documentation/lguest/i386/... for the lguest i386 loader. and Documentation/lguest/x86_64/... for the lguest x86_64

From: Rusty Russell <rusty@rustcorp.com.au> A brief document describing how to use lguest. Because lguest doesn't have an ABI we also include an example launcher in the Documentation directory. [jmorris@namei.org: Fix up nat example in documentation] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Signed-off-by: James Morris

From: Rusty Russell <rusty@rustcorp.com.au> A brief document describing how to use lguest. Because lguest doesn't have an ABI we also include an example launcher in the Documentation directory. [jmorris@namei.org: Fix up nat example in documentation] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Signed-off-by: James Morris