From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaeyong Yoo Subject: Re: Very strange behavior between balloon driver and network driver (Arndale) Date: Wed, 29 May 2013 11:57:27 +0000 (GMT) Message-ID: <13839965.291331369828647053.JavaMail.weblogic@epml02> Reply-To: jaeyong.yoo@samsung.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: MIME-version: 1.0 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org > >This needs to be a Xen argument, not a dom0 kernel argument. Ah! got it. > >That said I thought that privcmd mmapbatch put back the original page, >perhaps I am mistaken here though. > >> - create domU with config autoballoon="off" > >>You put this in /etc/xen/xl.conf, not the guest config, correct? Yes. I guess the current work-around solution would be commenting out the following two lines, very nasty and introduces memory leak though. Memory leak gives more time than network error for testing xen on Arndale :) In function drivers/xen/balloon.c //if (current_credit()) // schedule_delayed_work(&balloon_worker, 0); Jaeyong