From: Pavel Fedin <p.fedin@samsung.com>
To: qemu-devel@nongnu.org
Cc: "'Michael S. Tsirkin'" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH] vhost: Fix aborting if KVM does not support eventfds
Date: Fri, 13 Nov 2015 12:28:10 +0300 [thread overview]
Message-ID: <002301d11df5$9d440a10$d7cc1e30$@samsung.com> (raw)
If you happen to have a stock kernel of old version, like 3.x, and you
attempt to enable vhost by setting vhost=on, qemu aborts with error:
kvm_mem_ioeventfd_add: error adding ioeventfd: Function not implemented
This patch adds capability check, so that vhost gets disabled instead. A
warning is displayed, explaining the reason.
This problem can be observed with libvirt, which checks for /dev/vhost-net
availability and just inserts "vhost=on" automatically in this case.
Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
---
hw/virtio/vhost.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
index 1794f0d..3121e19 100644
--- a/hw/virtio/vhost.c
+++ b/hw/virtio/vhost.c
@@ -24,6 +24,7 @@
#include "hw/virtio/virtio-bus.h"
#include "hw/virtio/virtio-access.h"
#include "migration/migration.h"
+#include "sysemu/kvm.h"
static struct vhost_log *vhost_log;
static struct vhost_log *vhost_log_shm;
@@ -1083,6 +1084,11 @@ int vhost_dev_enable_notifiers(struct vhost_dev *hdev, VirtIODevice *vdev)
r = -ENOSYS;
goto fail;
}
+ if (!kvm_eventfds_enabled()) {
+ error_report("KVM does not support MMIO eventfds");
+ r = -ENOSYS;
+ goto fail;
+ }
for (i = 0; i < hdev->nvqs; ++i) {
r = k->set_host_notifier(qbus->parent, hdev->vq_index + i, true);
--
1.9.5.msysgit.0
next reply other threads:[~2015-11-13 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 9:28 Pavel Fedin [this message]
2015-11-14 19:18 ` [Qemu-devel] [PATCH] vhost: Fix aborting if KVM does not support eventfds Michael S. Tsirkin
2015-11-16 7:02 ` Pavel Fedin
2015-11-16 7:16 ` Michael S. Tsirkin
2015-11-16 7:31 ` Pavel Fedin
2015-11-16 14:34 ` Christian Borntraeger
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='002301d11df5$9d440a10$d7cc1e30$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).