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 10:23:49 -0500 [thread overview]
Message-ID: <564C9805.8080800@oracle.com> (raw)
In-Reply-To: <1447834972.23726.92.camel@redhat.com>
On 11/18/2015 03:22 AM, Gerd Hoffmann wrote:
> /me goes undust the kvmtool patches for seabios.
>
> (see https://www.kraxel.org/cgit/seabios/commit/?h=kvmtool,
> build with CONFIG_KVMTOOL=y + CONFIG_DEBUG_LEVEL=9)
>
> nilsson kraxel ~# ~kraxel/projects/kvmtool/lkvm run --name seabios
> --firmware /home/kraxel/projects/seabios/out-bios-kvmtool/bios.bin
> --disk /vmdisk/cloud/persistent/Fedora-Cloud-Base-22-20150521.x86_64.raw
> # lkvm run -k /boot/vmlinuz-3.10.0-324.el7.x86_64 -m 448 -c 4 --name
> seabios
Thanks for testing! I didn't even thing about seabios as a testing target.
I tried to do what you described, and built seabios with:
$ cat .config | grep 'KVMTOOL\|DEBUG'
CONFIG_KVMTOOL=y
CONFIG_DEBUG_LEVEL=9
But when booting, it just hangs on:
$ ./lkvm run --firmware ~/seabios/out/bios.bin -d dummy
# lkvm run -k /boot/vmlinuz-4.2.0-17-generic -m 448 -c 4 --name guest-12566
And same result with --virtio-legacy...
What did I miss?
Thanks,
Sasha
next prev parent reply other threads:[~2015-11-18 15:23 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 [this message]
2015-11-18 17:52 ` Gerd Hoffmann
[not found] ` <1447869140.23691.15.camel@redhat.com>
2015-11-19 4:00 ` Sasha Levin
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=564C9805.8080800@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).