similar to: Some of your Debian packages might need attention

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 more than 196 days. This is an semi-automated mail. These mails will be sent monthly. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail We are sorry if this mail was useless for

Dear Debian Xen Team, The following possible problem(s) were detected in the package(s) you maintain in Debian: === xen-3: = This package has 1 bug(s) that should be fixed for the next Debian release: - #464969 <http://bugs.debian.org/464969> xen-hypervisor-3.2-1-i386: Linux mmap()/vmsplice() exploit causes memory map corruption in hypervisor regardless of domain privilege This is a

=== xen-3: = 2 bug(s) that should be fixed for the next Debian release: - #391935 <http://bugs.debian.org/391935> Xen trademark might be problematic - #490409 <http://bugs.debian.org/490409> CVE-2008-2004: privilege escalation ------------ interesting stuff probably ends here ------------ This is an automated mail. These mails are sent two times per month. For more information

=== xen-3: = 1 bug(s) that should be fixed for the next Debian release: - #391935 <http://bugs.debian.org/391935> Xen trademark might be problematic ------------ interesting stuff probably ends here ------------ This is an automated mail. These mails are sent two times per month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail We are sorry

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 353 days. = This package has not been able to migrate from unstable to testing for 353 days. See <http://bjorn.haxx.se/debian/testing.pl?package=xen-unstable> This is an automated mail. These mails are sent

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 258 days. = This package has not been able to migrate from unstable to testing for 258 days. This is a semi-automated mail. These mails are sent monthly. For more information about these mails, refer to

This is an automated mail. These mails are sent twice a month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail === xen-3: = 2 bug(s) that should be fixed soon: - #536173 <http://bugs.debian.org/536173> xen-utils-3.4 need to depend on 3.4 version of xenstore - #536176 <http://bugs.debian.org/536176> xen-utils-3.4: trying xen-3.4 once

This is an automated mail. These mails are sent twice a month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail === xen-3: = There are 3 unfixed security issue(s), please fix them. See http://security-tracker.debian.net/tracker/source-package/xen-3 = Lintian reports 1 error(s) and 17 warning(s), you should consider fixing them. See

This is an automated mail. These mails are sent twice a month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail === xen-3: = There are 3 unfixed security issue(s), please fix them. See http://security-tracker.debian.org/tracker/source-package/xen-3 = Lintian reports 9 warning(s), you should consider fixing them. See

Package: xen-3 version: 3.1.0-2 Severity: serious User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20070917 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: make[5]: Entering directory `/build/user/xen-3-3.1.0/debian/build/build-utils_i386/tools/libxc' gcc -O2 -fomit-frame-pointer -m32 -march=i686

On 31.10.13 04:34, Miguel Clara wrote: > I was trying to get a core-dump for a domU with xl and got this error: > > # xl dump-core 20 test.core > Memory fault > > GDB shows this: > > a# gdb xl xl.core > GNU gdb (GDB) 7.3.1 > Copyright (C) 2011 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later<http://gnu.org/licenses/gpl.html> >

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

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

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

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:

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,

tags 446771 + patch thanks Hi, attached is a patch to fix this if you don't already have one. Kind regards Nico -- Nico Golde - http://ngolde.de - nion at jabber.ccc.de - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. -------------- next part -------------- A non-text attachment was scrubbed... Name: CVE-2007-4993.patch Type: text/x-diff Size: 4742

This change has the effect of adding some complexity to the callback routines. The original callback passed an opaque argument which was a private item for the use of the controlling mechanism and its callback function. This change removes this and specifies only an fd. While it''s possible for the controlling mechanism to use the fd as an index to find internal data structures, this is

# 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 ---

Dear all Some computations gave a matrix. The single value decomposition of it worked fine previously, after an system upgrade I get the following error: ----- > La.svd(x,256,256) Error in La.svd(x, nu, nv) : BLAS/LAPACK routine 'DLASCL' gave error code -4 ----- Erroneous Matrix: ftp://usys-ftp.ethz.ch/ITES/STEP/nussbaum/R/matrix-lapack-error4.RData /.csv Operating System: Debian 8