I think it does leak memory although I am not completely sure. What I
am seeing is that it uses almost 2GB of memory, and that it is
(slowly) growing. Before we updated to xen 4.1 (which included a qemu
update), we only had 512MB for dom0.
Right now, we have (24576 is qemu's pid):
$ pmap 24576
$ pmap 24576 | grep /proc/xen/privcmd | wc -l
On Fri, Apr 29, 2011 at 3:42 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Mon, Apr 11, 2011 at 09:54:27AM +0300, Pasi Kärkkäinen wrote:
>> On Mon, Apr 11, 2011 at 08:41:59AM +0800, Sylvain CHEVALIER wrote:
>> > > And did you mean qemu-dm process in dom0 is leaking memory?
>> > >
>> > I believe so. After running the whole week-end, with one instance of
>> > windows 2008 used as a domain controller, qemu-dm uses 2GB of RAM.
>> > Running pmap, I am getting lots of lines like this one:
>> > 00007fcd73f2e000 1024K rw-s- /proc/xen/privcmd
>> > $ pmap 10423| grep /proc/xen/privcmd | wc -l
>> > 1827
>> > Any clue?
>> Ok. So, a summary:
>> - VM has 512 MB of memory: qemu-dm leaks memory.
>> - VM has 4GB of memory: qemu-dm doesn't leak memory.
>> Is that what you meant?
>> btw. is that Windows running any PV drivers or pure HVM with emulated
> Hello again,
> Sylvain: Are you still seeing this qemu-dm memleak problem? Did you resolve
> -- Pasi
Xen-devel mailing list