From: Alex Williamson <alex.l.williamson@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1591628] Re: 2.6.0 hangs linux vm using vfio for pci passthrough of graphics card
Date: Wed, 15 Jun 2016 20:04:25 -0000 [thread overview]
Message-ID: <20160615200425.2555.86123.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20160612072726.11541.54806.malonedeb@wampee.canonical.com
Ran as:
# /usr/local/bin/qemu-system-x86_64 -enable-kvm -M q35 -m 4G -cpu host -smp 8 \
-vga none -device ioh3420,bus=pcie.0,addr=1c.0,port=1,chassis=1,id=root.1 \
-device vfio-pci,host=02:00.0,bus=root.1,x-vga=on,addr=0.0,romfile=/root/HD8570.rom \
-device ahci,bus=pcie.0,id=ahci \
-drive file=/root/qemutest2.img,id=iso,index=0,media=disk,format=raw \
-net none -nographic -monitor stdio -serial none -parallel none
Works fine, memtest86+ works fine too. Are you on an AMD or Intel host?
Can you try with a recent, stock (non-grsecurity) kernel? Can you
reproduce without the assigned USB devices?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1591628
Title:
2.6.0 hangs linux vm using vfio for pci passthrough of graphics card
Status in QEMU:
New
Bug description:
Not a duplicate of my old bug 1488363
qemu version 2.5.1 works fine
qemu version 2.6.0 fails
seabios 1.9.2-1
using kernel 4.5.5 with grsecurity
I built using the arch packaging tools, but commented out all the
patch code, so it should be vanilla.
The problem is just that I start a Linux vm using either my radeon R7
260x or radeon HD 6770, and with qemu 2.6.0, it looks normal until
after the grub menu, and then the screen looks broken (with mostly
black, and some pixely junk spread horizontally in a few places on the
screen... first we thought maybe the monitor died). I'm not sure if
it's before or only at the moment where the screen resolution changes
(I could check that or record it on request). Also, the VM is not
pingable and does not respond to "system_powerdown" on qemu monitor.
However, the same setup works fine with windows 8. And it works fine
without graphics cards passed through. A usb controller passed through
works fine too.
And then I ran a bisect...
2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62 is the first bad commit
commit 2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62
Author: Alex Williamson <alex.williamson@redhat.com>
Date: Thu Mar 10 09:39:08 2016 -0700
vfio/pci: Convert all MemoryRegion to dynamic alloc and consistent functions
Match common vfio code with setup, exit, and finalize functions for
BAR, quirk, and VGA management. VGA is also changed to dynamic
allocation to match the other MemoryRegions.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
:040000 040000 0acfd49b6ecae780b6f52a34080ecec6b3ec3672 e0cfdadede08f553463c0b23931eda81107f41b8 M hw
then confirm it by reverting that commit
git checkout v2.6.0
git revert 2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62
git mergetool -t kdiff3
"select all from C", save
not sure if this is the right way to do this...but it compiles and works (bug fixed)
git commit -m "revert 2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62 resolve conflicts"
And that 2.6.0 build with that one patch reverted works fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1591628/+subscriptions
next prev parent reply other threads:[~2016-06-15 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 7:27 [Qemu-devel] [Bug 1591628] [NEW] 2.6.0 hangs linux vm using vfio for pci passthrough of graphics card Peter Maloney
2016-06-12 8:25 ` [Qemu-devel] [Bug 1591628] " Peter Maloney
2016-06-12 23:56 ` Alex Williamson
2016-06-13 18:34 ` Peter Maloney
2016-06-13 18:40 ` Peter Maloney
2016-06-13 18:40 ` Peter Maloney
2016-06-13 18:41 ` Peter Maloney
2016-06-15 18:47 ` Peter Maloney
2016-06-15 18:53 ` Peter Maloney
2016-06-15 20:04 ` Alex Williamson [this message]
2016-06-15 22:10 ` Peter Maloney
2016-06-16 6:41 ` Peter Maloney
2016-06-20 2:23 ` Alex Williamson
2016-06-20 17:44 ` Peter Maloney
2016-09-02 21:22 ` T. Huth
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=20160615200425.2555.86123.malone@chaenomeles.canonical.com \
--to=alex.l.williamson@gmail.com \
--cc=1591628@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.