----- Original Message ----- > From: "Daniel Helgenberger" <[email protected]> > To: "Dan Kenigsberg" <[email protected]> > Cc: [email protected] > Sent: Monday, September 29, 2014 12:25:22 PM > Subject: Re: [ovirt-users] 3.4: VDSM Memory consumption > > Dan, > > I just reply to the list since I do not want to clutter BZ: > > While migrating VMs is easy (and the sampling is already running), can > someone tell me the correct polling port to block with iptables? > > Thanks,
Hi Daniel, there is indeed a memory profiling patch under discussion: http://gerrit.ovirt.org/#/c/32019/ but for your case we'll need a backport to 3.4.x and clearer install instructions, which I'll prepare as soon as possible. As for your question: if I understood correctly what you are asking (still catching up the thread), if you are trying to rule out the stats polling made by Engine to this bad leak, one simple way to test is just to shutdown Engine, and let VDSMs run unguarded on hypervisors. You'll be able to command these VDSMs using vdsClient or restarting Engine. In absence of commands from Engine VDSM will just sit idle and it will not do anything to VMs except it's own sampling. If you are on IRC, on freenode/#vdsm or OFTC/#ovirt, please ping me anytime - see my sign below for my IRC nickname. -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
