similar to: [PATCH] Rename libxc => libxenctl

Hello, When statically linking the following program: #include <stdio.h> #include <xenctrl.h> #include <xenguest.h> int main(void) { printf("%p\n", xc_domain_resume); printf("%p\n", xc_domain_save); return 0; } gcc -static test.c -o test -lxenguest -lxenctrl -lpthread -lz we get

Hi Ewan/Alistair, I have a patch that looks like this: diff -r a39ad4c78850 tools/libxc/xenctrl.h --- a/tools/libxc/xenctrl.h Wed Aug 30 13:51:12 2006 +0100 +++ b/tools/libxc/xenctrl.h Wed Aug 30 15:11:20 2006 -0500 @@ -416,6 +416,10 @@ int xc_domain_memory_populate_physmap(in unsigned int address_bits, xen_pfn_t

Hi, I''m playing with the builders in libxc. I am having trouble debugging the thing. I was wondering what options I have. - When I run ''xm create'', what process calls down to the xc_builder stuff? Can I attach to it with gdb? - Is there any way to spit out debug output (printf?)? Where would it go? - If I make changes and do a make install in

Source: xen-api Version: 1.3.2-15 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/?PKGBUILDDIR?' > omake phase1 > omake: Symbol `FamErrlist' has different size

Hello, c/s 17138 introduced the use of VPATH instead of symlinks to access to libelf files. However, that not only provides access to .c files, but also to .o files. That means that if one compiles the hypervisor before the tools, libxenguest.a contains .o files intended to the hypervisor, containing references to printk, etc. and thus is unusable. Is there a good reason against reverting to

libxc: Use vcpu_guest_context_any_t instead of two pages Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 14a9a1629590 tools/libxc/xc_dom_boot.c --- a/tools/libxc/xc_dom_boot.c wed aug 27 10:26:50 2008 +0100 +++ b/tools/libxc/xc_dom_boot.c wed aug 27 12:07:28 2008 +0100 @@ -187,7 +187,7 @@ int xc_dom_boot_image(struct xc_dom_imag int xc_dom_boot_image(struct

Thanks. I have already previewed the xenctrl.h. The following is what I understand: libxc is compiled to a file name after 'xc**' endding with '.so', xend communicates with domain0 through xc and domain0 communicates with hypervisor through privcmd. What's the privcmd? ------------------ 原始邮件 ------------------ 发件人: "Wei

xc_dom_alloc_segment requires start address to be page align. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index ffe575b..366061d 100644 --- a/tools/libxc/xc_dom_arm.c +++ b/tools/libxc/xc_dom_arm.c @@ -290,6 +290,8 @@ int

Thanks, I'll take a look at this. Mike On Sat, Jun 1, 2013 at 12:28 AM, David Su?rez <david.sephirot at gmail.com>wrote: > Source: xen-api > Version: 1.3.2-15 > Severity: serious > Tags: jessie sid > User: debian-qa at lists.debian.org > Usertags: qa-ftbfs-20130529 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages

Hi, I just had a try using the xeno-unstable. When I used the xc_dom_create.py to create a new domain I got the followings: ============================================== Traceback (most recent call last): File "/usr/bin/xc_dom_create.py", line 332, in ? (current_id, current_port) = make_domain() File "/usr/bin/xc_dom_create.py", line 238, in make_domain

On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up

Hi Mukesh, I was auditing uses of set_xen_guest_handle for correctness when I noticed that gdbsx (specifically tools/debugger/gdbsx/xg/xg_main.c) defines its own _domctl_hcall and associated helpers instead of using libxc. Is there any particular reason for that? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi! There''s a include path mistake when trying to build tools/libxc on OpenBSD: gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -D__XEN_TOOLS__ -Werror -fno-strict-aliasing -I. -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c In file included from xc_private.h:18, from xg_private.h:16,

Hi, I''m trying to test some changes of mine to libxc and python/xc.c, does it requires a boot any time I''m trying to test them? What are your development practices? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am trying to write a script to handle setup of domains using virtual block devices for their root FS and have been unable to get the virtual devices to work with any sort of consistency. This is using xen-1.1.bk on Redhat 7.3 (I had to rebuild all the tool binaries to run on 7.3). Anyway, I would first like to make sure I am using the vd/vbd stuff correctly. Here is an example of the problem I

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

Hi, libxc contains the following function which is used when uncompressing zipped kernel images: /* ------------------------------------------------------------------------ */ /* read files, copy memory blocks, with transparent gunzip */ size_t xc_dom_check_gzip(void *blob, size_t ziplen) { unsigned char *gzlen; size_t unziplen; if ( strncmp(blob,

Hello~~~ I need to use some functions provided by xen, such as xc_vcpu_getcontext(), xc_map_foreign_ranger() and so on. I have find them in the /libxc/xc_domain.c~~~ But I don't know how to use them in my program. For example, if I need to use the function named printf(), I have to include the header file <stdio.h>~~~ Now, I want to use these functions provided by xen, which header

Hi all, I am running the current xen-unstable and had the following error message when trying to create domain1. # ./xenctl script -f/etc/xen-mynewdom Domain defaults: name XenoLinux size 98304 vifs 1 domainImage /boot/xenolinux.gz domainInitRD null rootDevice /dev/hda5 rootArgs rw usrDevice null NWIP

xc_dom_alloc_page deals with virtual address not physical address. When an ELF is loaded, virtual address and physical address may be different. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index a40e04d..75a6f1c