From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: "Mr. Teo En Ming (Zhang Enming)" <space.time.universe@gmail.com>
Cc: jp.pozzi@izzop.net, xen-devel@lists.xensource.com,
xen-users@lists.xensource.com, Robert Dunkley <Robert@saq.co.uk>
Subject: Re: Re: [Xen-users] Max. PV and HVM Guests
Date: Mon, 9 Nov 2009 14:05:57 +0200 [thread overview]
Message-ID: <20091109120557.GG16033@reaktio.net> (raw)
In-Reply-To: <f712b9cf0911090401o49723f40waf1707e788ef0b20@mail.gmail.com>
On Mon, Nov 09, 2009 at 08:01:00PM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> No, I didn't limit dom0 memory in grub.conf.
>
You should.
If dom0 has all the memory at boot time, you need to balloon down dom0
memory every time you create a new guest - this can (and will) cause
problems with the dom0 linux kernel.
Linux calculates some internal parameters/buffers/values based on the
_boot time_ amount of memory. And when the amount of memory goes down to
only a small fraction of that while creating new guests bad things can
happen..
It still shouldn't crash though.. I bet your problem will get fixed when
you limit the dom0 memory to say dom0_mem=512M and reboot.
-- Pasi
> Here's my xm info output after I have shutdown all the virtual machines.
>
> [root@fedora11-x86-64-host ~]# xm list
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 2812 2 r-----
> 3242.5
> [root@fedora11-x86-64-host ~]# xm info
> host : fedora11-x86-64-host
> release : 2.6.30-rc3-enming.teo-tip
> version : #1 SMP Wed Aug 19 23:14:15 SGT 2009
> machine : x86_64
> nr_cpus : 2
> nr_nodes : 1
> cores_per_socket : 2
> threads_per_core : 1
> cpu_mhz : 2800
> hw_caps :
> bfebfbff:20100800:00000000:00000140:0400e3bd:00000000:00000001:00000000
> virt_caps : hvm hvm_directio
> total_memory : 6039
> free_memory : 3124
> node_to_cpu : node0:0-1
> node_to_memory : node0:3124
> xen_major : 3
> xen_minor : 5
> xen_extra : -unstable
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : Tue Sep 01 11:34:31 2009 +0100 20143:a7de5bd776ca
> xen_commandline : iommu=1
> cc_compiler : gcc version 4.4.1 20090725 (Red Hat 4.4.1-2)
> (GCC)
> cc_compile_by : root
> cc_compile_domain : (none)
> cc_compile_date : Thu Sep 10 07:01:13 SGT 2009
> xend_config_format : 4
>
> --
> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical
> Engineering)
> Alma Maters:
> (1) Singapore Polytechnic
> (2) National University of Singapore
> My Primary Blog: [1]http://teo-en-ming-aka-zhang-enming.blogspot.com
> My Secondary Blog: [2]http://enmingteo.wordpress.com
> My Youtube videos: [3]http://www.youtube.com/user/enmingteo
> Email: [4]space.time.universe@gmail.com
> Mobile Phone (Starhub Prepaid): +65-8369-2618
> Street: Bedok Reservoir Road
> Country: Singapore
>
> On Mon, Nov 9, 2009 at 7:54 PM, Pasi Kärkkäinen <[5]pasik@iki.fi> wrote:
>
> On Mon, Nov 09, 2009 at 06:52:37PM +0800, Mr. Teo En Ming (Zhang Enming)
> wrote:
> > Hi,
> >
> > Please watch this 4-minute video at
> > [1][6]http://www.youtube.com/watch?v=LbLaPpwNAx4
> >
> > I have only started 3 HVM Linux guests with 1 GB ram each. I can't
> start
> > the 4th HVM guest. If I attempt to start the 4th instance, it will
> crash
> > dom0.
> >
> > Are there anything in the xm dmesg output that could explain the
> low limit
> > to the number of VMs that I could start before dom0 becomes
> unresponsive?
> >
>
> Have you limited dom0 memory (by specifying dom0_mem=XMB option in
> grub.conf for xen.gz) ?
>
> What does "xm info" say about free memory before starting any guests?
> -- Pasi
>
> References
>
> Visible links
> 1. http://teo-en-ming-aka-zhang-enming.blogspot.com/
> 2. http://enmingteo.wordpress.com/
> 3. http://www.youtube.com/user/enmingteo
> 4. mailto:space.time.universe@gmail.com
> 5. mailto:pasik@iki.fi
> 6. http://www.youtube.com/watch?v=LbLaPpwNAx4
next prev parent reply other threads:[~2009-11-09 12:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 11:45 Max. PV and HVM Guests Mr. Teo En Ming (Zhang Enming)
2009-11-08 11:46 ` Mr. Teo En Ming (Zhang Enming)
2009-11-08 13:01 ` Moi meme
2009-11-09 8:17 ` [Xen-users] " Robert Dunkley
2009-11-09 10:52 ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 11:53 ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 11:54 ` [Xen-devel] " Pasi Kärkkäinen
2009-11-09 12:01 ` Re: [Xen-users] " Mr. Teo En Ming (Zhang Enming)
2009-11-09 12:05 ` Pasi Kärkkäinen [this message]
2009-11-09 12:14 ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 12:18 ` Pasi Kärkkäinen
2009-11-09 13:10 ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 14:37 ` [Xen-devel] " Mr. Teo En Ming (Zhang Enming)
2009-11-08 13:50 ` Pasi Kärkkäinen
2009-11-08 16:30 ` [Xen-devel] " Grant McWilliams
2009-11-09 3:35 ` Mr. Teo En Ming (Zhang Enming)
2009-11-09 15:06 Re: [Xen-users] " Nick Couchman
2009-11-09 15:18 ` [Xen-devel] " Keir Fraser
2009-11-09 15:29 ` Re: [Xen-users] " Nick Couchman
2009-11-09 15:17 [Xen-devel] " Pasi Kärkkäinen
2009-11-09 15:24 ` Keir Fraser
2009-11-09 15:27 ` Re: [Xen-users] " Pasi Kärkkäinen
2009-11-09 15:39 ` Dan Magenheimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091109120557.GG16033@reaktio.net \
--to=pasik@iki.fi \
--cc=Robert@saq.co.uk \
--cc=jp.pozzi@izzop.net \
--cc=space.time.universe@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.