similar to: [PATCH][Mini-OS][RESUBMIT] cscope patch

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

This patch adds a check to see if v_end in setup_guest() wraps around to 0 and lets the builder exit gracefully when it does. Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> > -----Original Message----- > From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] > Sent: Thursday, June 01, 2006 6:14 AM > To: Puthiyaparambil, Aravindh > Cc:

I am getting the following error with "xm list" on a x86_64 SLES10 Beta system running changeset 9435:11fee62328cc. I am able to bring up DomUs and I am able to do "xm info" without issues. But I am seeing similar "OverflowError: int exceeds XML-RPC limits" with "xm shutdown" and "xm destroy". My python version is 2.4.2. Any way I can get around

I am seeing a strange issue while running Mini-OS on the changeset 9906:a95e677073c1. This is on both i386 and x86_64. The only difference being on i386 if I stop printing to the console, this issue is not manifested. But with x86_64 it happens all the time. Bringing up Mini-OS for the first time causes xm to hang on certain commands like "list, destroy". Other commands like

destroy() is being called on exception in both start() and create(). It needs to be called only in create(). Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Cd /xen/xen-unstable/linux/2.6.12-xen0/ Then: make ARCH=xen xconfig Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von:

Here is a patch for clustered xAPIC and Unisys ES7000 support in Xen. To turn the features on add CONFIG_X86_CLUSTERED_APIC and CONFIG_ES7000 defines to xen/include/asm-x86/config.h Signed off by Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This patch causes "xm mem-set" to be lower bound on domX-min-mem option in xend-config. Another configuration option called domU-min-mem has been introduced, which works similarly to dom0-min-mem. This is prevents users from freezing the system when doing "xm mem-set" on very low values like 32M. Signed-off-by: Aravindh Puthiyaparambil

# HG changeset patch # User Wei Liu <wei.liu2@citrix.com> # Date 1329922671 0 # Node ID bb2986677df84b9709a60aea7e70ffd9f9e23f76 # Parent d433a9cb0089683b8f75458807c5437341f2cdcc Add gtags target for xen/Makefile. Also update .hgignore. Signed-off-by: Wei Liu <wei.liu2@citrix.com> diff --git a/.hgignore b/.hgignore --- a/.hgignore +++ b/.hgignore @@ -23,6 +23,7 @@ ^\.config$ ^\.pc

On Unisys 16X 16GB ES7000/one with SLES10 Beta11 updated to xen changeset 9998, attempted to create a 2GB domU and get Error: The privileged domain did not balloon. xm list shows that before the attempt to create the domain, dom0 has 15910 MB memory. After the error, dom0 has dropped down to 13993 MB. Bugzilla number is 650 > Sue Krysan > Linux Systems Group > Unisys Corporation >

Add GS base to the HVM VCPU context returned by xc_vcpu_getcontext() Signed-off-by: Aravindh Puthiyaparambil <aravindh@virtuata.com> diff -r e62ab14d44af -r babbb3e0f4d3 xen/arch/x86/domctl.c --- a/xen/arch/x86/domctl.c Fri Apr 20 11:36:02 2012 -0700 +++ b/xen/arch/x86/domctl.c Fri Apr 20 17:55:49 2012 -0700 @@ -1592,6 +1592,12 @@ void arch_get_info_guest(struct vcpu *v,

Is there a way to modify the build process to make xen-unstable use only 2.6.15 for the Dom0 and DomU kernels and not apply the 2.6.16-rc2 patch with the latest changeset? Thanks, Aravindh Puthiyaparambil Unisys, Tredyffrin PA _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am getting the following build break on changeset 13662. I am compiling on x86_64 SLES10 with gcc 4.1.0. Is there a fix for this? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA make[1]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware'' make[2]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware/rombios'' gcc -o biossums

I have an Adaptec 392320 Ultra320 SCSI adapter. I am running x86_64 SLES9 SP3. When I build x86_64 Xen with just the 2.6-xen kernel + initrd, I am getting the following error on the module load. But if I go back to building separate xenU and xen0 kernels without initrd the device works without any issues. Any idea what is going wrong here? Am I leaving something out of my initrd? Here is the

The Patch I made for SMP dom0 is also applicable to SMP domU. The issue is same for dom0 & domu as they both are compiled from the same code. The dom0 fix I sent earlier also fixes the domU SMP issue. Thanks & Regards, Nitin ------------------------------------------------------------------------ ----------- Open Source Technology Center, Intel Corp >-----Original Message-----

Yes, I saw that problem and removing the vif line or changing it to vif0 fixed it for me. Aravindh > -----Original Message----- > From: wei huang [mailto:huanwei@cse.ohio-state.edu] > Sent: Friday, November 04, 2005 12:14 PM > To: Puthiyaparambil, Aravindh > Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com > Subject: RE: [Xen-users] Error "Device 0

I have a Dell ASC-39230(B) U320 SCSI controller. If I use the linux-2.6-xen kernel I am getting an "Invalid Sequencer interrupt" and the system hangs after this. But if I use the linux-2.6-xen0 kernel it works well. Does anyone know why this is happening and how I can make it go away? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA ACPI: PCI Interrupt

Add cscope support to xen Makefile. While at it, refactor a bit so etags, ctags, and cscope use same method to generate file list. Signed-off-by: Chris Wright <chrisw@osdl.org> --- xen/Makefile | 19 +++++++++++-------- 1 files changed, 11 insertions(+), 8 deletions(-) ===== xen/Makefile 1.78 vs edited ===== --- 1.78/xen/Makefile 2005-03-28 13:51:31 -08:00 +++ edited/xen/Makefile

> > The patch I sent implements the minimum in the balloon driver and we are > currently building sles10 with my patch. > > K. Y I think I missed this patch when you sent it in. Could you please send it again so that I can take a look? Thanks, Aravindh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

CentOS Errata and Security Advisory CESA-2009:1101 cscope security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2009-1101.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/cscope-15.5-16.RHEL3.i386.rpm source: updates/SRPMS/cscope-15.5-16.RHEL3.src.rpm You may update your CentOS-3 i386 installations by running