From owner-freebsd-bugs@freebsd.org Thu Apr 4 03:03:10 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B4DF155F0F1 for ; Thu, 4 Apr 2019 03:03:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0C3F3812D8 for ; Thu, 4 Apr 2019 03:02:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C42EA155EFDD; Thu, 4 Apr 2019 03:02:54 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89B57155EFDC for ; Thu, 4 Apr 2019 03:02:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 762CE81234 for ; Thu, 4 Apr 2019 03:02:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B428418442 for ; Thu, 4 Apr 2019 03:02:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3432LN2006878 for ; Thu, 4 Apr 2019 03:02:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3432LUu006864 for bugs@FreeBSD.org; Thu, 4 Apr 2019 03:02:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236922] Virtio fails as QEMU-KVM guest with Q35 chipset on Ubuntu 18.04.2 LTS Date: Thu, 04 Apr 2019 03:02:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tommyhp2@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2019 03:03:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236922 --- Comment #9 from Tommy P --- (In reply to Bryan Venteicher from comment #8) Hi Bryan, Thank you for the feedback. I've been digging further to learn more about = the FreeBSD's internal while improving my C/C++ skills. I've found that there = are 2 sets of device IDs: PCI (which FreeBSD currently support) and the PCIe (which I think your work would support). I'll give them a try a report bac= k if I've found any issue. While doing a lot of trial and error, I've found something puzzling. If I build my custom kernel w/o debug, traces, and netmap (in addition to unnecessary drivers), pciconf shows correctly for the PCIe root: pcib1@pci0:0:2:0: class=3D0x060400 card=3D0x00001b36 chip=3D0x000c1b3= 6 rev=3D0x00 hdr=3D0x01 vendor =3D 'Red Hat, Inc.' device =3D 'QEMU PCIe Root port' class =3D bridge subclass =3D PCI-PCI cap 10[54] =3D PCI-Express 2 root port max data 128(128) ARI disabled link x1(x1) speed 2.5(2.5) ASPM disabled(L0s) slot 0 power limit 0 mW HotPlug(present) surprise Attn But= ton PC(on) EI(disengaged) cap 11[48] =3D MSI-X supports 1 message Table in map 0x10[0x0], PBA in map 0x10[0x800] cap 0d[40] =3D PCI Bridge card=3D0x00001b36 ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected However, when added back in the debug, traces, and netmap (still w/o the ex= tra drivers) similar to the GENERIC kernel, that same controller becomes: none0@pci0:0:2:0: class=3D0x060400 card=3D0x00001b36 chip=3D0x000c1b3= 6 rev=3D0x00 hdr=3D0x01 vendor =3D 'Red Hat, Inc.' device =3D 'QEMU PCIe Root port' class =3D bridge subclass =3D PCI-PCI bar [10] =3D type Memory, range 32, base 0xfd212000, size 4096, enabl= ed bus range =3D 1-1 window[1c] =3D type I/O Port, range 16, addr 0xe000-0xdfff, disabled window[20] =3D type Memory, range 32, addr 0xfd000000-0xfd1fffff, enabl= ed window[24] =3D type Prefetchable Memory, range 64, addr 0xfea00000-0xfebfffff, enabled cap 10[54] =3D PCI-Express 2 root port max data 128(128) ARI disabled link x1(x1) speed 2.5(2.5) ASPM disabled(L0s) slot 0 power limit 0 mW HotPlug(present) surprise Attn But= ton PC(on) EI(disengaged) cap 11[48] =3D MSI-X supports 1 message Table in map 0x10[0x0], PBA in map 0x10[0x800] cap 0d[40] =3D PCI Bridge card=3D0x00001b36 ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected as seen from pciconf. Note how it's 'pcib1' w/o debug+traces and 'none0' w= ith debug+traces. I don't know if the bug is with the VirtIO driver or the debug/trace. Perhaps its by design? This from src r345840. --=20 You are receiving this mail because: You are the assignee for the bug.=