hi.
i have "cacting" machine started with maxmem=1024 and memory=256 (so,
not xm
maxmem ...).
i can''t get it to 1024.
my commands:
xen2 ~ # xm list cacting
Name ID Mem VCPUs State Time(s)
cacting 3 256 1 r----- 3180.0
xen2 ~ # xm mem-set cacting 1024
xen2 ~ # xm list cacting
Name ID Mem VCPUs State Time(s)
cacting 3 256 1 r----- 3180.0
xen2 ~ #
the domain:
xen2 ~ # xm list --long cacting
(domain
(domid 3)
(on_crash restart)
(memory 1024)
(uuid 36d9e2b9-917c-cb36-a340-150222e695ac)
(bootloader_args )
(name cacting)
(maxmem 1024000000)
(cpus (1 2 3))
(on_reboot restart)
(on_poweroff destroy)
(localtime 0)
(vcpus 1)
(bootloader )
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1170934380.64)
(cpu_time 3183.10161632)
(online_vcpus 1)
(cpus (1 2 3))
(cpus (1 2 3))
(cpus (1 2 3))
(cpus (1 2 3))
(cpus (1 2 3))
(image
(linux
(kernel /boot/vmlinuz-default-xen-DomU)
(args ''root=/dev/sda1 ro root=/dev/sda1 ro 3'')
(root ''/dev/sda1 ro'')
)
)
(status 2)
(memory_dynamic_min 256)
(memory_dynamic_max 1024)
(state r-----)
(store_mfn 848024)
(console_mfn 2273983)
(device
(vif
(bridge xenbr1.14)
(mac 00:16:3e:7e:41:02)
(script vif-bridge)
(uuid fe94ec21-c98e-e24c-8c92-12a49b2ac041)
(backend 0)
)
)
(device
(vif
(bridge xenbr1.600)
(mac 00:16:3e:7f:8c:26)
(script vif-bridge)
(uuid bc918d59-eb7f-9935-2c8a-308b2f7a6fac)
(backend 0)
)
)
(device
(vif
(bridge xenbr1.1)
(mac 00:16:3e:78:81:ec)
(script vif-bridge)
(uuid 4c03c7f2-b6e7-1eef-fab7-71de21376bb5)
(backend 0)
)
)
(device
(vbd
(uname phy:/dev/XenVolume/cacting)
(uuid 982b666a-1ea0-3a4c-2881-9199693d4cbc)
(mode w)
(dev /dev/sda1:disk)
(backend 0)
)
)
(device
(vbd
(uname phy:/dev/XenVolume/cacting-swap)
(uuid 7cc2e8f5-ea7c-c972-0ba4-bf4988444503)
(mode w)
(dev /dev/sda2:disk)
(backend 0)
)
)
)
many thanks
Daniele
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Daniele Palumbo wrote:> hi. > > i have "cacting" machine started with maxmem=1024 and memory=256 (so, not xm > maxmem ...). > i can''t get it to 1024.Try the following additional setting in your domain config. --<snip>-- extra = "mem=1024M" --<snap>-- AFAIK that will be unnecessary in the next release - 3.0.5. Note that this setting may break migration for some reason. Greetings, -timo -- Timo Benk - Jabber ID: fry@downtempo.de - ICQ ID: #414944731 PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Timo Benk wrote:> Daniele Palumbo wrote: >> hi. >> >> i have "cacting" machine started with maxmem=1024 and memory=256 (so, not xm >> maxmem ...). >> i can''t get it to 1024. > Try the following additional setting in your domain config. > > --<snip>-- > extra = "mem=1024M" > --<snap>-- > > AFAIK that will be unnecessary in the next release - 3.0.5. > > Note that this setting may break migration for some reason.Correction: You don''t need that in 3.0.4. Just reduce the Dom0-memory, than it should work. # xm mem-set Domain-0 512 # xm mem-set Domain-U 512 HTH, greetings, -timo -- Timo Benk - Jabber ID: fry@downtempo.de - ICQ ID: #414944731 PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday 08 February 2007 14:39, Timo Benk wrote:> You don''t need that in 3.0.4. > > Just reduce the Dom0-memory, than it should work. > > # xm mem-set Domain-0 512 > # xm mem-set Domain-U 512that was. i think that this is not so good... dom0 should reduce himself also when i do a mem-set around in the world... bye d. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users