From: Alex Williamson <alex.williamson@redhat.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: vfio problem
Date: Fri, 08 Jun 2012 11:35:07 -0600 [thread overview]
Message-ID: <1339176907.26976.109.camel@ul30vt> (raw)
In-Reply-To: <4FD22F47.908@01019freenet.de>
On Fri, 2012-06-08 at 18:58 +0200, Andreas Hartmann wrote:
> Hello Alex,
>
> You can probably say, what this message on host side means:
>
> kernel: [ 3902.124109] vfio_dma_do_map: RLIMIT_MEMLOCK (65536) exceeded
We've hit the limit of locked pages. Are you trying to run as root or a
normal user? If the latter, you need to play with ulimits to increase
the size.
> The WLAN card in the VM doesn't work any more. It came up after a few
> times of restarting the VM (with unbinding / rebinding - procedures).
Do I recall correctly you reporting a message about the device not
supporting reset for the WLAN?` Unfortunately devices are mostly black
boxes as far as VFIO is concerned, so if the device doesn't support
reset and doesn't have it's own device specific reset and doesn't simply
start behaving when we restore config space, there's little for vfio to
do. We do have a bit more flexibility in performing a secondary bus
reset on the bridge since we own everything below the bridge. We
probably need to consider adding a group reset ioctl to take advantage
of that.
> I'll see if it is reproducible. I had to reboot to get it working again.
I'm definitely curious if there's anything cumulative about the locked
memory problem above. Thanks,
Alex
next prev parent reply other threads:[~2012-06-08 17:35 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 [this message]
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
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=1339176907.26976.109.camel@ul30vt \
--to=alex.williamson@redhat.com \
--cc=andihartmann@01019freenet.de \
--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