Thanks Piotr, the lack of the host-side memory shrinkage after balloon
deflation is interesting anyway, hopefully you may share guest` dmesg
bits from compiled-in balloon to check visible signs of the issue
It is really hard to see dmesg output via vnc console, when kernel is sending
so many
On Tue, Jun 23, 2015 at 3:32 PM, Piotr Rybicki
piotr.rybi...@innervision.pl wrote:
Thanks Piotr, the lack of the host-side memory shrinkage after balloon
deflation is interesting anyway, hopefully you may share guest` dmesg
bits from compiled-in balloon to check visible signs of the issue
It
Thanks, this is an unexpected behavior, because you are starting with
small amount of total memory exposed to a balloon at the beginning and
there should be no issues except if the inflation races with plugging
in new DIMMs (just a wild guess), dmesg output will be helpful there
as I pointed
On Mon, Jun 22, 2015 at 4:30 PM, Piotr Rybicki
piotr.rybi...@innervision.pl wrote:
W dniu 2015-06-19 o 14:01, Andrey Korolyov pisze:
On Fri, Jun 19, 2015 at 2:14 PM, Piotr Rybicki
piotr.rybi...@innervision.pl wrote:
Hello.
Actually it was my mistake.
After some time using memory in
W dniu 2015-06-19 o 14:01, Andrey Korolyov pisze:
On Fri, Jun 19, 2015 at 2:14 PM, Piotr Rybicki
piotr.rybi...@innervision.pl wrote:
Hello.
Actually it was my mistake.
After some time using memory in guest (find /, cp bigfine, etc), res size of
qemu process shrinks to expected value.
Sorry
2015-06-19 15:01 GMT+03:00 Andrey Korolyov and...@xdel.ru:
Please don`t top-post in technical mailing lists. Do you have a
crashkernel-reserved area there in the boot arguments? What
distro/guest kernel are running in this guest and what is dimm
configuration?
disabling crashkernel in my
Hello.
Actually it was my mistake.
After some time using memory in guest (find /, cp bigfine, etc), res
size of qemu process shrinks to expected value.
Sorry for disturbing.
Now i don't see any memory waste in guest and host when using 'base'
memory + 'dimm' memory.
Although i have one
On Fri, Jun 19, 2015 at 2:14 PM, Piotr Rybicki
piotr.rybi...@innervision.pl wrote:
Hello.
Actually it was my mistake.
After some time using memory in guest (find /, cp bigfine, etc), res size of
qemu process shrinks to expected value.
Sorry for disturbing.
Now i don't see any memory waste
Do You see similar results at Your side?
Best regards
Would you mind to share you argument set to an emulator? As far as I
understood you are using plain ballooning with most results from above
for which those numbers are expected. The case with 5+gig memory
consumption for deflated 1G guest
W dniu 2015-06-18 o 00:57, Vasiliy Tolstov pisze:
2015-06-18 1:52 GMT+03:00 Andrey Korolyov and...@xdel.ru:
Whoosh... technically it is possible but it would be an incompatible
fork for the upstreams for both SeaBIOS and Qemu, because the generic
way of plugging DIMMs in is available down to at
2015-06-18 1:52 GMT+03:00 Andrey Korolyov and...@xdel.ru:
Whoosh... technically it is possible but it would be an incompatible
fork for the upstreams for both SeaBIOS and Qemu, because the generic
way of plugging DIMMs in is available down to at least generic 2.6.32.
Except may be Centos where
On Thu, Jun 18, 2015 at 12:21 AM, Vasiliy Tolstov v.tols...@selfip.ru wrote:
2015-06-17 19:26 GMT+03:00 Vasiliy Tolstov v.tols...@selfip.ru:
This is band news =( i have debian wheezy that have old kernel...
Does it possible to get proper results with balloon ? For example by
patching qemu or
2015-06-18 1:40 GMT+03:00 Andrey Korolyov and...@xdel.ru:
Yes, but I`m afraid that I don`t fully understand why do you need this
when pure hotplug mechanism is available, aside may be nice memory
stats from balloon and easy-to-use deflation. Just populate a couple
of static dimms with small
On Thu, Jun 18, 2015 at 1:44 AM, Vasiliy Tolstov v.tols...@selfip.ru wrote:
2015-06-18 1:40 GMT+03:00 Andrey Korolyov and...@xdel.ru:
Yes, but I`m afraid that I don`t fully understand why do you need this
when pure hotplug mechanism is available, aside may be nice memory
stats from balloon
2015-06-17 19:26 GMT+03:00 Vasiliy Tolstov v.tols...@selfip.ru:
This is band news =( i have debian wheezy that have old kernel...
Does it possible to get proper results with balloon ? For example by
patching qemu or something like this?
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
Hi. I have issue with incorrect memory side inside vm. I'm try utilize
memory balloon (not memory hotplug, because i have guest without
memory hotplug (may be)).
When domain started with static memory all works fine, but then i'm
specify in libvirt
memory = 16384 , maxMemory = 16384 and
On Wed, Jun 17, 2015 at 4:35 PM, Vasiliy Tolstov v.tols...@selfip.ru wrote:
Hi. I have issue with incorrect memory side inside vm. I'm try utilize
memory balloon (not memory hotplug, because i have guest without
memory hotplug (may be)).
When domain started with static memory all works fine,
On Wed, Jun 17, 2015 at 6:33 PM, Vasiliy Tolstov v.tols...@selfip.ru wrote:
2015-06-17 17:09 GMT+03:00 Andrey Korolyov and...@xdel.ru:
The rest of visible memory is eaten by reserved kernel areas, for us
this was a main reason to switch to a hotplug a couple of years ago.
You would not be able
2015-06-17 17:09 GMT+03:00 Andrey Korolyov and...@xdel.ru:
The rest of visible memory is eaten by reserved kernel areas, for us
this was a main reason to switch to a hotplug a couple of years ago.
You would not be able to scale a VM by an order of magnitude with
regular balloon mechanism
2015-06-17 18:38 GMT+03:00 Andrey Korolyov and...@xdel.ru:
Currently QEMU memory hotplug should work with 3.8 and onwards.
Mentioned patches are an adaptation for an older frankenkernel of 3.8`
functionality.
This is band news =( i have debian wheezy that have old kernel...
--
Vasiliy
20 matches
Mail list logo
