public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: vfio problem
Date: Fri, 08 Jun 2012 21:43:13 +0200	[thread overview]
Message-ID: <4FD255D1.5040404@01019freenet.de> (raw)
In-Reply-To: <1339179446.26976.120.camel@ul30vt>

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

  reply	other threads:[~2012-06-08 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 16:58 vfio problem Andreas Hartmann
2012-06-08 17:35 ` Alex Williamson
2012-06-09 13:42   ` Andreas Hartmann
2012-06-09 14:30     ` Alex Williamson
2012-06-09 15:58       ` Andreas Hartmann
2012-06-09 15:32     ` Andreas Hartmann
2012-06-08 17:39 ` Andreas Hartmann
2012-06-08 18:17   ` Alex Williamson
2012-06-08 19:43     ` Andreas Hartmann [this message]
2012-06-09  0:00     ` Andreas Hartmann
2012-06-09 14:09       ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FD255D1.5040404@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox