All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Peter Milesson <miles@atmos.eu>
Cc: AndrewCooper <andrew.cooper3@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-users] Xen 4.7.0 graphics pass through problems (Win10, AMD Radeon)
Date: Wed, 14 Sep 2016 15:17:23 +0100	[thread overview]
Message-ID: <CAFLBxZY0R0iBSy7ijbGTVJgtZAiR_LHUO_OC6tDXhR=n7ZcQ5Q@mail.gmail.com> (raw)
In-Reply-To: <014bee96-61a0-4c45-c24c-f306712136f0@atmos.eu>

On Wed, Sep 14, 2016 at 3:04 PM, Peter Milesson <miles@atmos.eu> wrote:
>
>
> On 2016-09-14 14:50, Jan Beulich wrote:
>>>>>
>>>>> On 14.09.16 at 13:34, <george.dunlap@citrix.com> wrote:
>>>>
>>>>   On 2016-09-09 09:51, Peter Milesson wrote:
>>>
>>> [snip]
>>>>>
>>>>> I've been using Xen for 3 years, starting out with 4.2, and I've been
>>>>> upgrading regularly, and installed 4.7.0 today.
>>>>>
>>>>> I'm using Windows 10, 64-bit with PCI pass through in a VM with
>>>>> PV-drivers, using a AMD Radeon HD6450 card (AMD graphics cards don't
>>>>> seem to
>>>>> need graphics pass through)
>>>>>
>>>>> Previously (up till Xen 4.6.3), the graphics output has displayed some
>>>>> shorter lines, a bit like thin coarse snow, when watching videos. The
>>>>> distortions stayed within the movie, and was tolerable.
>>>>>
>>>>> After upgrade to Xen 4.7.0, the video performance is seriously ugly.
>>>>> Just
>>>>> for example, I open cnn.com and move the mouse pointer up and down over
>>>>> the
>>>>> photos, which creates a bunch of flickering lines over the display. The
>>>>> same
>>>>> with moving content in Youtube for example. Or opening a Cygwin
>>>>> terminal
>>>>> window and scrolling through a file. Terrible.
>>>>>
>>>>> Nothing else has changed, only the Xen version.
>>>
>>> [snip]
>>>
>>> On Fri, Sep 9, 2016 at 10:35 AM, Peter Milesson <miles@atmos.eu> wrote:
>>>>
>>>> Hi again,
>>>>
>>>> I've been playing around a bit more.
>>>>
>>>> It seems one of the problems is that I passed a couple of PCI-devices
>>>> (USB
>>>> controllers) to the VM, beside the graphics card.
>>>>
>>>> When I pass the USB-devices individually in the VM configuration file
>>>> (usbdevice=['tablet','host:1.4','host:1:9','host:x.y']), the display
>>>> problems seem to be more or less gone.
>>>
>>> Jan / Andy,
>>>
>>> Can you think of anything that's changed between 4.6 and 4.7 that
>>> would cause the performance problems he's describing when both a video
>>> card and a usb controller are passed through, but not when only the
>>> video card is passed through?
>>
>> Not really, no. Peter - are there any indications of problems in
>> one or more of the logs (Xen, xl, qemu)? Did you try running a
>> debug build of all Xen components?
>>
>> Jan
>>
> Hi Jan,
>
> No, I did not try a debug build. However, the system seems fairly stable
> now, only the display driver crashing once, or twice a day. That did occur
> with Xen 4.6.3 also, but maybe once a week.

Well crashing twice a day isn't what most people would call "stable".
:-)  In any case, I was trying to debug the issue you had with passing
through both the video card and the usb controller -- that is
obviously an important configuration, but if there's a bug in that
configuration it probably affects a large number of wider
configurations as well.

> Looking at the log files, I
> cannot see anything particular that stands out, except for the domU log.
>
> The domU log file qemu-dm-<Name>.log started to contain the following lines
> after upgrading to 4.7:
>
> [00:06.0] xen_pt_bar_read: Error: Should not read BAR through QEMU.
> @0x0000000000000004
> [00:06.0] xen_pt_bar_write: Error: Should not write BAR through QEMU.
> @0x0000000000000000
>
> There are only a couple of lines with write, the rest with read. I don't
> know what significance it's got, but there are around 350 lines every day.

Yeah, those definitely look important.  This is with just the video
card passed through, or with both passed through?

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-09-14 14:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <02b85238-cacb-a994-2402-d0aa4fc8d7b3@atmos.eu>
     [not found] ` <3d258ed8-4cb2-e6e0-76b7-81f06c835b53@atmos.eu>
2016-09-14 11:34   ` [Xen-users] Xen 4.7.0 graphics pass through problems (Win10, AMD Radeon) George Dunlap
2016-09-14 12:50     ` Jan Beulich
2016-09-14 13:23       ` Andrew Cooper
2016-09-14 13:30         ` George Dunlap
2016-09-14 14:40           ` Peter Milesson
2016-09-14 14:16         ` Peter Milesson
2016-09-14 14:04       ` Peter Milesson
     [not found]       ` <014bee96-61a0-4c45-c24c-f306712136f0@atmos.eu>
2016-09-14 14:17         ` George Dunlap [this message]
2016-09-14 14:48           ` Peter Milesson
2016-09-14 14:49         ` Jan Beulich
2016-09-14 15:29           ` Peter Milesson

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='CAFLBxZY0R0iBSy7ijbGTVJgtZAiR_LHUO_OC6tDXhR=n7ZcQ5Q@mail.gmail.com' \
    --to=george.dunlap@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=miles@atmos.eu \
    --cc=xen-devel@lists.xenproject.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.