similar to: RE: Fix for SMP xen dom0/domU for x86_64

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:

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo xm create breezy -c Using config file "/etc/xen/breezy". Started domain breezy Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 SMP Thu Oct 13 14:56:20 NZDT 2005 kernel direct mapping tables upto 10000000 @ 568000-5ea000 Built 1 zonelists Kernel command line: root=/dev/sda1 ro 4 lockd.udpport=32768

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

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

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

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:

This patch adds a cscope option to the Mini-OS makefile. It also adds "cscope.*" globally to ".hgignore" Signed-off-by Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

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,

Check the return values of the libxc mem_access calls. Free allocated structures (platform_info, domain_info) on errors during initialization and exit. Unbind VIRQ, close event channel and connection to Xen on errors during initialization Signed-off-by: Aravindh Puthiyaparambil <aravindh@virtuata.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> diff -r ea47068fa7a2 -r

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

I get and install the xen-3.0-testing on my futur xenbox (alias Bi-P3 on abit vp6 motherboard) but I have two problems. 1/ I don''t succeed in poweroff the dom0. When the poweroff is started by "shutdown -h now" command the kernel power down all disks devices but It seems the kernel don''t call the "acpi_power_off() alias pm_poweroff()" function for power down

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

Here are the relevant details. all help is greatly appreciated. xenbox linux # uname -a Linux xenbox.localhost 2.6.14-gentoo-r2 #2 Mon Dec 5 16:17:58 Local time zone must be set--see zic manua x86_64 Intel(R) Xeon(TM) CPU 3.00GHzGenuineIntel GNU/Linux xenbox linux # lspci 0000:00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev 0c) 0000:00:00.1 Class ff00: Intel Corporation

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

Sir/Madam, This is Aravindh,final year student of Anna University India.We are carrying on research in Cloud Computing and using Open Nebula toolkit for that;for which we need strong network connectivity. The problem i am facing is that i am not able to ping continuously to other nodes in the network. The connectivity is getting lost after 2-3 minutes. we have inspected the connectivity links ,

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

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 >

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