Re: [Xen-users] SLES10SP2 (xen 3.2.x) vs SLES11 (xen 3.4.x)

> > Thanks for the response. I had to change one of these servers back to
> > sles10sp2 as we were trying to use one of the domUs and it kept
> > crashing. The end of the log for the domU gives:
> > 
> > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw 
> > state.
> > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro 
> > state.
> > xc_map_foreign_batch: mmap failed: Cannot allocate memory
> > xc_map_foreign_batch error 12
> > 
> 
> Do you see these in domU or in dom0 ?

Not sure. 

> 
> > Not sure what this means. The host server has 32 gb of RAM and there
> > were only half a dozen domUs running, with only about 5gb of ram
> > assigned. 
> > 
> > It's now running on sles10sp2 dom0 without a problem. I guess it will be
> > a while before we go with sles11. 
> > 
> 
> Did you dedicate fixed amount of memory for dom0? For example 512 MB or
> 1 GB using dom0_mem= parameter for Xen in grub.conf ?
> 

Yes, had that set, but did not have ballooning disabled. I'm going to
try and recreate the issue today and see if disabling ballooning fixes
it. 

Thanks,
James


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-users] OpenSuSE 11.2 bug, dom0-cpus limit causes xenwatch_cb running 100% and xm command freeze and xend dead, Vladislav Karpenko

Next by Date:

[Xen-users] How to use tapdisk, Jack

Previous by Thread:

Re: [Xen-users] SLES10SP2 (xen 3.2.x) vs SLES11 (xen 3.4.x), Pasi Kärkkäinen

Next by Thread:

Re: [Xen-users] SLES10SP2 (xen 3.2.x) vs SLES11 (xen 3.4.x), Joseph Coleman

Indexes:

[Date] [Thread] [Top] [All Lists]