similar to: [PATCH] boot with default on dom0_mem allocation failure.

# HG changeset patch # User inakoshi.hiroya@jp.fujitsu.com # Date 1191287395 -28800 # Node ID 5543e74774a826b1781893982ed5052312b820fc # Parent 83239b2890723e0c06bad507bb273a970784b18e Flush stdout when xentop -b gets SIGINT and SIGTERM. It is useful when you stop xentop -b by keyboard interrupt or by other programs such as killall from a batch script. You would have missed the bottom part of

Since TRC_MEM is defined as 0x000af000 in xen/include/public/trace.h, TRC_MEM = TRC_SCHED | TRC_VMX. I feel strange about this. I do not think scheduling is a part of memory management. Am I right? If not, please tell me the background TRC_MEM is defined as TRC_SCHED | TRC_VMX. If so, please apply this patch. This patch defines TRC_MEM as an independent event mask. In addition, xentrace

Fixed typos in xmexamples. Signed-off-by: Hiroya INAKOSHI <inakoshi.hiroya@jp.fujitsu.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Keir, Attached patch gets rid of the global attr variable and adds support for NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht

# HG changeset patch # User Ian Campbell <ijc@hellion.org.uk> # Date 1354011148 0 # Node ID 3174dc24e3efb0c5b964c244dbfb0218a03a38cf # Parent 541b0e1a36c86db5df04988dd4ade5430776a7f2 xl: xl.conf(5): correct advice re autoballooning vs. dom0_mem. The advice was backwards, you should really disable autoballoon if you use dom0_mem. Also add a reference to the command-line docs.

On Fri 06/Sep/2013 10:12:29 +0200 Ian Campbell wrote: > On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: >> >> I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then >> crashes when used=2837436K free=4127432K. > > On a modern dom0 kernel you need to specify the maximum memory as well, > i.e. dom0_mem=8192M,max:8192M

On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: > Package: xen-hypervisor-4.1-amd64 > Version: 4.1.4-3+deb7u1 > Severity: normal > > I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then > crashes when used=2837436K free=4127432K. > By crash I mean the gnome screen was blown away, replaced by a black screen > with white log

hi folks, anyone around who knows how to setup grub2 to allow at boot time a static memory allocation for the Domain-0. I use debain squeeze, lates update''s and my actual grub2 config doesn''t work automaticlly at boot time. i configured the arg "dom0_mem=4096M" in the grub.cfg section multiboot as shown bellow: *** menuentry ''Debian GNU/Linux, with

Hi all, the throughput measured by netperf differs from time to time. The changeset was xen-unstable.hg C/S 11760. This is observed when I executed a netperf on DomU connecting to a netserver on Dom0 in the same box. The observed throughput was between 185Mbps to 3854Mbps. I have never seen such a difference on ia64. Regards, Hiroya _______________________________________________ Xen-devel

Hello friends! In this week, i had a problem with Xen version 3.0.2_09749-0.7 on SLES10 for x86, when the initrd-xen file was loaded. On console, various messages about "No space left on device" appears later that the "/dev" was monted on a tmpfs filesystem (for udev). The only sollution for this problem at that moment, was remove the "dom0_mem=192M" and the

I have a xVm b75 server and use zfs for storage (zfs root mirror and a raid-z2 datapool.) I see everywhere that it is recommended to have a lot of memory on a zfs file server... but I also need to relinquish a lot of my memory to be used by the domUs. What would a good value for dom0_mem on a box with 4 gig of ram?

I have a xVm b75 server and use zfs for storage (zfs root mirror and a raid-z2 datapool.) I see everywhere that it is recommended to have a lot of memory on a zfs file server... but I also need to relinquish a lot of my memory to be used by the domUs. What would a good value for dom0_mem on a box with 4 gig of ram?

Hello, I have four domU''s that have pci devices pass-true to them (one nic, two gfx cards, one usb controller and one ide controller) and it works grate but ballooning down memory on startup takes along time, so i tried using the dom0_mem command in grub with different memory values but then the host will crash on boot every time. Software: Xen 4.0 with the official xenkernel 2.6.18.8

I''ve installed Xen Hypervisor 3.0.3 (CentOS 5.7, i386) inside Virtualbox 4.1.16 (Mageia 1, i686) and have noticed that Dom0 is consuming 85% of the memory allocated to the VM (1GB) so I''d like to reduce this as much as possible in order to make more room for one or two VM''s. Is there a minimum amount of vRAM that can/should be allocated to Dom0 (using the dom0_mem boot

I tried for a couple of times to add an information that might help you with regard to Bug #603713 by sending mailto "603713 at bugs.debian.org" But it never appeared there - so I try to let you know how to work around that bug this way. If you decide not to take this mail into account I won't bother you any more Regards Andreas -----Urspr?ngliche Nachricht----- Von: Balg, Andreas

Hello, I''ve just installed Fedora Core 4 and I''m now trying to install xen. I''m follwing the redhat quickstart but when I try to boot the xen kernel I get the sam errors as described in a previous message to this list. Nobody has answered, so I thought it was a good idea to repost it... Greetings, I installed Fedora a few weeks ago and have been using the basic

Hi, We have a brand new HP Z820 system which is a E5 based sandy-bridge server with NVIDIA Quadro 600 Graphics card. The machine has 32GB RAM and 8 CPUs (16 with Hyper threading enabled) The system has AMI BIOS 2.07 (the latest). We have enabled Hyper-threading, VT-d, VMX in the BIOS. We installed Ubuntu 12.04 first, followed by, XEN installation (the one that is packaged (4.1) along with

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

Hi All, Running into temporary pauses in our VMs which correspond to these errors in dmesg on the dom0: [1721485.352560] SLUB: Unable to allocate memory on node -1 (gfp=0x20) [1721485.352563] cache: kmalloc-2048, object size: 2048, buffer size: 2048, default order: 3, min order: 0 [1721485.352566] node 0: slabs: 81, objs: 1296, free: 0 [1721485.352576] swapper: page allocation failure:

Are you still able to reproduce this issue? Please could you try with the Xen and Kernel currently in the Jessie release (they ought to install pretty cleanly onto a Wheezy system). Ian.