On Thu, Jun 03, 2010 at 02:30:36AM -0700, Fantu wrote:
>
> Now i have update kernel to last of xen/stable2.6.32.x
> DomU disk is with blktap2 (tap2:aio)
> 13 domU hvm (windows xp with gplpv 0.11.213) running
> dom0 ram decrease to 1.5 gb:
> ------------------------
> #free
> total used free shared buffers cached
> Mem: 1563136 1485024 78112 0 35960 1155452
^^^^^^^
1.1 GB is used as cache (which is bypassed by both phy: and tap:aio drivers),
so you'd basicly need only around 512 MB for dom0.
-- Pasi
> -/+ buffers/cache: 293612 1269524
> Swap: 2097144 0 2097144
> ------------------------
> Some error show on boot mainly about ioapic and acpi, here dmesg:
> http://old.nabble.com/file/p28765188/dmesg dmesg
> What these messagges are related to? Kernel, xen or bios?
>
>
>
> Pasi Kärkkäinen wrote:
> >
> > On Fri, May 28, 2010 at 02:45:04AM -0700, Fantu wrote:
> >>
> >> Server is Dell T610 with last bios (2.0.13)
> >> Dom0: Lenny 64 bit, kernel 2.6.32.13, xen 4.0-rc1
> >> Kernel is last commit of jeremy git xen/stable-2.6.32.x with this config:
> >> http://old.nabble.com/file/p28704783/config-2.6.32.13 config-2.6.32.13
> >> lspci -vvv: http://old.nabble.com/file/p28704783/lspcivvv.log
> >> lspcivvv.log
> >> dmidecode: http://old.nabble.com/file/p28704783/dmidecode.log
> >> dmidecode.log
> >> dmesg: http://old.nabble.com/file/p28704783/dmesg dmesg
> >> lsmod: http://old.nabble.com/file/p28704783/lsmod.log lsmod.log
> >> xend log: http://old.nabble.com/file/p28704783/xend.log xend.log
> >> menu.lst:
> >> title Xen 4 / Debian GNU/Linux, kernel 2.6.32.13
> >> root (hd0,0)
> >> kernel /boot/xen.gz dom0_mem=2560M
> >> module /boot/vmlinuz-2.6.32.13 root=LABEL=root-backup2 ro
> >> nomodeset
> >> module /boot/initrd.img-2.6.32.13
> >>
> >> The server run 12 domU windows xp with gplpv 0.11.0.213, all work
> >> On dom0 blktap not work (write about in other topic) and i must chage
> >> domU
> >> disk from tap:aio to file, is one or the problem about performance?
> >> With not set of dom0 memory and dom0 balloning have "freeze" with last
> >> msg
> >> calltrace about out of memory, i set dom0 memory in menu.lst and disable
> >> dom0 balloning, is necessary more ram that 2.5gb for dom0?
> >>
> >
> > You really don't need 2,5 GB for dom0.
> > Start with 1024 MB. You might be able to go down to 512 MB or so.
> >
> > It really depends what kind of tools you run in dom0.
> >
> > Also remember that file: driver for guest disks uses dom0 page cache,
> > so it may appear that a lot of dom0 memory is used when using file: driver
> > since dom0 page cache will use *all* the free memory.. so increasing
> > dom0 memory just makes you use more of the memory as cache.
> >
> > You really should get tap:aio: working instead. But I guess you open
> > another
> > thread about it.
> >
> >> There are some option in .config of kernel wrong or not good?
> >> with c state option in bios enable system is inusable, now i disable it
> >> but
> >> this is kernel, xen or bios problem?
> >>
> >> I hope this information helps improve the kernel and xen, tell me if need
> >> another information
> >>
> >> Thanks for any reply about my questions
> >>
> >
> > -- Pasi
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Low-performance-and-some-problem-with-kernel-2.6.32.13-and-xen-4.0.1-rc1-tp28704783p28765188.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|