Re: [xen-ia64-devel] dom0 memory not responding to changing dom0_mem
append=sync_console dom0_mem=262144 -- root=/dev/sda2 3 Thanks I'll try that tomorrow (when I get to work). Thanks, that did work fine, somewhere I missed what that -- did and removed it. - David Brown ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [xen-ia64-devel] dom0 memory not responding to changing dom0_mem
Hi, David My elilo.conf entry looks like this image=vmlinuz-2.6.16.33-xen0 label=2.6.16.33-xen0 vmm=xen-3.0-unstable.gz initrd=initrd-2.6.16.33-xen0.img read-only append=sync_console dom0_mem=262144 root=/dev/sda2 3 I've tried changing dom0_mem to 256M, 128M and the dom0 system keeps coming up with 453M of memory. We need to split options of xen and dom0 with --. So you should use like the following option. append=sync_console dom0_mem=262144 -- root=/dev/sda2 3 Best Regards, Akio Takebe ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[xen-ia64-devel] dom0 memory not responding to changing dom0_mem
I'm having problems changing my dom0 memory usage on the cmdline every time I change the value it seems to ignore it and go to a default 453M of memory. I tried using xm mem-set Domain-0 128 but I then I couldn't start up any domU systems. I get this output from the console when I try to start up a domU after cranking down the dom0 memory usage using xm mem-set (XEN) domain.c:470: arch_domain_create:470 domain 1 pervcpu_vhpt 1 (XEN) tlb_track_allocate_entries:69 allocated 256 num_entries 256 num_free 256 (XEN) tlb_track_create:115 hash 0xf0001bd7c000 hash_size 512 (XEN) ### domain f7d10080: rid=8-c mp_rid=2000 (XEN) arch_domain_create: domain=f7d10080 (XEN) xencomm_paddr_to_maddr: called with bad memory address: 0x14e48000 - iip=0 My elilo.conf entry looks like this image=vmlinuz-2.6.16.33-xen0 label=2.6.16.33-xen0 vmm=xen-3.0-unstable.gz initrd=initrd-2.6.16.33-xen0.img read-only append=sync_console dom0_mem=262144 root=/dev/sda2 3 I've tried changing dom0_mem to 256M, 128M and the dom0 system keeps coming up with 453M of memory. This is all with the current xen-ia64-unstable.hg (I'm not sure if this is the supposed to be the same as xen-3.0.4-testing.hg or not, should I try that as well?). - David Brown ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
