From: Sasha Levin <sasha.levin@oracle.com>
To: Gerd Hoffmann <kraxel@redhat.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: Wed, 18 Nov 2015 23:00:45 -0500 [thread overview]
Message-ID: <564D496D.2010105@oracle.com> (raw)
In-Reply-To: <1447869140.23691.15.camel@redhat.com>
On 11/18/2015 12:52 PM, Gerd Hoffmann wrote:
> Hi,
>
>> Thanks for testing! I didn't even thing about seabios as a testing target.
>
> Not surprising, support isn't upstream, ran into a bunch of issues[1][2]
> last time I tried to combine the two, ran into some issues and nobody
> seemed to care, so the seabios patches where just sitting in a branch in
> my repo ...
>
>> $ cat .config | grep 'KVMTOOL\|DEBUG'
>> CONFIG_KVMTOOL=y
>> CONFIG_DEBUG_LEVEL=9
>
> Hmm, 'CONFIG_KVMTOOL=y > .config; make olddefconfig' should give you a
> working configuration.
>
> Setting 'CONFIG_DEBUG_LEVEL=9' is useful for trouble-shooting as it
> makes the virtio drivers more verbose, but not mandatory to have.
>
> Serial line support is needed to get output:
>
> CONFIG_DEBUG_SERIAL=y
> CONFIG_DEBUG_SERIAL_PORT=0x3f8
>
> Also I think rom size must be 128k b/c kvmtool expects it to be that
> way:
>
> CONFIG_ROM_SIZE=128
>
> But those are the defaults, and after "make olddefconfig" you should
> already have them ...
It was the ROM_SIZE one as it seems, it was set to 0 here.
Anyways, I debugged it for a bit a found that seabios attempts to write to
the notification BAR, I look further tomorrow to narrow it down and fix it.
Thanks,
Sasha
next prev parent reply other threads:[~2015-11-19 4:00 UTC|newest]
Thread overview: 9+ 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
[not found] ` <1447834972.23726.92.camel@redhat.com>
2015-11-18 15:23 ` Sasha Levin
2015-11-18 17:52 ` Gerd Hoffmann
[not found] ` <1447869140.23691.15.camel@redhat.com>
2015-11-19 4:00 ` Sasha Levin [this message]
2015-11-19 4:01 ` Sasha Levin
2015-11-19 7:21 ` Gerd Hoffmann
[not found] ` <1447917670.25140.3.camel@redhat.com>
2015-11-19 13:41 ` Sasha Levin
2015-11-19 14:55 ` 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=564D496D.2010105@oracle.com \
--to=sasha.levin@oracle.com \
--cc=andre.przywara@arm.com \
--cc=josh@joshtriplett.org \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=penberg@kernel.org \
--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 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).