[xen-tools] Re: xen-create-image memory usage leads to kernel oops

[Anton Melser]

I haven't had any memory problems at all with xen-create-image. I
suspect this may be a Gutsy issue with the beta versions they are
using. I don't think the Ubuntu kernel guys track the upstream closely
enough... at least kvm/qemu seems to be broken as a result, and I
can't see any reason why xen would be any better.
Cheers
Anton

On 09/09/2007, Peter de Kraker <peterdekraker at planet.nl> wrote:
> Hello everybody,
>
> I have been experimenting with Xen on Ubuntu Gutsy with a dual P3 server
> with 1.25Gb RAM.
> Unfortunately I haven't been able to get a virtual instance up and running.
>
> The problem is that when I use xen-create-image it always generates a
> kernel oops.
> It looks like it has to do with the memory consumption because all the
> available memory is consumed when using xen-create-image. Often I get a
> pdflush process that hangs and sometimes it just stalls.
>
> Is it normal that xen-create-image (using loop and debootstrap) uses
> that much memory?
>
> TIA,
>
> Peter
>
>
>


-- 
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc
This will help you for 99.9% of your problems ...