search for: dom0_mem

...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 parameter) considering that I only want to host one or two VM''s? Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

# 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. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 541b0e1a36c8 -r 3174dc24e3ef docs/man/xl.conf.pod.5 --- a/docs/man/xl.conf.pod.5 Tue Nov 27 10:...

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 lines. That seems to happen every time dom0 uses a large amount > of memory. On a modern dom0 ker...

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)   root (hd1,0)   kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen   module /initrd-2.6.31-rc8.img Then disconnected NUL modem cable and loaded Dom0 via : title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/de...

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

...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 "mem=1024M of my GRUB configuration file (menu.lst on SuSE). My dom0 configurations are: - Intel(R) Xeon(TM) CPU 2.80GHz - 1 GiB RAM grub: title XEN root (hd0,0) kernel /xen.gz dom0_mem=192M module /vmlinuz-xen root=/dev/system/root vga=0x314 resume=/dev/syste...

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?

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 Nope, I tried the string you said, and got a crash. I attach the log file again...

...h domain I get an out of memory exception: Not enough memory is available, and dom0 cannot be shrunk any further Each of my domains only uses 256 so I thought there would be sufficient memory for 4 :-/ I am also using ZFS (maybe this is causing problems?) and have tried using the kernel flag: dom0_mem=2048M Any ideas? Thanks, Christian

Is there any reason why I would not want to set dom0-min-mem to 0 or to what I set dom0_mem on my kernel line? Setting to 0 or setting to the same value as dom0_mem disables memory balloon correct? I cant seem to think of a reason why I would want memory ballooning. Also setting dom0-min-mem should that be done in xend-config.sxp or on the kernel command line? -- Nick Anderson <...

...pmod 2.6.18.8-xen # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod --builtin=ata_piix initrd-2.6.18.8-xen.img 2.6.18.8-xen # cp initrd-2.6.18.8-xen.img /boot/ 7. configure grub: default=0timeout=10splashimage=(hd0,0)/grub/splash.xpm.gzhiddenmenutitle xen-dom0 kernel /xen.gz dom0_mem=2097152 module /vmlinuz-2.6.18.8-xen ro root=LABEL=/ rhgb quiet crashkernel=128M@16M module /initrd-2.6.18.8-xen.imgtitle Red Hat Enterprise Linux Server (2.6.18-53.el5) root (hd0,0) kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/ rhgb quiet crashkernel=128M@16M ini...

Are you expecting improvement after  09/15/2009 new-swiotlb commits ? 4097,6144, "No_dom0_mem_specified" don''t look to me to have any. Boris.   _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

# grub.conf generated by anaconda I recently tried installing xen on another machine and I''m getting the "CPU0 is toast rebooting in 5 seconds" message. Reading through past postings, I was hopeful setting the dom0_mem=128M would solve the problem. Unfortunately, it didn''t make a difference. I haven''t fooled with anything on this system -- just a fresh FC4 install, updated everything with yum and tried to get xen going. The machine runs FC4 just fine and has been up for days. If it matters, th...

...as the Xen command line is specifies a fixed dom0 memory allocation and noselfballooning is specified for the kernel and ballooning is also disabled in the xend-config.sxp / xl.conf (one system using xm, another xl) xen command line: placeholder xsave=0 iommu=0 console=vga,com2 com2=115200,8n1 dom0_mem=max:6144m kernel command line: root=/dev/loop0 ro console=tty1 console=hvc0 earlyprintk=xen nomodeset noselfballooning Examining /proc/iomem does show that the dom0 memory allocation is actually 64kb short of 6144Mb: cat /proc/iomem | grep System\ RAM 00010000-0009bfff : System RAM [57344...

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

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 Hardware: Intel DX48BT2<http://www.intel.com/products/desktop/motherboards/DX48BT2/DX48BT2-overview.htm>,8GB ram, quad core 2.8Ghz anyone got...

...to the same error: (XEN) Not enough memory for DOM0 memory reservation Whereafter a poweroff/poweron is the only way ouy. (Machine doesn''t have a reset button, keyboard ctrl-alt-del does not respond) The grub entries are: title Xen 2.0 / XenLinux 2.6.9 kernel (hd0,1)/boot/xen.gz dom0_mem=131072 console=vga module (hd0,1)/boot/vmlinuz-2.6.9-xen0 root=/dev/hda2 ro console=tty0 title Xen2 kernel (hd0,1)/boot/xen.gz dom0_mem=65536 module (hd0,1)/boot/vmlinuz-2.6.8-24.8-xen root=/dev/hda2 vga=0x314 splash=silent desktop resume=/dev/hda1 showopts module (...

...on is too small for kernel image That''s the error message I get after installing FC4 and following the instructions on http://www.fedoraproject.org/wiki/FedoraXenQuickstart running kernel - 2.6.13.1. I partitioned Fedora to have 6GB on a 30GB drive. I have tried adjusting dom0_mem=256M on a system that has 1GB of RAM and still no luck Any thoughts? -Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...der tries to install Xen but after a while it crashes and starts rebooting recursively. I have tried both the entries listed below. I am using the following entries in the grub.conf file: title Xen-bhatia 3.0 / XenLinux-bhatia 2.6.16 root (hd0,0) kernel /bhatia/boot/xen-3.0.gz dom0_mem=262144 console=ttyS0,9600n8 console=tty0 module /bhatia/boot/vmlinuz-2.6-xen root=/dev/VolGroup00/LogVol00 rhgb quiet console=ttyS0,9600n8 console=tty0 title Xen 3.0 / XenLinux 2.6.16 root (hd0,0) kernel /xen.gz dom0_mem=262144 console=ttyS0,9600n8 console=tty0 modul...