All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Rak <brak@gameservers.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu 2.7.0 incompatible with host kernel < 3.19
Date: Tue, 13 Sep 2016 15:10:00 -0400	[thread overview]
Message-ID: <75670f77-d788-7217-52a3-f086061fcb78@gameservers.com> (raw)

I have some KVM hosts that I just upgraded to qemu 2.7.0.  When the host 
is running a kernel newer then 3.19, everything works fine.

If the host is running on something lower then 3.19, some guests fail to 
start.  I noticed this on a Ubuntu 16.04 guest, it fails to find the 
virtio NIC, and this is printed to dmesg:

virtio_net virtio0: virtio: device uses modern interface but does not 
have VIRTIO_F_VERSION_1

Looking around, I found 
https://lists.gnu.org/archive/html/qemu-devel/2015-12/msg00373.html , 
but this does not appear to fully resolve the issue.  Any suggestions 
here?  I'm currently just rolling back the upgrade until we can get the 
kernel upgraded on the rest of the hosts.

             reply	other threads:[~2016-09-13 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 19:10 Brian Rak [this message]
2016-09-13 21:09 ` [Qemu-devel] qemu 2.7.0 incompatible with host kernel < 3.19 Laszlo Ersek
2016-09-14  4:35   ` Michael S. Tsirkin
2016-09-14 13:53     ` Brian Rak

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=75670f77-d788-7217-52a3-f086061fcb78@gameservers.com \
    --to=brak@gameservers.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.