similar to: no kernel-debuginfo or source RPM for kernel 3.18.21-17

On 7 March 2016 at 14:42, Johnny Hughes <johnny at centos.org> wrote: > On 03/03/2016 01:22 PM, Thanos Makatos wrote: >> I'm trying to debug what I believe to be a kernel bug >> (https://lists.centos.org/pipermail/centos-devel/2016-March/014463.html) >> and I'm trying to set up systemtap for that. >> >> I'm trying to set up systemtap on kernel

On 03/03/2016 01:22 PM, Thanos Makatos wrote: > I'm trying to debug what I believe to be a kernel bug > (https://lists.centos.org/pipermail/centos-devel/2016-March/014463.html) > and I'm trying to set up systemtap for that. > > I'm trying to set up systemtap on kernel 3.18.21-17.el6.x86_64 (Xen > 4.4.3-10.el6) and it requires the kernel-debuginfo package, however I

Hi There, I''ve been trying to get this to work for the last couple of days, but found no information on the internet that would help. Essentially, a tap-ctl opencommand with a qcow2 image does not work (error code 2) and produces the following line in syslog: tap-ctl: tap-err:tap_ctl_open: open failed, err -2 I have attached a shell script that reproduces the problem on my machine. The

Hi, I''d like to use the blktap utils from https://github.com/xen-org/blktap because of the mirror feature, as the blktap utils comming with xen does not support this. Could anybody explain why there are two different blktap utils (one in git and one comming with xen source) and how to compile the one from git so that it works with libxl ? Any pointers greatly appreciated ;-) Thanks

This patch series introduces the tapback daemon, the user space daemon that acts as a device''s back-end, essentially most of blkback in user space. The daemon is responsible for coordinating the front-end and tapdisk. It creates tapdisk process as needed, instructs them to connect to/disconnect from the shared ring, and manages the state of the back-end. The shared ring between the

(I've already sent this to centos-devel almost a week ago but didn't get any reply.) I'm evaluating dm-cache on kernels 3.18.21-17.el6.x86_64 (Xen 4) and 2.6.32-573.7.1.el6.x86_64 (KVM). The test I do is a simple sequential read using dd(1). read_promote_adjustment and sequential_threshold have been set to 1 and 0, respectively. For the 2.6.32 kernel, all seems to be working fine,

Compiling NBD kernel module for kernel 3.10.0-514.26.2.el7.x86_64 fails as follows: # make -C ../../ M=`pwd` nbd.o make: Entering directory `/root/rpmbuild/BUILD/kernel-3.10.0-514.26.2.el7/linux-3.10.0-514.26.2.el7.x86_64' CC /root/rpmbuild/BUILD/kernel-3.10.0-514.26.2.el7/linux-3.10.0-514.26.2.el7.x86_64/drivers/block/nbd.o

Hello. I want to know what is the unit of compression in ZFS. Is it 4 KB or larger? Is it tunnable? Thanks. Thanos -- This message posted from opensolaris.org

Hi, I''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success. My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

This patch series introduces the shared ring used by the front-end to pass request descriptors to tapdisk, as well as responses from tapdisk to the front-end. Requests from this ring end up in tapdisk''s standard request queue. When the tapback daemon detects that the front-end tries to connect to the back-end, it spawns a tapdisk and tells it to connect to the shared ring. The shared

This patch series introduces the VHD library. It is based on the blktap2 one, with changes coming from the blktap2.5 one. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

The current mitigation for CVE-2018-14634 is a systemtap script mentioned here: https://access.redhat.com/security/cve/cve-2018-14634 It also mentions that one can build a kernel module to distribute to other machines, but in any case one needs the corresponding debuginfo packages to do either. After enabling CentOS-Debug.repo, what I get is:

I want to use systemtap on a 5.3 system but cannot find supporting kernel-PAE-debuginfo or kernel-debuginfo-common packages. Am I being a noob, or do these not exist for the PAE kernel? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20101202/82cc98b8/attachment-0002.html>

Hi! I'm trying systemtap on CentOS 6.2 kernel-2.6.32-220.23.1.el6.x86_64. My problem is that I can't find kernel-debuginfo... corresponding to my kernel version. The systemtap docs suggest rebuilding the kernel from sources, but it looks like I will have to install my own kernel, which is not acceptable on the production machine. Where can I find the debuginfo for the latest CentOS

I have released to the master mirror the following packages for Xen4CentOS: b518e3b0fd4f735b34d7784815793cb787283d9029776bd9794cedeb274b9204 kernel-3.18.21-16.el6.x86_64.rpm 4b17373a0ef6806b26d02eb87fc299020beb60b6e31ed08a9c57d30a1410fbe7 kernel-devel-3.18.21-16.el6.x86_64.rpm cacedf6771849f7525145ad4ed7d36a2cad5b49b546173bb7c132b236cb7ac49 kernel-doc-3.18.21-16.el6.noarch.rpm

On 11/01/2015 12:07 PM, Karel Hendrych wrote: > Hi, just a heads-up: 3.18.21 didn't boot up on HP ML310e Gen8 v2, SATA drives in AHCI mode, / on software raid 1, no LVM. It ended up in kernel panic > with unable to mount root fs. Attached. No difference in grub kernel/xen settings. > > I didn't investigate the things deeper so far. 4.4.3-3/3.18.17 is booting fine. > >

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz

We got a remote Oracle 10g R2 standby running on OCFS2. Initial when we started the standby, read I/O was < 5MB/sec on average. Since then it has grown to over 40MB/sec (longer average, it peaks much higher). Here is a graph showing this: http://www.alameda.net/~ulf/dbphx01.png We also have a local standby running (on EXT3) which is not showing the same symptom. I am trying to find where all

Is there anyway to tell with top or iostat which process is hogging all the disk I/O? Matt