From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109456] KVM VFIO guest X hang with guest kernel > 4.15 Date: Fri, 25 Jan 2019 11:03:28 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0462053854==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 487A66F390 for ; Fri, 25 Jan 2019 11:03:30 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0462053854== Content-Type: multipart/alternative; boundary="15484142100.ece92dd.5349" Content-Transfer-Encoding: 7bit --15484142100.ece92dd.5349 Date: Fri, 25 Jan 2019 11:03:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D109456 Bug ID: 109456 Summary: KVM VFIO guest X hang with guest kernel > 4.15 Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: libgradev@gmail.com Hi Host: Arch running kernel 4.20.3 / Qemu 3.1 Guest: Ubuntu 18.04.1 (tried Ubuntu 18.10 also) with any kernel after 4.15 Driver: Happens with current stable, git from Padoka PPA and amdgpu-pro 18.= 50 Issue: Vega 64 passed through to guest causes X to hang on boot using 100% = CPU for one of the passed through cores for the Xorg process. X never starts wi= th the stopping point being 'LoadModule: "dri2"'. I cannot see any relevant er= rors in Xorg.log or the KRB - though it's easily reproducible. The system is sti= ll alive and can be ssh'd into. Adding the nomodeset kernel option allows the guest to boot to GUI (albeit without acceleration). Details: With Qemu 3.0 having more than ~12GB RAM assigned to the guest cau= ses this behaviour. With Qemu 3.1 the amount of RAM is irrelevant - the hang al= ways occurs. Believe this is related to one of the GPU reset patches added to the 4.16 kernel as the guest boots fine with Qemu 3.0/3.1 and guest kernel 4.15 (tes= ted up to 16GB guest RAM). --=20 You are receiving this mail because: You are the assignee for the bug.= --15484142100.ece92dd.5349 Date: Fri, 25 Jan 2019 11:03:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 109456
Summary KVM VFIO guest X hang with guest kernel > 4.15
Product DRI
Version XOrg git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter libgradev@gmail.com 

Hi

Host: Arch running kernel 4.20.3 / Qemu 3.1
Guest: Ubuntu 18.04.1 (tried Ubuntu 18.10 also) with any kernel after 4.15
Driver: Happens with current stable, git from Padoka PPA and amdgpu-pro 18.=
50

Issue: Vega 64 passed through to guest causes X to hang on boot using 100% =
CPU
for one of the passed through cores for the Xorg process. X never starts wi=
th
the stopping point being 'LoadModule: "dri2"'. I cannot see any r=
elevant errors
in Xorg.log or the KRB - though it's easily reproducible. The system is sti=
ll
alive and can be ssh'd into.

Adding the nomodeset kernel option allows the guest to boot to GUI (albeit
without acceleration).

Details: With Qemu 3.0 having more than ~12GB RAM assigned to the guest cau=
ses
this behaviour. With Qemu 3.1 the amount of RAM is irrelevant - the hang al=
ways
occurs.

Believe this is related to one of the GPU reset patches added to the 4.16
kernel as the guest boots fine with Qemu 3.0/3.1 and guest kernel 4.15 (tes=
ted
up to 16GB guest RAM).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15484142100.ece92dd.5349-- --===============0462053854== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0462053854==--