> http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Virtualization%20Tools&component=libvirt
https://bugzilla.redhat.com/show_bug.cgi?id=1330598
But how (and why) start any service by systemd from top node can
affect /machine.slice/machine-lxc subtree ?
And what is special in start of di
On 04/26/2016 10:01 AM, mxs kolo wrote:
>> Cool, thanks for the info! Does this still affect libvirt 1.3.2 as well? You
>> mentioned elsewhere that you weren't hitting this issue with that version
> Sorry, I miss version and another details.
> Test make on CentOS Linux release 7.2.1511 (Core)
> and
>Cool, thanks for the info! Does this still affect libvirt 1.3.2 as well? You
>mentioned elsewhere that you weren't hitting this issue with that version
Sorry, I miss version and another details.
Test make on CentOS Linux release 7.2.1511 (Core)
and libvirt 1.3.2, build from sources with next optio
On Tue, Apr 26, 2016 at 02:44:19PM +0300, mxs kolo wrote:
> Now reporduced with 100%
> 1) create contrainer with memory limit 1Gb
> 2) run inside simple memory test allocator:
[snip example]
I've seen this behaviour with LXC when running systemd inside the
container. /proc/meminfo is generated by
On 04/26/2016 07:44 AM, mxs kolo wrote:
> Now reporduced with 100%
> 1) create contrainer with memory limit 1Gb
> 2) run inside simple memory test allocator:
> #include
> #include
> #include
> #define MB 1024 * 1024
> int main() {
> int total = 0;
> while (1) {
> void *p = malloc( 100*MB
Now reporduced with 100%
1) create contrainer with memory limit 1Gb
2) run inside simple memory test allocator:
#include
#include
#include
#define MB 1024 * 1024
int main() {
int total = 0;
while (1) {
void *p = malloc( 100*MB );
memset(p,0, 100*MB );
total = total + 100;
pri
On 03/25/2016 03:17 AM, mxs kolo wrote:
I found a download for this version and tried it out but we ran into a
different set of problems when running our software in containers under
this environment.
What kind problem ? Network ?
That's a good question and I don't have a good short answer. We
>> I found a download for this version and tried it out but we ran into a
>> different set of problems when running our software in containers under
>> this environment.
What kind problem ? Network ?
b.r.
Maxim Kozin
___
libvirt-users mailing list
libv
>> The latest version available for CentOS/RHEL is version 1.2.17. What
>> site are you using to get the rpm for version 1.3.2?
build from source rpm's
> I found a download for this version and tried it out but we ran into a
> different set of problems when running our software in containers under
On 03/24/2016 05:48 AM, Peter Steele wrote:
On 03/24/2016 02:26 AM, mxs kolo wrote:
use libvirt 1.3.2, it's more stable and never show negative values
for memory and swap inside container
The latest version available for CentOS/RHEL is version 1.2.17. What
site are you using to get the rpm for
On 03/24/2016 02:26 AM, mxs kolo wrote:
use libvirt 1.3.2, it's more stable and never show negative values
for memory and swap inside container
The latest version available for CentOS/RHEL is version 1.2.17. What
site are you using to get the rpm for version 1.3.2?
Peter
Hi all
> Has anyone seen this issue? We're running containers under CentOS 7.2
> and some of these containers are reporting incorrect memory allocation
> in /proc/meminfo. The output below comes from a system with 32G of
> memory and 84GB of swap. The values reported are completely wrong.
yes, it's
On 03/23/2016 11:26 AM, Cole Robinson wrote:
Even if you don't reproduce on RHEL/Fedora, it would be useful if you figure
out exactly what steps it takes to reproduce: is it random, or after a set
amount of time, or after machine suspends, or some manual way to tickle the
issue.
Thanks,
Cole
I
On 03/23/2016 01:41 PM, Peter Steele wrote:
> On 03/23/2016 09:19 AM, Cole Robinson wrote:
>> On 03/23/2016 12:10 PM, Peter Steele wrote:
>>> Has anyone seen this issue? We're running containers under CentOS 7.2 and
>>> some
>>> of these containers are reporting incorrect memory allocation in
>>>
On 03/23/2016 09:19 AM, Cole Robinson wrote:
On 03/23/2016 12:10 PM, Peter Steele wrote:
Has anyone seen this issue? We're running containers under CentOS 7.2 and some
of these containers are reporting incorrect memory allocation in
/proc/meminfo. The output below comes from a system with 32G of
On 03/23/2016 12:10 PM, Peter Steele wrote:
> Has anyone seen this issue? We're running containers under CentOS 7.2 and some
> of these containers are reporting incorrect memory allocation in
> /proc/meminfo. The output below comes from a system with 32G of memory and
> 84GB of swap. The values rep
16 matches
Mail list logo
