similar to: Clustered xAPIC and Unisys ES7000 patch

Using an 8-way ES7000 with 32GB of ram, I''m running xen at changset 11217 with dom0_mem=3092M as a kernel parameter on a x86_64 hyperviser. It appears that qemu is adding too much overhead to virtual machines to display graphics. If I boot a sles9sp3 domVT in runlevel 5 with vga=0x314 for a graphicalboot, and immediately use vncviewer simply to watch the virtual machine as it boots,

Hi, I have buit Xen (32 bit) with PAE and can start multiple Paraguests with 4 gig memory, but cannot launch a single VM with more than 4 gb memory. I would like to launch 1 VM with 30GB or so memory. Are there any config paramters like kernel,/inittrd that need to be changed. I have the ramdisk set to the initrd I used to boot xen with PAE. Thanks - padma

I''ve checked in a patch that will hopefully fix ''acpi=off'' and ''acpi=ht'' modes for domain0. It''s been tested on just one machine so far, so it''d be good to get some wider feedback. :-) -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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:

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

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 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 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 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

> > 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

The DMI checks that force the use of the bigsmp APIC driver are for systems that are no longer supported by Xen (32-bit x86). Signed-off-by: Matt Wilson <msw@amazon.com> Cc: Keir Fraser <keir@xen.org> Cc: Jan Beulich <jbeulich@suse.com> Cc: Andrew Cooper <andrew.cooper3@citrix.com> --- xen/arch/x86/genapic/bigsmp.c | 30 +----------------------------- 1 files changed, 1

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,

We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. issues: - No bocking issues. IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain Can bootup unmodified IA-32 WindowsXP SP1/SP2 in VMX domain Can bootup VMX & XenU with different memory size(VMX:128MB,256MB,512MB.XenU:256MB)

Hi Ian, Natasha and I are interested in helping with the io emulation work for fully virtualized HVM guests you mentioned in your March 12th email: http://lists.xensource.com/archives/html/xen-devel/2006-03/msg00394.html In the post, you mentioned the following tasks: - get minios running on x86_64 - port xenbus/netfront/blkfront to minios - compile qemu-dm into minios - redirect IO to qemu-dm

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

I have always needed the rm_nx_xd patch to boot Xen / Dom0 on the ES7000 x86_64 but the system boots without any issues on plain vanilla Linux 2.6. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Keir Fraser > Sent: Thursday, August 18, 2005 4:49 AM > To: Nakajima, Jun > Cc: Jerone Young;

In a recent conversation one of my coworkers raised a concern about memory limitations when running 32-bit guests on top of the 64-bit hypervisor. At this point the discussion is academic; I don''t know when/if we''ll ever be able to get system resources to test it, to see if the concerns that he expressed are real. So I decided to post this in hope of getting comments from the

This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, calls to hvm_memory_event_cr3 and hvm_memory_event_cr4 were lost. These functions were originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in

Can find documented how many CPUS can Xen support and how many Virtual Machines per CPU are allowed? Can someone please supply this info? -- View this message in context: http://www.nabble.com/Supported--of-CPUs-VMs-per-CPUs-tf2278842.html#a6329630 Sent from the Xen - Dev forum at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I am not able to build the latest x86_64 xen-unstable on SLES9 SP1 x86_64. Here is the build output. Am I doing anything wrong here? Aravindh gcc -DPIC -m64 -Wall -Werror -O3 -fno-strict-aliasing -I ../../tools/libxutil -I. -Wp,-MD,.xc_ptrace.opic.d -fPIC -c -o xc_ptrace.opic xc_ptrace.c In file included from /usr/include/asm/sigcontext.h:4, from