similar to: [patch] Add more xc_error_code values.

Made the xenctrl.h and xenstore.h easier to use with C++: added ''extern "C"'' statements, moved the definition of enum xc_error_code above it''s typedef, and renamed a ''new'' parameter (''new'' is a C++ keyword). Signed-off-by: Razvan Cojocaru <rzvncj@gmail.com> diff -r 5af4f2ab06f3 -r c273ee1fc8ba tools/libxc/xenctrl.h

Made the xenctrl.h and xenstore.h easier to use with C++: added ''extern "C"'' statements, moved the definition of enum xc_error_code above it''s typedef, and renamed a ''new'' parameter (''new'' is a C++ keyword). Includes a modification of _hvm_hw_fix_cpu() suggested by Jan Beulich. Signed-off-by: Razvan Cojocaru

Hi, changeset 12809 gives me this: xc_private.c: In function ‘safe_strerror’: xc_private.c:500: warning: return makes pointer from integer without a cast make[3]: *** [xc_private.o] Error 1 cheers, Gerd -- Gerd Hoffmann <kraxel@suse.de> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

> Put the Linux definition in xc_linux.c. Put a default dummy > implementation > in xc_private.c with __attribute__ ((weak)). If you have only a > function > prototype in xc_private.h then you won''t need -D_GNU_SOURCE for > xcutil/Makefile. This wont quite work -- xc_private.c isn''t part of libxenguest which includes save/restore which needs the function...

hi, my friends: Currently, i am studying the way of hypercall's implementation. i have already known the flow of hypercall's execuation, and i decided to add a new hypercall into the Xen. first, i want to know the detail of one hypercall function, for example, "do_xen_version", but i can not find the location of definition of "do_xen_version". who can help me? i have

Hi, All Intel QA conducted a full validation for xen 4.1 rc1, it includes VT-x, VT-d, SRIOV, RAS, TXT and xl tools testing. 24 issues were exposed. Refer the bug list, please. We already assigned 14 bugs to Intel developers (which has an ''Intel'' tag in the bug title), most of the rest 10 bugs are related xl command. For the these bugs, need community''s help to fix

Good day - This is my first post to this list , and I''m new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and

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)

Linux 3.11 added respective support, so I think we should follow suit. 1: xen: add LZ4 decompression support 2: libxc: add LZ4 decompression support Signed-off-by: Jan Beulich <jbeulich@suse.com>

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

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,

Hi,All We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Two platforms (PAE/32E) test all are based on SMP, It means that we boot up SMP guest OS in VMX. Here is the test summary: New issue (1) ================================================ 1) Fails to restore VMX guests http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=929 Issues List (3):

Hi list, Since I've upgraded from Version 5.0 to 5.1 i have strange problems with samba. Since 5.1 the connection from a XP client to the samba server disconnect often, especially then i write a file to the share after some idle time. Some informations of my config. The Box is a Samba PDC for a little Windows Domain with a ldap backed. I used this config on Centos 4.x and 5.0 without

I am tasked with installing xen on a FC4 machine. I went ahead and followed the fedora xen howto, however when I rebootrd into the dom0 kernel I would get a page full of hda: lost interrupt followed by a blank screen. I then decided to remove all that and go with a xen-testing from source build. Now when I do "make tools" in the -testing directory I get: [...] In file included from

Hello there, We (a small hosting community) are running a steadily growing number of Xen domUs on a quad dualcore Xeon server with 64GB ram. We''ve got 100 running domUs at the moment. Trying to create a new one results in this error: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') If I shut down another domain, I can

xc_interface_close() crashes if it gets NULL as an argument. However, it just calls xc_interface_close_common() which is called by many others functions. It means that they are also vulnerable. So fix above mentioned issue by adding NULL check in xc_interface_close_common(). This way we fix similar issue in other functions which calls xc_interface_close_common() too. Signed-off-by: Daniel Kiper