From: Launchpad Bug Tracker <1851972@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1851972] Re: pc-q35-4.1 and AMD Navi 5700/XT incompatible
Date: Tue, 22 Jun 2021 04:18:42 -0000 [thread overview]
Message-ID: <162433552268.20423.3557039532468519884.malone@loganberry.canonical.com> (raw)
In-Reply-To: 157336268640.31256.1488114867676518393.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1851972
Title:
pc-q35-4.1 and AMD Navi 5700/XT incompatible
Status in QEMU:
Expired
Bug description:
Hello,
I am not sure if this qualifies as a "bug"; it is be more of an
unknown issue with default settings. However, since the default value
of q35 default_kernel_irqchip_split was changed seemingly due to
similar user feedback, I thought this was important to share..
AMD Navi 5700/XT vfio-pci passthrough seems incompatible with
one/multiple settings in pc-q35-3.1 and higher. The workaround for me
is that pc-q35-3.0 still works fine passing through the GPU and
official drivers can load/install fine.
The default/generic GPU drivers in a Fedora 30 or Windows 1903 guest
do work; the monitor displays the desktop in a 800x600 resolution and
things are rendered fine.. so the basic functionality of the card
seems fine with pc-q35-4.1.
But attempting to use the official open source AMD driver with the
card resulted in a hung kernel for the Fedora 30 guest.. and a BSOD on
the Windows 1903 guest immediately during driver install.
I do not see any errors in Qemu command output.. did not investigate
other logs or KVM etc, because I am not sure what to look for or how
to go about it. Also not sure which combination of the latest q35
default settings are valid combinations to try either, because it
seems that multiple things have changed related to pcie-root-port
defaults and other machine options. I am happy to run tests and
provide feedback if that helps identify the issue.
I am using "Linux arch 5.4.0-rc6-mainline" kernel on ArchLinux host
with AMD Navi reset pci quirk patch applied.
My working Qemu command line is this:
QEMU_AUDIO_DRV=pa \
QEMU_PA_SERVER=/run/user/1000/pulse/native \
/usr/bin/qemu-system-x86_64 \
-name windows \
-m 16g \
-accel kvm \
-machine pc-q35-3.0,accel=kvm,pflash0=ovmf0,pflash1=ovmf1 \
-blockdev node-name=ovmf0,driver=file,filename=/virt/qemu/roms/OVMF_CODE.fd,read-only=on \
-blockdev node-name=ovmf1,driver=file,filename=/virt/qemu/machines/windows/OVMF_VARS.fd \
-boot menu=on \
-global kvm-pit.lost_tick_policy=discard \
-no-hpet \
-rtc base=utc,clock=host,driftfix=slew \
-cpu host,kvm=off,hv_vendor_id=RedHatRedHat,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer \
-smp sockets=1,cores=4,threads=1 \
-nodefaults \
-netdev bridge,br=br0,id=net0 \
-device virtio-net-pci,netdev=net0,addr=19.0,mac=52:54:00:12:34:77 \
-device virtio-scsi-pci \
-blockdev raw,node-name=disk0,cache.direct=off,discard=unmap,file.driver=file,file.aio=threads,file.filename=/virt/qemu/machines/windows/os.raw \
-device scsi-hd,drive=disk0,rotation_rate=1 \
-blockdev raw,node-name=disk1,cache.direct=off,discard=unmap,file.driver=file,file.aio=threads,file.filename=/virt/qemu/machines/windows/data.raw \
-device scsi-hd,drive=disk1,rotation_rate=1 \
-drive index=0,if=ide,media=cdrom,readonly,file=/virt/qemu/isos/Win10_1903_V2_English_x64.iso \
-drive index=1,if=ide,media=cdrom,readonly,file=/virt/qemu/isos/virtio-win-0.1.173.iso \
-device ich9-intel-hda,addr=1b.0 \
-device hda-output \
-monitor stdio \
-display none \
-vga none \
-device pcie-root-port,id=pcierp0,chassis=1,slot=1,addr=1c.0,disable-acs=on,multifunction=on \
-device pcie-root-port,id=pcierp1,chassis=2,slot=2,addr=1c.1,disable-acs=on \
-device x3130-upstream,bus=pcierp0,id=pcieu0 \
-device xio3130-downstream,bus=pcieu0,id=pcied0,chassis=11,slot=11 \
-device vfio-pci,host=03:00.0,bus=pcied0,addr=00.0,multifunction=on \
-device vfio-pci,host=03:00.1,bus=pcied0,addr=00.1 \
-device qemu-xhci,addr=1d.0 \
-device usb-host,vendorid=0x258a,productid=0x0001 \
-device usb-host,vendorid=0x1bcf,productid=0x0005 ;
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1851972/+subscriptions
prev parent reply other threads:[~2021-06-22 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 5:11 [Bug 1851972] [NEW] pc-q35-4.1 and AMD Navi 5700/XT incompatible Marshall Porter
2020-01-07 11:02 ` [Bug 1851972] " Philippe Mathieu-Daudé
2020-01-09 6:37 ` Marshall Porter
2020-01-13 2:25 ` Joey Adams
2020-01-31 14:39 ` Joey Adams
2021-04-22 8:52 ` Thomas Huth
2021-06-22 4:18 ` Launchpad Bug Tracker [this message]
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=162433552268.20423.3557039532468519884.malone@loganberry.canonical.com \
--to=1851972@bugs.launchpad.net \
--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.