On 04/26/2016 02:56 PM, Nir Soffer wrote:
> On Tue, Apr 26, 2016 at 4:37 PM, Cole Robinson wrote:
>> On 04/26/2016 09:35 AM, Shahar Havivi wrote:
>>> On 26.04.16 15:30, Shahar Havivi wrote:
On 26.04.16 14:14, Shahar Havivi wrote:
> On 25.04.16 09:11, Cole Robinson wrote:
>> On 04/25/2
On Tue, Apr 26, 2016 at 4:37 PM, Cole Robinson wrote:
> On 04/26/2016 09:35 AM, Shahar Havivi wrote:
>> On 26.04.16 15:30, Shahar Havivi wrote:
>>> On 26.04.16 14:14, Shahar Havivi wrote:
On 25.04.16 09:11, Cole Robinson wrote:
> On 04/25/2016 08:10 AM, Shahar Havivi wrote:
>> On 17.0
> 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 04/26/2016 09:35 AM, Shahar Havivi wrote:
> On 26.04.16 15:30, Shahar Havivi wrote:
>> On 26.04.16 14:14, Shahar Havivi wrote:
>>> On 25.04.16 09:11, Cole Robinson wrote:
On 04/25/2016 08:10 AM, Shahar Havivi wrote:
> On 17.04.16 15:41, Shahar Havivi wrote:
>> Hi,
>> The followi
On 26.04.16 15:30, Shahar Havivi wrote:
> On 26.04.16 14:14, Shahar Havivi wrote:
> > On 25.04.16 09:11, Cole Robinson wrote:
> > > On 04/25/2016 08:10 AM, Shahar Havivi wrote:
> > > > On 17.04.16 15:41, Shahar Havivi wrote:
> > > >> Hi,
> > > >> The following snippet works fine e.g. receiving the
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 26.04.16 14:14, Shahar Havivi wrote:
> On 25.04.16 09:11, Cole Robinson wrote:
> > On 04/25/2016 08:10 AM, Shahar Havivi wrote:
> > > On 17.04.16 15:41, Shahar Havivi wrote:
> > >> Hi,
> > >> The following snippet works fine e.g. receiving the data but when calling
> > >> stream.finish() we get
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 25.04.16 09:11, Cole Robinson wrote:
> On 04/25/2016 08:10 AM, Shahar Havivi wrote:
> > On 17.04.16 15:41, Shahar Havivi wrote:
> >> Hi,
> >> The following snippet works fine e.g. receiving the data but when calling
> >> stream.finish() we get the following error:
> >>
> >> stream = con.newStrea
12 matches
Mail list logo
