similar to: [Patch] Enable "sysrq c" handler for domU coredump

Displaying 20 results from an estimated 700 matches similar to: "[Patch] Enable "sysrq c" handler for domU coredump"

2009 Jan 27
13
[Patch] fix xenfb_update_screen bogus rect
Hi, When I tested pvfb, I got the following warnings. It seems to be caused by checking/setting info->dirty without dirty_lock. We need to check/set info->dirty safely. xenfb_update_screen bogus rect 2147483647 0 2147483647 0 BUG: warning at /root/linux-2.6.18-xen.hg/drivers/xen/fbfront/xenfb.c:240/xenfb_update_screen() Call Trace: [<ffffffff8036920e>] xenfb_thread+0x19b/0x2be
2008 Jun 02
4
[Patch] fix compilation
Hi, I got the following compilation error. This patch fix the error, I think it is needed for xen-testing tree. /root/unstable/linux-2.6.18-xen.hg/scripts/mod/sumversion.c: In function ''get_src_version'': /root/unstable/linux-2.6.18-xen.hg/scripts/mod/sumversion.c:384: error: ''PATH_MAX'' undeclared (first use in this function)
2008 Dec 25
1
[Patch] Enable Option ROM write access
Hi, This patch is enabling write access during rom_scan. Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Best Regards, Akio Takebe _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 Aug 03
3
RE: [Patch][RFC] Support "xm dump" (is Re: Re: [Patch]Enable "sysrq c" handler for domU coredump)
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'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as
2008 Apr 27
2
Random reboots with Xen 3.2.1
I am seeing random reboots after installing Xen 3.2.1 (running with linux-2.6.18-8 pulled from a few days ago). So far, the reboots only happen if I have enabled cpufreq=dom0-kernel and actually run frequency scaling (such as with the ondemand governor). The reboots only happen after a few hours. The machines seem to be stable if I pass the cpufreq option to Xen but disable frequency scaling. I
2008 Sep 04
5
xm dump-core options are useless
This cset: changeset: 11473:0008fca70351 date: Thu Sep 14 08:19:38 2006 +0100 description: xm dump command add on xm dump-core [-L|--live][-C| --crash] <domID> [output path] Didn''t actually implement anything. Worse, it looks like we don''t even pause the domain, so it''s always live (not good). What''s going on? regards john
2006 Jul 28
6
[PATCH] ia64 buildconfig update
Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28
2008 Jan 11
2
xen-3.1 IPMI sensor (fwd)
Hallo *! I have a board SE7501HG2. - On 2.6.18 ipmitool works succefull. On Xen-3.1 (2.6.18) ipmitool say: # ipmitool sensor WARNING: Unknown SDR repository version 0x00 SDR record id 0x0000: invalid length 0 (see thread [ipmitool-devel] Unknown SDR version) - On page [4] as written: ipmitool -> BMC ---> i2c/smbus ''-> SDR - On Thread [9] was written:
2006 Dec 11
13
xm dump-core and analyzing
Hi, Is there any tool out there that can help me analyze a coredump? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 Jan 13
2
[PATCH] unifying error message of migrate and sysrq
This patch unifys error messag of migrate and sysrq. Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r bfcdf4099d23 tools/python/xen/xm/migrate.py --- a/tools/python/xen/xm/migrate.py Thu Jan 12 13:27:55 2006 +++ b/tools/python/xen/xm/migrate.py Fri Jan 13 15:26:14 2006 @@ -56,8 +56,8 @@ if opts.vals.help: opts.usage()
2008 Jan 31
5
How-To create Windows HVM?
Hi, i''m a little bit stuck here with creating a HVM-Windows (w2k3) Guest under Xen 3.1. I''m using ubuntu 7,10 with a 2.6.22.16-xen-patched kernel which seems to be stable for single cpu-linux guests. Cpu is a Q6600 and XD,VT and VT-d is enabled in the bios. When i create the windows guest with ''xm create w2k3 -c" (conf below) I get: "Started domain
2006 Jul 25
6
[PATCH][QEMU] Add IA64-specific code for new qemu.
This patch adds the ia64-specific code for new Qemu . In addition, some ia64 patches aren''t checked into xen-unstable.hg, so I reversed the related logic temporarily. Once sync with xen-ia64-unstable.hg, the logic will regain automatically. Thanks & Best Regards -Xiantao OTC,Intel Corporation _______________________________________________ Xen-devel mailing list
2006 Aug 03
2
RE: [Patch][RFC] Support "xm dump" (is Re: Re:[Patch]Enable "sysrq c" handler for domU coredump)
> 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. >
2007 Mar 26
8
Backend device not found error
Hi, Sometimes when I mount a disk image, unmount it, and then try to create a domU using the disk image I get the following error: Error: Device 2049 (vbd) could not be connected. Backend device not found. Im using a FC4 image. Here is the config file: kernel = "/boot/vmlinuz-2.6.16-rc3-xenU" memory=256 name=Domain1 vif = [''bridge=xenbr0''] disk = [
2008 Oct 01
1
How to get linux-2.6.18-xen.hg?
Hi, I downloaded xen-3.3.0.tar.gz and linux-2.6.18-xen-3.3.0.tar.gz from http://www.xen.org/download. when I executed "hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg", there was an error. Prompt was: destination directory: linux-2.6.18-xen.hg abort: error: Temporary failure in name resolution How can fix this problem? Thanks, Jeff.Gu
2009 Jul 01
1
IO controller mini-summit -- Japan, Oct 2009
Hi All, We will hold a Linux IO controller Mini-Summit in Tokyo, Japan on Saturday, Oct. 17, 2009 -- day before the 9th Linux kernel summit. This is a good opportunity to meet face-to-face to discuss issues and directions for developing IO controller. Details of the summit are still sketchy, so suggestions for agenda topics are welcome. Please e-mail to me or post on the wiki page at
2009 Jul 01
1
IO controller mini-summit -- Japan, Oct 2009
Hi All, We will hold a Linux IO controller Mini-Summit in Tokyo, Japan on Saturday, Oct. 17, 2009 -- day before the 9th Linux kernel summit. This is a good opportunity to meet face-to-face to discuss issues and directions for developing IO controller. Details of the summit are still sketchy, so suggestions for agenda topics are welcome. Please e-mail to me or post on the wiki page at
2009 Jul 01
1
IO controller mini-summit -- Japan, Oct 2009
Hi All, We will hold a Linux IO controller Mini-Summit in Tokyo, Japan on Saturday, Oct. 17, 2009 -- day before the 9th Linux kernel summit. This is a good opportunity to meet face-to-face to discuss issues and directions for developing IO controller. Details of the summit are still sketchy, so suggestions for agenda topics are welcome. Please e-mail to me or post on the wiki page at
2012 Dec 28
1
[PATCH v3 01/11] kexec: introduce kexec firmware support
> 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
2012 Dec 28
1
[PATCH v3 01/11] kexec: introduce kexec firmware support
> 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