similar to: Crash when setting dom0_mem value

# 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, this patch makes Xen boot with the default dom0_mem value when the given value exceeds available memory, instead Xen panics and reboots. Administrators have a chance to correct dom0_mem (and other parameters if necessary) after Xen is up with default, seeing the warning message. Tested by booting Domain-0. Signed-off-by: Hiroya INAKOSHI <inakoshi.hiroya@jp.fujitsu.com>

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?

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

I want to install Xen 3.3.0 from source code. but I failed in doing that in the following steps 1. download xen from http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz 2. # tar -zxf xen-3.3.0;cd xen-3.3.0 3. # make world ......succeed 4. # cp /boot/config-2.6.18-53.el5 build-linux-2.6.18-xen_x86_64/.config 5. # make linux-2.6-xen-config CONFIGMODE=menuconfig (or xconfig)

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

Hello, I seem to be having some troubles regarding the latest 2.6.31.6 and 2.6.32.9 Xen dom0 pv_ops trees. Our platform: -Xen 3.4.3-rc3 (also tried 3.4.2 on 2.6.31.6 pv_ops dom0) -2.6.32.9 pv_ops dom0 kernel, perhaps a week old checkout from xen/stable git (can provide changeset if requested). -100+ domU''s, all PV. Ever since we switched to a pv_ops dom0 kernel (we were using 2.6.26

Hello All, I finally compiled xen 3.3.0 using make World, installed it but I cannot get it to Boot, I always get kernel panic, kernel not sync kind of errors, I suppose it''s some hard disk or partition issue, my setup is as follows. CentOS 5.2 x86_64 on a HP ML-115 Grub, menu.list Entries CentOS xen''s line title CentOS (2.6.18-92.1.22.el5xen) root

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.

On Fri, 2013-09-06 at 16:39 +0200, Alessandro Vesely wrote: Both sets of log contain stuff like: > Sep 6 15:22:53 pcale kernel: [ 126.828195] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x6 frozen > Sep 6 15:22:53 pcale kernel: [ 126.828199] ata4: SError: { 10B8B } > Sep 6 15:22:53 pcale kernel: [ 126.828201] ata4.00: failed command: SMART > Sep 6 15:22:53 pcale

We''ve been looking in to support of 32bit domains on machines with large amounts of RAM. Working from the ballooning and reservation support added a few years ago: http://lists.xen.org/archives/html/xen-devel/2009-11/msg01277.html 32 bit domains eventually fail to boot with the following Xen complaint: xm create: Error: (4, ''Out of memory'', "panic:

Dear ALL, I have encountered an issue while installing xen4.1.2 from source. No problem encountered while xen installation.While booting towards XEN kernel, i encountered the folowing error ******************** setuproot: moving /dev failed : No such file or directory no fstab,sys mounting internal defaults setuproot: error mounting /proc setuproot: error mounting /sys Kernel

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all

From: David Vrabel <david.vrabel@citrix.com> autoballoon=1 is not recommened if dom0_mem was used to reduce the amount of dom0 memory. Instead of requiring users to change xl.conf if they do this, extend the autoballoon option with a new choice: "auto". With autoballoon="auto", autoballooning will be disabled if dom0_mem was used on the Xen command line. For

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>