similar to: How to read text buffer after kernel crash?

Hello everyone, this is my first mail. I am trying to pxe boot an ISO CD. I configured DHCP and TFTP. In DHCP config file I define the boot folder as filename "pxelinux.0"; In TFTP config file in /tftpboot/pxelinux.cfg/default I wrote the boot option as LABEL ccc LINUX memdisk INITRD ccc.iso APPEND raw Now I have some problems and parts I don't understand. 1) I downloaded and

Information: 5.4 kernel (2.6.18-164.el5). I have a vmcore (from kdump), if the developers are interested, let me know a place to upload the vmcore file. I used the crash command to do a backtrace. I manage to get machines with later 5.4 and 5.5 to panic the same way. Broadcom or Intel NICs panic the same way. This is an NFS client where the NFS server is restarting several times; NFSv3, mount

I''m experimenting with xen + iscsi, and I founded that under heavy stress domU''s can crash entire system, I''ve reproduced this many many times. My system is like this Software: - iSCSI Enterprise Target v0.4.13 - RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel 2.6.16.29 + Open iSCSI v2.0.730 (Initiator) - Bonnie++ v1.03a VM: - Debian 3.1r3 + Open iSCSI v2.0.730

... [ 176.025679] random: crng init done [ 411.168635] netem: version 1.3 [ 456.059840] ------------[ cut here ]------------ [ 456.059849] WARNING: CPU: 4 PID: 1918 at net/ipv4/tcp_output.c:1048 tcp_set_skb_tso_segs+0xeb/0x100 [ 456.059851] Modules linked in: sch_netem cirrus ttm drm_kms_helper crc32_pclmul syscopyarea ghash_clmulni_intel sysfillrect sysimgblt fb_sys_fops aesni_intel lrw

I have multiple VM's on the same KVM host. One of the VM's is running NTP. All VM's can reach eachother, no firewall in between. But the problem is, the VM's cannot communicate over port 123/udp to the NTP VM. Network: 172.24.100.0/22 KVM: 172.24.101.50 VM ntp: 172.24.102.10 VM foo: 172.24.102.20 1. On the NTP server, listen for any incoming packets from VM foo

> Hi, Simon > > >Two things: > > > >1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this > >(and if you want > > a dump, do ''xm dump'' followed by ''xm destroy'') > > > What do you mean? > I think we cannot dump with "xm destroy" now. >

Add guide to using the kexec and kdump facility in xen. Signed-off-by: Simon Horman <horms@verge.net.au> --- I the work on this document using an ia64 machine and qemu emulating x86_32. I am yet to verify it on x86_32 hardware or x86_64. Index: xen-unstable.hg/docs/misc/kexec_and_kdump.txt =================================================================== --- /dev/null 1970-01-01

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Howdy, Running a round of updates from 6.3 to 6.4 and I'm seeing the following on all the servers. Want to make sure I'm not going to end up with a kernel panic if I reboot into the new kernel or have any other issues. Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel Apr 22 11:10:21 www kdump: stopped Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd Apr 22

Hey all! I''m currently in the process of trying to debug a (possibly!) Xen-related issue (with Kernel 3.2.9-vanilla as Dom0, and Xen 4.1.2 [almost] vanilla, except for a patch for CVE-2012-0029), where a system freezes without me being able to ascertain a triggering event. The system console is completely unresponsive in the event of hangs (i.e., displays motd and the login prompt,

Sorry I forgot to mention. We use FreeIPA for SSH login. >Thanks for the information. > >I know this is kinda out of topic but is it possible to use samba with ipa client from another domain? > >It is probably broke both Samba and FreeIPA client. > >Our servers run a different domain with FreeIPA. Samba domain is domain.com, FreeIPA domain is domain.cloud > >I know

Requires "kdump support" patch for ovirt-node Signed-off-by: Alan Pevec <apevec at redhat.com> --- common-blacklist.ks | 2 +- common-pkgs.ks | 2 ++ ovirt-node-image.ks | 10 +++++++++- 3 files changed, 12 insertions(+), 2 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index 2452237..af7fa07 100644 --- a/common-blacklist.ks +++

Just updated one of our servers, and see a bunch of udevd-event[8735]: run_program: ressize 256 too short Along with Apr 8 14:57:48 <servername> kernel: Breaking affinity for irq 209 Apr 8 14:57:48 <servername> kernel: CPU 8 is now offline Apr 8 14:57:49 <servername> kernel: CPU 8 offline: Remove Rx thread Apr 8 14:57:49 <servername> kernel: CPU 9 is now offline Apr

+nouveau at lists.freedesktop.org On 11/27/2017 11:57 AM, Sinan Kaya wrote: > pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as > where a PCI device is present. This restricts the device drivers to be > reused for other domain numbers. > > Getting ready to remove pci_get_bus_and_slot() function in favor of > pci_get_domain_bus_and_slot(). > >

> Daniel Kiper <daniel.kiper at oracle.com> writes: > > > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default > > Linux infrastructure and require some support from firmware and/or hypervisor. > > To cope with that problem kexec firmware infrastructure was introduced. > > It allows a developer to use all kexec/kdump features of given firmware

> Daniel Kiper <daniel.kiper at oracle.com> writes: > > > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default > > Linux infrastructure and require some support from firmware and/or hypervisor. > > To cope with that problem kexec firmware infrastructure was introduced. > > It allows a developer to use all kexec/kdump features of given firmware

Kexec / Kdump - xen-3.0.4-testing-13098 Kexec Kexec Kexec Kexec Kdump Hardware Xen -> Xen -> bzImage -> Xen -> Xen -> Arch Platform Xen bzImage Xen vmlinux vmlinux i386 A PASS PASS PASS PASS PASS i386 B (VMX) PASS PASS PASS PASS

Hi all. While playing with iSCSI Enterprise Target + multipathd on CentOS 5.1 (both the target and the initiator/multipath/xen box are Cent 5.1), I encountered a strange fault condition that leads to a kernel panic in a version of Xen 3.2.1-rc2 pulled from a couple of days ago. My lab consists of two Clovertown machines with dual GigE into separate switches. The target box is softraid5