public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Schettler <max.schettler@googlemail.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Alex Williamson <alex.williamson@redhat.com>, kvm@vger.kernel.org
Subject: Re: Vga passthrough to KVM Guest issues
Date: Fri, 01 Nov 2013 17:35:38 +0100	[thread overview]
Message-ID: <1383323738.952.5.camel@max-laptop> (raw)
In-Reply-To: <20131101150914.GL17455@8bytes.org>

[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]

Hey Joerg,

Am Freitag, den 01.11.2013, 16:09 +0100 schrieb Joerg Roedel:
> Hey Max,
> 
> On Mon, Oct 28, 2013 at 10:17:19AM -0600, Alex Williamson wrote:
> > On Wed, 2013-10-16 at 21:08 +0200, Max Schettler wrote:
> > > Hi guys,
> > > 
> > > Im trying to set up vga passthrough. I use the latest mainline kernel
> > > (3.12rc5) and patched qemu (1.6.50). When i try to start a VM using this
> > > command:
> > > 
> > > qemu-system-x86_64 -enable-kvm -M q35 -m 1024 -cpu qemu64
> > > -bios /usr/share/qemu/bios.bin -vga none 
> > > -device
> > > ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1
> > > -device vfio-pci,host=06:00.0,bus=root.1,multifunction=on,x-vga=on
> > > -device vfio-pci,host=06:00.1,bus=root.1
> > > 
> > > The screen attached to the passthroughed GPU turns on but does not show
> > > any output.
> > > Also I get some warnings from amd_iommu and my kernel messages are full
> > > of AMD-Vi messages:
> > > "AMD-Vi: Completion-Wait loop timed out" and
> > > "AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=06:00.0
> > > address=0x0000000438544b90"
> > > 
> > > If i dont stop the qemu process this eventually forces me to reboot
> > > since the host gets unusable.
> > > 
> > > I uploaded the whole dmesg output, if its of any help here:
> > > http://pastebin.com/ki13dqEd
> > > 
> > > My hardware is an AMD FX-8350 with an Gigabyte 970A-UD3 and a Gigabyte
> > > 7870OC.
> > > 
> > > Any help is much appreciated, thanks in advance!
> 
> That's interesting, what GPU is it that you are trying to pass through
> to the guest? It seems to be an ATS capable device. Either there is a
> problem in the AMD IOMMU driver with handling ATS or there is a problem
> with the hardware and ATS should not be enabled there. Either way, the
> fix/workaround has to be in the AMD IOMMU driver.
> 
> 
> 	Joerg

I fixed this issue in the meanwhile by switching to another Mainboard,
so I guess it was at least somehow associated with the Hardware.

The first Setup was this one:
AMD FX-8350
Gigabyte 970A-UD3
Gigabyte 7870GHz Edition
Sapphire 6450

I switched to an Asrock 990FX Extreme3.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-11-01 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 19:08 Vga passthrough to KVM Guest issues Max Schettler
2013-10-28 16:17 ` Alex Williamson
2013-11-01 15:09   ` Joerg Roedel
2013-11-01 16:35     ` Max Schettler [this message]
2013-11-01 16:45       ` Joerg Roedel
2013-11-01 16:54         ` Max Schettler

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=1383323738.952.5.camel@max-laptop \
    --to=max.schettler@googlemail.com \
    --cc=alex.williamson@redhat.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox