All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: kvm@vger.kernel.org, mst@redhat.com, andre.przywara@arm.com,
	will.deacon@arm.com, josh@joshtriplett.org,
	virtualization@lists.linux-foundation.org, penberg@kernel.org
Subject: Re: [RFC] kvmtool: add support for modern virtio-pci
Date: Thu, 19 Nov 2015 15:55:02 +0100	[thread overview]
Message-ID: <1447944902.25140.74.camel__33718.5143646368$1447944933$gmane$org@redhat.com> (raw)
In-Reply-To: <564DD178.9010904@oracle.com>

  Hi,

> That was indeed the ISR field. Fixing that makes seabios reach the same point as
> legacy virtio before failing.
> 
> I don't see the original correspondence about seabios failures you've reported, if
> you want to forward them over we can look at it further.

It was a few months back, when I posted the seabios patches for kvmtool
to both seabios and kvm lists.

Issue #1 is that kvmtool adds a bunch of kernel command line options,
not only for stuff like rootfs configuration, but also to force specific
things the kernel fails to autodetect (or to speedup boot by
shortcutting hardware probing).  Among them is "pci=conf1", without that
the kernel doesn't find a pci bus and therefore also doesn't find the
virtio-{blk,net} devices.

So, when booting with seabios and let grub or another boot loader load
the kernel from the guest disk image those kernel arguments are not
there.  Of course you can boot the image with qemu, add "pci=conf1" to
grub.cfg (maybe others are required too, don't remember exactly), then
try again with kvmtool.  That gets the boot one step further and leads
to ...

Issue #2: virtio kernel drivers fail initialize the virtio devices.
I suspect virtio device reset is not implemented properly and because of
that the state of the device as left by seabios confuses the kernel
driver.  Didn't check that in detail though.

cheers,
  Gerd

  reply	other threads:[~2015-11-19 14:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  5:11 [RFC] kvmtool: add support for modern virtio-pci Sasha Levin
2015-11-18  8:22 ` Gerd Hoffmann
2015-11-18 15:23   ` Sasha Levin
2015-11-18 17:52     ` Gerd Hoffmann
2015-11-18 17:52     ` Gerd Hoffmann
2015-11-19  4:00       ` Sasha Levin
2015-11-19  4:01         ` Sasha Levin
2015-11-19  7:21           ` Gerd Hoffmann
2015-11-19 13:41             ` Sasha Levin
2015-11-19 14:55               ` Gerd Hoffmann [this message]
2015-11-19 14:55               ` Gerd Hoffmann
2015-11-19  7:21           ` Gerd Hoffmann
2015-11-18  8:22 ` Gerd Hoffmann

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='1447944902.25140.74.camel__33718.5143646368$1447944933$gmane$org@redhat.com' \
    --to=kraxel@redhat.com \
    --cc=andre.przywara@arm.com \
    --cc=josh@joshtriplett.org \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=penberg@kernel.org \
    --cc=sasha.levin@oracle.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will.deacon@arm.com \
    /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.