All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Maxim Gordeev <m.gordeev@ntc-vulkan.ru>
Cc: xen-devel@lists.xen.org
Subject: Re: VGA passthrough is not working
Date: Mon, 16 Jun 2014 13:17:54 -0400	[thread overview]
Message-ID: <20140616171754.GC26036@laptop.dumpdata.com> (raw)
In-Reply-To: <539EC07F.1010303@ntc-vulkan.ru>

On Mon, Jun 16, 2014 at 02:01:35PM +0400, Maxim Gordeev wrote:
> Hi!
> 
> I find some message into dmesg:
> pci 0000:00:05.0: BAR 1: can't assign mem pref (size 0x100000000)
> [    0.910157] pci 0000:00:05.0: BAR 1: trying firmware assignment [mem
> 0x100000000-0x1ffffffff 64bit pref]
> [    0.910162] pci 0000:00:05.0: BAR 1: assigned [mem
> 0x100000000-0x1ffffffff 64bit pref]
> 
> This issue when I use VM whit the next parametуr: device_model_version
> =  "qemu-xen"
> 
> And lspci -s 00:05.0 -vvv :
> Subsystem: NVIDIA Corporation Device 097e
> Physical Slot: 5
> ...
>  Region 0: Memory at 85000000 (32-bit, non-prefetchable) [size=16M]
>  Region 1: Memory at 100000000 (64-bit, prefetchable) [size=4G]
>  Region 3: Memory at 82000000 (64-bit, prefetchable) [size=32M]
> 
> 
> Do you help me?

Please include (I mentioned this earlier but it probably got lost), your
full 'dmesg' from both the guest _and_ the initial domain (dom0). Also
your 'lspci -vvv' from dom0 _and_ from your guest.

Lastly, also include you /var/log/xen/qemu-* file.

Thank you.

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

  reply	other threads:[~2014-06-16 17:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 11:39 VGA passthrough is not working Maxim Gordeev
2014-06-09 11:51 ` Gordan Bobic
2014-06-09 12:21   ` Maxim Gordeev
2014-06-09 12:29     ` Gordan Bobic
2014-06-09 12:40       ` Maxim Gordeev
2014-06-09 12:42         ` Maxim Gordeev
2014-06-09 12:48           ` Gordan Bobic
2014-06-10  6:56             ` Maxim Gordeev
2014-06-10  9:10               ` Maxim Gordeev
2014-06-10 12:58                 ` Konrad Rzeszutek Wilk
2014-06-11  9:40                   ` Maxim Gordeev
2014-06-11 11:28                     ` Maxim Gordeev
2014-06-11 13:40                       ` Maxim Gordeev
2014-06-11 14:16                         ` Konrad Rzeszutek Wilk
2014-06-16  6:47                           ` Maxim Gordeev
2014-06-16 10:01                             ` Maxim Gordeev
2014-06-16 17:17                               ` Konrad Rzeszutek Wilk [this message]
2014-06-17  8:08                                 ` Maxim Gordeev
2014-06-17 16:35                                   ` Konrad Rzeszutek Wilk
2014-06-18  7:57                                     ` Maxim Gordeev
2014-06-23 13:38                                       ` Maxim Gordeev
2014-06-30 19:57                                         ` Konrad Rzeszutek Wilk

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=20140616171754.GC26036@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=m.gordeev@ntc-vulkan.ru \
    --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.