RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1257882 - FEAT: support to boot from virtio 1.0 modern devices
Summary: FEAT: support to boot from virtio 1.0 modern devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ovmf
Version: 7.2
Hardware: All
OS: All
low
low
Target Milestone: rc
: ---
Assignee: Laszlo Ersek
QA Contact: aihua liang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-28 10:14 UTC by Xiaoqing Wei
Modified: 2016-11-04 08:39 UTC (History)
9 users (show)

Fixed In Version: ovmf-20160608-1.git988715a.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 08:39:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2608 0 normal SHIPPED_LIVE ovmf bug fix and enhancement update 2016-11-03 15:27:02 UTC

Description Xiaoqing Wei 2015-08-28 10:14:42 UTC 
Description of problem:

virtio-1.0 has finalized spec, and drivers are already included in RHEL kernel.
while booting still no possible due to firmware dont recognize them yet.


Version-Release number of selected component (if applicable):
OVMF-20150414-2.gitc9e5618.el7.noarch
qemu-kvm-rhev-2.3.0-18.el7.x86_64


How reproducible:
1/1

Steps to Reproduce:
1. boot a vm with virtio-1.0 modern mode only
-netdev tap,id=hostnet0,vhost=on \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:17:89:55,bus=pci.2,addr=0x1,disable-legacy=on,disable-modern=off
2.
3.

Actual results:
              dev: virtio-net-pci, id "net0"
                ioeventfd = false
                vectors = 3 (0x3)
                virtio-pci-bus-master-bug-migration = false
                disable-legacy = true
                disable-modern = false
OVMF just no able to boot from it.

Expected results:

OVMF able to boot from virtio-1.0 modern devices.
Additional info:
Comment 2 Xiaoqing Wei 2015-08-28 10:18:31 UTC 
As neither virtio-1.0 nor OVMF would be promoted to fully support in 7.2 GA,

setting M/M.
Comment 3 Laszlo Ersek 2015-08-28 10:28:58 UTC 
I acknowledge this as a feature request, so I'm leaving the BZ open. But, this feature would require immense work in OVMF, with absolutely minimal benefit. Simply remove the "disable-legacy=on" device property from the QEMU command line, and everything will work (the firmware will use the pre-1.0 virtio protocol, while the kernel will use the 1.0 protocol).

I recommend checking out Michael Tsirkin's virtio presentation from the KVM Forum 2015:

http://events.linuxfoundation.org/sites/events/files/slides/misha2015-v1.pdf

I attended that presentation and looked very carefully for signs that would require OVMF to support this. I found none. See especially slide #20 (-> compatibility is guaranteed) and slide #27 (-> the only reason for doing it is "improved robustness", which does not justify the immense amount of work it would take.)

So, just drop "disable-legacy=on". The expected result ("OVMF able to boot from virtio-1.0 modern devices") is ensured by default, using the parallel legacy interface, *unless* you explicitly prevent OVMF from doing that.

Setting Prio / Sev to Low, and Devel Cond-NAK to Capacity.
Comment 5 Laszlo Ersek 2016-03-14 12:55:58 UTC 
Posted upstream patches:
http://thread.gmane.org/gmane.comp.bios.edk2.devel/9150
Comment 6 Laszlo Ersek 2016-04-06 12:42:07 UTC 
Posted the v2 upstream series:
http://thread.gmane.org/gmane.comp.bios.edk2.devel/10264
Comment 7 Laszlo Ersek 2016-04-06 17:24:44 UTC 
V2 committed to upstream edk2: b1bb6f5961d8..3898f4922879.
Comment 11 aihua liang 2016-09-07 11:21:06 UTC 
Has verified, virtio1.0 work normally.

Verified Version:
 Kernel version:3.10.0-504.el7.x86_64
 qemu-kvm-rhev version:qemu-kvm-rhev-2.6.0-22.el7.x86_64
 OVMF version:OVMF-20160608-3.git988715a.el7.noarch
Comment 13 errata-xmlrpc 2016-11-04 08:39:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2608.html
Note You need to log in before you can comment on or make changes to this bug.