All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109456] KVM VFIO guest X hang with guest kernel > 4.15
Date: Fri, 25 Jan 2019 11:03:28 +0000	[thread overview]
Message-ID: <bug-109456-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1574 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109456

            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 with
the stopping point being 'LoadModule: "dri2"'. I cannot see any relevant errors
in Xorg.log or the KRB - though it's easily reproducible. The system is still
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 causes
this behaviour. With Qemu 3.1 the amount of RAM is irrelevant - the hang always
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 (tested
up to 16GB guest RAM).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2884 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-01-25 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 11:03 bugzilla-daemon [this message]
2019-01-25 15:32 ` [Bug 109456] KVM VFIO guest X hang with guest kernel > 4.15 bugzilla-daemon
2019-04-18 14:12 ` bugzilla-daemon
2019-04-23 10:07 ` bugzilla-daemon
2019-04-23 10:11 ` bugzilla-daemon
2019-04-23 10:13 ` bugzilla-daemon
2019-06-19 11:46 ` bugzilla-daemon
2019-06-19 12:47 ` bugzilla-daemon
2019-07-29 14:16 ` bugzilla-daemon
2019-07-29 14:17 ` bugzilla-daemon

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=bug-109456-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.