search for: xc_core

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, from xc_core.c:1: xen/privcmd.h:36:23: asm/types.h: No such file or directory gcc tries to use /usr/include/asm/types.h, which only exists on Linux (and therefore works on...

...=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -D_GNU_SOURCE -Werror -Wmissing-prototypes -fno-strict-aliasing -I. -I../xenstore -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c cc1: warnings being treated as errors xc_core.c: In function 'xc_core_shdr_get': xc_core.c:195: warning: assuming signed overflow does not occur when assuming that (X + c) < X is always false make[5]: *** [xc_core.o] Error 1 make[5]: Leaving directory `/buil...

...process 1] > Core was generated by `xl''. > Program terminated with signal 11, Segmentation fault. > #0 0x00007f7ff7007b45 in xc_domain_dumpcore_via_callback > (xch=0x7f7ff7b0d800, domid=20, args=0x7f7fffffdae0, > dump_rtn=0x7f7ff700632c<local_file_dump>) > at xc_core.c:860 > 860 xc_core.c: No such file or directory. > in xc_core.c > > > (gdb) backtrace > #0 0x00007f7ff7007b45 in xc_domain_dumpcore_via_callback > (xch=0x7f7ff7b0d800, domid=20, args=0x7f7fffffdae0, > dump_rtn=0x7f7ff700632c<local_file_dump>) > a...

...patchbot-unstable <patchbot-unstable@lists.xensource.com> wrote: > > # HG changeset patch > # User root@procyon > # Node ID 11645dda144c3c8365dd2a6a64cb5a7d7da01170 > # Parent 30c659b655f15da7f6eeca68cd204162fbcf4733 > In this patch, the xc_domain_dumpcore_via_callback() in xc_core.c of > libxc is modified. Previously, the xc_domain_dumpcore_via_callback() > did not respond to error when copy_from_domain_page() failed. > In other words, the dump core remained silent even if mapping the domain > memory failed and its page could not be copied. When this happened, &g...

# HG changeset patch # User yamahata@valinux.co.jp # Date 1188385920 -32400 # Node ID ed74e810c3cc669fc236ffdc4eb6114d610f35c4 # Parent 6642cba9eb6631f40071cdb39f518ef4bf270387 update dump-core-foramt.txt documentation. PATCHNAME: dump_core_documentation_update Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> diff -r 6642cba9eb66 -r ed74e810c3cc docs/misc/dump-core-format.txt ---

This patch allows core-dumping to work on a cross-bit host/guest configuration, whereas previously that was not supported. It supports both PV and FV guests. The core file format generated by the host, needs to match that of the guest, so an alignment issue is addressed, along with the p2m frame list handling being done according to the guest size. Signed-off-by: Bruce Rogers

The existing xc_domain_dumpcore is very specific to disk/file based output. Refactor the code slightly to allow more user-specified control. This is done by adding a parallel xc_domain_dumpcore2 (naming isn''t always my strong suit), which allows the specification of a callback routine and an opaque argument block. The existing dumpcore routine is modified to use the callback for all

The following dump-core patches changes its format into ELF, adds PFN-GMFN table, HVM support, and adds experimental IA64 support. - ELF format Program header and note section are adopted. - HVM domain support To know the memory area to dump, XENMEM_set_memory_map is added. XENMEM_memory_map hypercall is for current domain, so new one is created. and hvm domain builder tell xen its

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26 > close 443024 3.1.1-1 Bug#443024: xen-3: FTBFS: xc_core.c:195: warning: assuming signed overflow does not occur when assuming that (X + c) < X is always false 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 3.1.1-1, send any further explanations to Lucas Nussbaum <lucas at lucas-nussb...

Dear Debian Xen Team, The following possible problem(s) were detected in the package(s) you maintain in Debian: === xen-unstable: = This package has not been in testing for 292 days. = This package has not been able to migrate from unstable to testing for 292 days. See <http://bjorn.haxx.se/debian/testing.pl?package=xen-unstable> This is an automated mail. These mails are sent

The following patches shave some rough edges off the tools build system to allow cross compiling for at least arm32 and arm64 based on the Debian/Ubuntu multiarch infrastructure. They also add the necessary fixes to build for arm64 (which I have only tried cross, not native). I have posted some instructions on how to compile with these patches on the wiki:

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list