All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Bug 1636217" <1636217@bugs.launchpad.net>,
	qemu-devel@nongnu.org,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Kevin O'Connor <kevin@koconnor.net>
Subject: Re: [Qemu-devel] [Bug 1636217] Re: qemu-kvm 2.7 does not boot kvm VMs with virtio on top of VMware ESX
Date: Wed, 2 Nov 2016 23:19:35 +0100	[thread overview]
Message-ID: <26d51ec5-7fcd-bf63-5273-a5e74ef840fd@redhat.com> (raw)
In-Reply-To: <20161028082343.20884.81864.malone@gac.canonical.com>

Adding Gerd, Marcel, and Kevin

On 10/28/16 10:23, Fabian Grünbichler wrote:
> I traced this back to the switch to enabling virtio-1 mode by default in
> 2.7 in commit 9a4c0e220d8a4f82b5665d0ee95ef94d8e1509d5
> 
> forcing the old behaviour with a 2.6 machine type works.

I think this issue is a duplicate of the following RHBZ:

https://bugzilla.redhat.com/show_bug.cgi?id=1373154

and the *SeaBIOS* commit that makes it all work again is:

commit 0e21548b15e25e010c362ea13d170c61a3fcc899
Author: Gerd Hoffmann <kraxel@redhat.com>
Date:   Fri Jul 3 11:07:05 2015 +0200

    virtio: pci cfg access

That SeaBIOS commit is part of the SeaBIOS 1.10.0 release.

However, QEMU 2.7 shipped with bundled SeaBIOS 1.9.3 binaries. See QEMU
commits 6e03a28e1cee (part of v2.7.0) and 6e99f5741ff1 (not part of any
tagged release yet).

The fix is probably the following:
- backport SeaBIOS commit 0e21548b15e2 to the stable 1.9 branch, for
  release 1.9.4
- bundle SeaBIOS 1.9.4 binaries with QEMU v2.7.1.

Thanks
Laszlo

  reply	other threads:[~2016-11-02 22:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 14:13 [Qemu-devel] [Bug 1636217] [NEW] qemu-kvm 2.7 does not boot kvm VMs with virtio on top of VMware ESX MartinSteigerwald
2016-10-28  8:23 ` [Qemu-devel] [Bug 1636217] " Fabian Grünbichler
2016-11-02 22:19   ` Laszlo Ersek [this message]
2016-11-03  8:29     ` Gerd Hoffmann
2016-11-02 11:40 ` MartinSteigerwald
2016-11-03  7:35 ` Fabian Grünbichler
2017-11-16  2:24 ` introom
2018-01-30 11:58 ` Adrien
2018-02-23  9:24 ` zzfancy
2018-06-06 11:51 ` Mykola Ivanets
2018-06-06 13:23 ` Martin Steigerwald
2018-06-07 10:12 ` Mykola Ivanets
2018-06-07 17:29 ` Roman Kagan
2018-06-07 17:45 ` Mykola Ivanets
2018-06-08  5:53 ` Thomas Huth

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=26d51ec5-7fcd-bf63-5273-a5e74ef840fd@redhat.com \
    --to=lersek@redhat.com \
    --cc=1636217@bugs.launchpad.net \
    --cc=f.gruenbichler@proxmox.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=marcel@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 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.