[pve-devel] balloon bug in qemu 2.1 ?

[Andrew Thrift]

Hi Alexandre,

This may be the cause of the crashes we have been experiencing.    We
reported them here:

http://forum.proxmox.com/threads/21276-Kernel-Oops-Panic-on-3-10-5-and-3-10-7-Kernels

These only started happening since we moved to qemu-2.1.x and we get the
same output:

# info balloon
balloon: actual=16384 max_mem=16384


and have noticed VM's with only 1-2GB usage in the guest reporting
almost the entire amount of ram used to the host, even though we have
the latest balloon driver loaded and the blnsvr.exe service running.




On Thu, Mar 5, 2015 at 11:33 PM, Alexandre DERUMIER <aderumier at odiso.com>
wrote:

> Hi,
>
> I have see a bug report here:
>
> http://forum.proxmox.com/threads/21111-RAM-Problem-since-Upgrade-to-3-4?p=108367&posted=1#post108367
>
> about balloon.
>
>
> on my qemu 2.2
>
> #info balloon
> balloon: actual=1024 max_mem=2048 total_mem=985 free_mem=895
> mem_swapped_in=0 mem_swapped_out=0 major_page_faults=301
> minor_page_faults=61411 last_update=1425550707
>
>
> same vm with qemu 2.2 + "-machine type=pc-i440fx-2.1"
> #info balloon
> balloon: actual=1024 max_mem=2048
>
>
>
> (Don't have true qemu 2.1 for test currently)
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20150306/ea02e560/attachment.htm>