From: Hans Mueller <mcbeagle@gmx.de>
To: xen-devel@lists.xen.org
Subject: Re: PCI/VGA passthrough on >Xen-4.2 - (XEN) AMD-Vi: IO_PAGE_FAULT:
Date: Fri, 09 Nov 2012 17:25:23 +0100 [thread overview]
Message-ID: <1382625.svAp90pkVF@sheik-lin> (raw)
In-Reply-To: <CAN3GA=T8Ztupou=XU4a6MeMWJN5yJgN=0fmDUp0BvXFRPEfLYw@mail.gmail.com>
On Thursday, 8. November 2012 20:02:51 feral wrote:
> Upgraded from Xen-4.1 to 4.2/4.3/4.3-unstable. Tested against all three.
>
> VGA passthrough previously working with 4.1 is no longer working with >4.2.
>
> Setup - Working:
> Mint13, kernel-3.2.0-32, Xen-4.1 (from Ubuntu-Precise repos), libvirt-bin,
> xend
> Asus Radeon HD 7870 DirectCU.
> Works perfect. Benches on par with bare metal.
>
> Setup - Broken:
> Mint13, kernel-3.2.0-32, Xen-4.2,Xen-4.3,Xen-4.3-unstable (from GIT), xl
> toolstack.
> Asus Radeon HD 7870 DirectCU.
> Some times the guest boots correctly but display is never enabled.
> Sometimes BSOD, doesn't seem to be any rhyme or reason?
>
> No errors in logs. Found the following in 'xl dmesg':
> (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 2, device id = 0x600, fault address =
> 0x1ac800000, flags = 0
I had a similar problem since hg revision 25818:50adc933faaf which changes the
qemu tag.
It looks like the qemu commit
3e66da7266c84638c0e22a09c9d2b07529802576
(qemu-xen-trad: fix msi_translate with PV event delivery)
causes this behavior.
I solved the problem for me by using 'pci_msitranslate=0' in the domU config.
In addition I had to reboot (perhaps poweroff?) the dom0 once the IO_PAGE_FAULT
occured.
Regards
Hans
next prev parent reply other threads:[~2012-11-09 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 4:02 PCI/VGA passthrough on >Xen-4.2 - (XEN) AMD-Vi: IO_PAGE_FAULT: feral
2012-11-09 16:25 ` Hans Mueller [this message]
2012-11-09 16:33 ` Ian Campbell
2012-11-09 17:03 ` Hans Mueller
2012-11-09 17:14 ` Hans Mueller
2012-11-13 11:29 ` Stefano Stabellini
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=1382625.svAp90pkVF@sheik-lin \
--to=mcbeagle@gmx.de \
--cc=xen-devel@lists.xen.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.