On Sun, Mar 14, 2010 at 2:21 AM, Brandon Lamb <brandonlamb@xxxxxxxxx> wrote:
> On Sun, Mar 14, 2010 at 2:03 AM, Brandon Lamb <brandonlamb@xxxxxxxxx> wrote:
>> On Sun, Mar 14, 2010 at 1:49 AM, Brandon Lamb <brandonlamb@xxxxxxxxx> wrote:
>>> On a fresh reboot
>>>
>>> free:
>>> total used free shared buffers cached
>>> Mem: 3371340 448156 2923184 0 5328 77840
>>>
>>> ----------
>>>
>>> top:
>>> Mem: 3371340k total, 449044k used, 2922296k free, 5344k buffers
>>>
>>> ----------
>>>
>>> xentop - 01:44:00 Xen 3.4.3-rc4-pre
>>> 1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
>>> Mem: 4160828k total, 4022996k used, 137832k free CPUs: 4 @ 2308MHz
>>> NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k)
>>> MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR
>>> SSID
>>> Domain-0 -----r 109 2.2 3965032 95.3 no limit n/a
>>> 4
>>>
>>> ----------
>>>
>>> xm mem-set Domain-0 512
>>>
>>> xentop showed ~1G memory (26% memory), then right after this i tried
>>>
>>> xm mem-set Domain-0 192
>>>
>>> ... box died with caps and scroll lock flashing.
>>>
>>> I had dom0_mem=512, dom0-min-mem=192
>>>
>>> xen-3.4-testing-hg and xen/master kernel from jeremy's git repo
>>
>> Rebooted, this time did xm mem-set Domain-0 448, no crashes.
>>
>> xentop - 01:58:54 Xen 3.4.3-rc4-pre
>> 1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
>> Mem: 4160828k total, 1113620k used, 3047208k free CPUs: 4 @ 2308MHz
>> NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k)
>> MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR
>> SSID
>> Domain-0 -----r 123 1.8 1055656 25.4 no limit
>> n/a 4 0 0 0 0 0 0 0 0
>>
>> So this look to me like I *should* have 3 gigs free, why its still
>> saying that its using 1gig is beyond me. Anyhow, now I try to start my
>> guest...
>>
>> xen1:/etc/xen# xm create syslog.cfg
>> Using config file "./syslog.cfg".
>> Error: (4, 'Out of memory', 'xc_dom_alloc_segment: segment ramdisk too
>> large (0xef4f > 0x10000 - 0x26e0 pages)\n')
>>
>> xen1:/etc/xen# cat syslog.cfg
>> kernel = '/boot/vmlinuz-2.6.31.12'
>> ramdisk = '/boot/initrd.img-2.6.31.12'
>> memory = '256'
>> #maxmem = '384'
>> root = '/dev/xvda ro'
>> disk = ['phy:/dev/volumes/syslog,xvda,w']
>> name = 'syslog'
>> vcpus = 1
>> vif = [ 'ip=208.200.248.121, mac=00:16:3E:36:9C:15,
>> bridge=xenbr0, model=e1000' ]
>> vfb = ['vnc=1, vnclisten=0.0.0.0, vncunused=1']
>> serial = 'pty'
>> on_poweroff = 'destroy'
>> on_reboot = 'restart'
>> on_crash = 'restart'
>>
>> /dev/volumes/syslog is on lvm.
>>
>> I dont get it, I had this working fine on another box argh. The last
>> thing I just did was remove all /boot files related to xen, dom0
>> kernel etc, did make uninstall in xen-testing and then copied over
>> tarballs of my working install, then ran the make install and copied
>> my xend-config over. Why does this hate me so
>
> Wow well just had a WTH moment. For s&g I set memory=512 in my
> syslog.cfg... and it STARTED!
>
> No more Error: (4, 'Out of memory', 'xc_dom_alloc_segment: segment
> ramdisk too large (0xef4f > 0x10000 - 0x26e0 pages)\n')
>
> I am totally scratching my head... must be something going on that i
> dont know about
Trying to figure this out logically, so the error message seemed
cryptic but now i am wondering, was I getting this error because I was
trying to start a guest with 256 megs of ram, but the
initrd.img-2.6.31.12 is 72 megabytes by itself, maybe with that and
whatever else is loaded it doesnt fit into the memory slot given? If
thats the case I guess that makes sense why it was failing but now I
can see 448 and even 288 work.
Well I think Im calling it hehe, fresh start tomorrow... err later today
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home