search for: es7000

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@list...

...quot;, { - DMI_MATCH(DMI_BIOS_VENDOR, "HP"), - DMI_MATCH(DMI_BIOS_VERSION, "P44-"), - }}, - - { force_bigsmp, "HP ProLiant DL740", { - DMI_MATCH(DMI_BIOS_VENDOR, "HP"), - DMI_MATCH(DMI_BIOS_VERSION, "P47-"), - }}, - { force_bigsmp, "UNISYS ES7000-ONE", { - DMI_MATCH(DMI_PRODUCT_NAME, "ES7000-ONE") - }}, - - { } -}; - - static __init int probe_bigsmp(void) { /* @@ -47,8 +20,7 @@ static __init int probe_bigsmp(void) if (acpi_gbl_FADT.flags & (ACPI_FADT_APIC_CLUSTER | ACPI_FADT_APIC_PHYSICAL)) def_to_bigs...

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

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

A while ago (I think at the Xummit), I recall someone saying that the structure of the files in xenlinux may change soon so that the xen-specific files would move to a subdirectory or arch/<arch> (e.g. linux/arch/i386/xen instead of linux/arch/xen/i386). Is this still planned? If so, what is the timing? If it''s in progress, I''d like to get in the loop... Thanks, Dan

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

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

Hi Raj, I also meet the same python problem when create VMX in FC3-x86_64 xen0. But python error doesn''t happen in RHEL4U1-x86_64 xen0. Are your two computers all SLES9? Thanks, Yongkang You(Kangkang) > >All. > >I am running Xen on an ES7000 system with 4 procs and 4 GB memory. >I am running Suse Sles-9 (32-bit) on the machine. > >I have compiled Xen (the tip on the unstable tree : 6552) with PAE >enabled (XEN_TARGET_X86_PAE=y). >The system boots fine. > >I started xend and when I tried to bring up a virtual machin...

The host server halts upon shutdown of 126000mb domU (64-bit SLES10). It booted fine and was able to run kernbench. However, during shutdown the host crashes. Host is Unisys ES7000 host with 32 processors and 128gb memory using x86_64 SLES10 with xen-unstable c/s 15080. Reducing the memory allocation for the domU to 124000mb works fine. My guess is that specifying 126000 does not leave enough memory for the hypervisor to do its required work at shutdown, so shouldn'&...

Using 3.1.2 c/s 15492 on Unisys ES7000 configured with 32 processors and 128 gb memory, I attempted to start a 160 gb domU. The xm create command hangs, as well as any other xm commands that are issued. If I do ctl-c of the hanging xm create command, I am able to terminate it and then xm commands are once again functional. I expec...

...omU 16domU --------------------------------------- with 14000 25900 39500 49000 without 13900 24950 34900 38500 --------------------------------------- %gain +0.8% +3.8% +13.2% +27.0% I''ve also been working with Raj at Unisys to test out the NUMA patches on their ES7000. Just today Raj confirmed that the previous "dom0 slowdown" that had been reported has been reproduced without the NUMA patches. I believe there are no outstanding machines that have tested the NUMA patches that have any issues. I would like to see the NUMA patches included in xen-unst...

Hi, I am a Masters student from Carnegie Mellon University. I am looking for a research topics for an Advanced OS & DS course we have. I wanted to know what is the current support for NUMA on Xen ? Does it support the IBM x440 and AMD64 Opteron ? Also, does the Xen scheduler do NUMA aware scheduling so it does not degrade the VM performace ? My group is currently looking into Scheduling

...hile >> > > booting processor 1/1. This is in spite of the fact that I have set >> > > vcpus to 4 in the DomU configuration file. I confirmed that the DomU >> > > kernel was compiled with SMP turned on. I am seeing this on the Dell >> and >> > > ES7000 x86_64 boxes. Is anyone else seeing this issue or am I doing >> > > something wrong? >> > >> > I am seeing it, too: >> > [root@bl2-10 ~]# xm create -c /tmp/xen/test.cfg >> > Using config file "/tmp/xen/test.cfg". >> > Started domain...

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the f...

# HG changeset patch # User Hollis Blanchard <hollisb@us.ibm.com> # Date 1158780052 18000 # Node ID f7d90f962967a5a94fce0c04f8fcac449f36344f # Parent 041be3f6b38e05f904d240630c18cadb1259317b [XEND] Remove hard tabs. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> diff -r 041be3f6b38e -r f7d90f962967 tools/python/xen/xend/XendDomainInfo.py ---

* Greg KH (greg@kroah.com) wrote: > > Who said that? Please smack them on the head with a broom. We are all > > actively working on implementing Rusty's paravirt-ops proposal. It > > makes the API vs ABI discussion moot, as it allow for both. > > So everyone is still skirting the issue, oh great :) No, we are working closely together on Rusty's paravirt ops

* Greg KH (greg@kroah.com) wrote: > > Who said that? Please smack them on the head with a broom. We are all > > actively working on implementing Rusty's paravirt-ops proposal. It > > makes the API vs ABI discussion moot, as it allow for both. > > So everyone is still skirting the issue, oh great :) No, we are working closely together on Rusty's paravirt ops

Hello, We''re running Xen Unstable changeset 15468 with SLES10 on a Unisys ES7000/one 56x cpu and 160GB memory. Xen is built with NR_DYNIRQS=1024 and max_phys_cpus=64, and booted with dom0_mem=1024 and xenheap_megabytes=64. We have 320 para-virtualized SLES10 VMs on external storage. Our script starts a VM, waits for the start to complete, then starts the next: "for i in...

Attached patch fixes a problem in marshaling large integers. It seems to only occur on systems with very large memory. However, on those systems, it''s a show-stopper. I see this as a temporary solution until we can sanitize the XML-RPC functions and get rid of all the S-Expression stuff. I''ll run xm-test tomorrow against it. Right now I''ve only done basic

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not