similar to: Monitor syscalls in guests

Hello I am running Xen 3.3.1 on Debian x86 with 2.6.26 Dom0. I have a PV guest running another Debian with 2.6.18 kernel. all kernels are precompiled Debian ones. Everything work quite well. I have a modified hypervisor running to intercept syscalls issued by the PV guest and analyze the behavior of a given PID. But this is not an issue, as it works fine. My concern is about the applications

Hi, I was trying to determine how Wine captures syscalls, and I found this thread: http://www.winehq.org/pipermail/wine-users/2002-October/009077.html The answer was that Wine *doesn't* deal with syscalls, and relies on the application never directly making a syscall, but instead calling into the standard system libraries (Win32). Is this still true today? I'm surprised that Wine can

Commit-ID: cd5927c02749b7c9d58b5144586505c85b903c27 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=cd5927c02749b7c9d58b5144586505c85b903c27 Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Mon, 21 May 2012 10:21:21 -0700 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 21 May 2012 10:24:45 -0700 [klibc] SYSCALLS.def: add openat() on 64-bit

Commit-ID: 0c7359e8787c60b7143b3e366d31b2c2409cba3a Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0c7359e8787c60b7143b3e366d31b2c2409cba3a Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:10 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:30:11 -0800 [klibc] syscalls: Fixup some of the

The finit_module() system call was merged in Linux 3.8. This system call is similar to init_module(), but it allows to load Linux kernel modules from file descriptors. Signed-off-by: Nikita Ermakov <sh1r4s3 at mail.si-head.nl> --- usr/klibc/SYSCALLS.def | 1 + 1 file changed, 1 insertion(+) diff --git a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def index c8ac9e0d..7a67b01f 100644 ---

klibc fails to build on ia64 because it has neither fork nor the ppoll syscalls. This patch marks the former in SYSCALLS.def, and puts a guard wrapper around the ppoll definition in ppoll.c Should these calls return ENOSYS rather than simply not existing on some systems? If yes, please apply this and I'll follow up with a patch shortly that does ENOSYS for this and pselect at least.

that looks great, will include it in my next patch queue. now that 1.5.18 is out of the door, posting to mailing list for review and will soon try it out. ----- Forwarded message from Aurelien Jarno <aurel32 at debian.org> ----- Date: Fri, 16 Apr 2010 18:17:58 +0200 From: Aurelien Jarno <aurel32 at debian.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Subject:

fwd'ing to klibc malinglist. ----- Forwarded message from Lo?c Minier <lool at dooz.org> ----- Date: Wed, 16 Mar 2011 23:34:51 +0100 From: Lo?c Minier <lool at dooz.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Subject: Bug#618616: arm build failure with latest binutils - usr/klibc/syscalls/_exit.S:29: Error: .size expression does not evaluate to a

Commit-ID: 8858e8319655ef38398e0833b71d65b0e620a061 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8858e8319655ef38398e0833b71d65b0e620a061 Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:11 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:13 -0800 [klibc] syscalls: Add syscalls

arm64 uses generic syscalls, and does not include the "noat", "noflags", and "deprecated" syscalls. i.e. __ARCH_WANT_SYSCALL_{NO_AT|NO_FLAGS|DEPRECATED} This patch adds the syscalls needed for klibc to run on arm64. Signed-off-by: Steve Capper <steve.capper at linaro.org> --- usr/klibc/Kbuild | 3 +++ usr/klibc/SYSCALLS.def | 33

Debian: (Closes: #334917) Signed-off-by: Thorsten Glaser <tg at mirbsd.de> --- usr/klibc/arch/m68k/syscall.S | 42 +++++++++++++++++++++++++++++++++------- usr/klibc/arch/m68k/vfork.S | 13 +++-------- 2 files changed, 38 insertions(+), 17 deletions(-) diff --git a/usr/klibc/arch/m68k/syscall.S b/usr/klibc/arch/m68k/syscall.S index 966c92d..f468678 100644 ---

Hello! Perhaps someone can give me a good answer to this question. Please give me a direct answer, I have allready been trouh the wine FAQ:s , docs, code, etc. I know DOS syscalls is made using interupts (int instruction) but, is Windows/NT syscalls made the same way. How does wine stop these instructions from reaching the unix kernel?

There were a few unchecked syscalls in fish.c >From ba8b8b0684a03b6e6fbb939ed7e1cbf5e1000092 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Wed, 19 Aug 2009 10:01:07 +0200 Subject: [PATCH libguestfs] guestfish: detect a few more failed syscalls * fish/fish.c (issue_command): Detect/diagnose more failed syscalls. --- fish/fish.c | 26

I had a klibc build failure (on s390) because of include/sys/module.h and noticed that it still has the old system call interface for 2.4 style modutils. Is there any reason to keep that in klibc? This patch fixes the build problem by removing the old file and also makes it possible to build module-init-tools (after some tweaking there) against klibc. Arnd <>< =====

This patchset allow syscalls (flock, ipc, getuid, geteuid and ioctl), so openssl engines, e.g. OpenSSL-ibmca and OpenSSL-ibmpkcs11, can work and communicate with the crypto cards during ssh login. 1. The flock and ipc are allowed only for s390 architecture. They are needed for openCryptoki project (PKCS#11 implementation), as the ibmpkcs11 engine makes use of openCryptoki. For more information,

> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Thorolf Godawa > Sent: 02 February 2006 02:30 > To: xen-devel@lists.xensource.com > Cc: xen-users@lists.xensource.com > Subject: [Xen-users] Re: No VMX-guests on Intel Xeon/VT > > Hi all, > > OK, I''ve installed

> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Thorolf Godawa > Sent: 02 February 2006 02:30 > To: xen-devel@lists.xensource.com > Cc: xen-users@lists.xensource.com > Subject: [Xen-users] Re: No VMX-guests on Intel Xeon/VT > > Hi all, > > OK, I''ve installed

Summary: Changeset 10173 - 64bit UP and SMP guests boot cleanly - 32bit UP guests boot clean and 32bit SMP guests still fail to boot (see failure.7) - 32bit UP guests lockup under load with "ata1: command 0x25 timeout" (see failure.4) - 64bit SMP 2 CPU guests lockup under load with "ata1: command 0x25 timeout" (see failure.2) - 32bit UP guest crashed on user load test

Hi List, (Long time lecher, first time poster) Not sure if this is the best place to ask, but here goes.. I have a few test Guests on a Xen host, and I would like to start monitoring (and maybe restricting) the network traffic of the guests but not the Host. No I know this can be done with iptables, but I just wondered if anyone knew of a package or how-to to set this up with Xen on CentOS 5 ?

hi! i read some other threads but none could help me. i''m on gentoo trying to boot 2.6.24 and 2.6.25 kernel.org kernels within my 2.6.20-xen kernel but i fail to get a correct .config. thanks yannick more infos: -- dom0 alchemist ~ # xm info host : alchemist release : 2.6.20-xen-r6-yk version : #1 SMP Sat Dec 1 13:47:54 CET 2007