From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Hartmann Subject: Re: vfio problem Date: Fri, 08 Jun 2012 21:43:13 +0200 Message-ID: <4FD255D1.5040404@01019freenet.de> References: <4FD22F47.908@01019freenet.de> <4FD238C3.8000505@01019freenet.de> <1339179446.26976.120.camel@ul30vt> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: KVM To: Alex Williamson Return-path: Received: from mout2.freenet.de ([195.4.92.92]:55521 "EHLO mout2.freenet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933432Ab2FHTpq (ORCPT ); Fri, 8 Jun 2012 15:45:46 -0400 In-Reply-To: <1339179446.26976.120.camel@ul30vt> Sender: kvm-owner@vger.kernel.org List-ID: Alex Williamson wrote: > On Fri, 2012-06-08 at 19:39 +0200, Andreas Hartmann wrote: [...] >> - What size should be used for ulimit -l? > > It should be about the size of memory assigned to the guest. Ok, I'm using 256MB, this means, I should try to set ulimit -l to 256MB. Nevertheless, I'm wondering that I don't get the same problem with root. Obviously, the limit is ignored as root. > Once we have libvirt support, all of this should be relatively > transparent as that will take care of the limits setting. For now, it's > a bit of a pain running it as a normal user. If you come up with an > easy way of doing it, please share. Thanks, Hmm, should work like this (I'm already running VM's this way, but without changes to ulimit): Define a new user and run libvirt with this user. For this user context, ulimit can be set to, lets say, 256MB. I'll try it. Thanks for your explanations, Andreas