This thread and the ticket linked by Michael got me curious about whether
we could write our own routine for spawning processes that doesn't invoke
the usual copy-on-write semantics.
The struct returned by exec.Command has a a SysProcAttr field where you can
set (Linux-specific) flags to pass to
On 4 June 2015 at 11:56, Menno Smits menno.sm...@canonical.com wrote:
bigs := make([][]byte, 6)
Note: I was using 6GB because my machine is running a bunch of VMs and has
very little free memory at the moment. With the 14GB allocated in the
example, memory runs out before the program gets
If it is overcommit, this go issue will make for interesting (but
possibly not helpful) reading:
https://github.com/golang/go/issues/5838
On 3 June 2015 at 17:24, Gustavo Niemeyer gust...@niemeyer.net wrote:
Hey John,
It's probably an overcommit issue. Even if you don't have the memory in use,
So interestingly we are already fairly heavily overcommitted. We have 4GB
of RAM and 4GB of swap available. And cat /proc/meminfo is saying:
CommitLimit: 6214344 kB
Committed_AS:9764580 kB
John
=:-
On Wed, Jun 3, 2015 at 9:28 AM, Gustavo Niemeyer gust...@niemeyer.net
wrote:
Ah, and
Hi Michael,
(uvtool author here)
On Tue, Jun 02, 2015 at 09:30:15AM +0100, Michael Foord wrote:
In order to specify a MAC address for a KVM image we need to create a
libvirt domain xml template to pass as the template argument to uvt-kvm.
Right.
Ideally we'd like to specify as *little as
On 03/06/15 09:15, Robie Basak wrote:
Hi Michael,
(uvtool author here)
On Tue, Jun 02, 2015 at 09:30:15AM +0100, Michael Foord wrote:
In order to specify a MAC address for a KVM image we need to create a
libvirt domain xml template to pass as the template argument to uvt-kvm.
Right.
Yeah, I'm pretty sure this machine is on 0 and we've just overcommitted
enough that Linux is refusing to overcommit more. I'm pretty sure juju was
at least at 2GB of pages, where 1G was in RAM and 1GB was in swap. And if
we've already overcommitted to 9.7GB over 6.2GB linux probably decided that
From https://www.kernel.org/doc/Documentation/vm/overcommit-accounting:
The Linux kernel supports the following overcommit handling modes
0 - Heuristic overcommit handling. Obvious overcommits of
address space are refused. Used for a typical system. It
