From: Maxim Gordeev <m.gordeev@ntc-vulkan.ru>
To: xen-devel@lists.xen.org
Subject: Re: VGA passthrough is not working
Date: Mon, 16 Jun 2014 14:01:35 +0400 [thread overview]
Message-ID: <539EC07F.1010303@ntc-vulkan.ru> (raw)
In-Reply-To: <539E92FC.5000606@ntc-vulkan.ru>
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?
Regards!
16.06.2014 10:47, Maxim Gordeev пишет:
> OK!
>
> Do you help me?
>
> 11.06.2014 18:16, Konrad Rzeszutek Wilk пишет:
>> On Wed, Jun 11, 2014 at 05:40:04PM +0400, Maxim Gordeev wrote:
>>> <html>
>> Yuck. HTML!? Please please don't do that.
>>
>>> <head>
>>> <meta content="text/html; charset=ISO-8859-1"
>>> http-equiv="Content-Type">
>>> </head>
>>> <body bgcolor="#FFFFFF" text="#000000">
>>> I try build and compile xen 4.4:<br>
>>> ./configure --with-system-qemu=x86_64-softmmu<br>
>>> Use config VM:<br>
>>> device_model_version =
>>> "qemu-xen" <br>
>>> device_model_override = "/usr/local/bin/qemu-system-x86_64"<br>
>>> <br>
>>> It didn't yield result.<br>
>>> <div class="moz-cite-prefix">11.06.2014 15:28, Maxim Gordeev пишет:<br>
>>> </div>
>>> <blockquote cite="mid:53983D5E.3040702@ntc-vulkan.ru" type="cite">
>>> <meta http-equiv="Content-Type" content="text/html;
>>> charset=ISO-8859-1">
>>> I do not apply a patches...<br>
>>> <br>
>>> <div class="moz-cite-prefix">11.06.2014 13:40, Maxim Gordeev
>>> пишет:<br>
>>> </div>
>>> <blockquote cite="mid:53982401.5070007@ntc-vulkan.ru" type="cite">
>>> Hi!<br>
>>> <br>
>>> Thanks for your answer!<br>
>>> <br>
>>> <b>1. Version Xen:</b>
>>> <blockquote type="cite">(XEN) Xen version 4.4.1-pre (gcc (Debian
>>> 4.8.3-2) 4.8.3) debug=n Tue Jun 10 08:25:03 CDT 2014<br>
>>> </blockquote>
>>> <b>2. Kernel:</b><br>
>>> <blockquote type="cite">Linux hv2 3.14-1-amd64 #1 SMP Debian
>>> 3.14.4-1 (2014-05-13) x86_64 GNU/Linux<br>
>>> </blockquote>
>>> <br>
>>> <br>
>>> Variant using :<br>
>>> <br>
>>> <b>A). Config file my VM:</b><br>
>>> <blockquote type="cite">device_model_version =
>>> "qemu-xen-traditional"<br>
>>> device_model_override = "/usr/local/lib/xen/bin/qemu-dm"<br>
>>> </blockquote>
>>> <b>A.1) Trouble in VM(use conf file VM </b><b><i>3</i></b><b>):</b><br>
>>> VM is not starting!<br>
>>> <blockquote type="cite">register_real_device: Real physical
>>> device 03:00.0 registered successfuly!<br>
>>> IRQ type = INTx<br>
>>> pt_pci_write_config: [00:05:0] Warning: Guest attempt to set
>>> address to unused Base Address Register.
>>> [Offset:14h][Length:4]<br>
>>> pt_pci_write_config: Internal error: Invalid write emulation
>>> return value[-1]. I/O emulator exit.<br>
>>> </blockquote>
>>> <br>
>>> OR<br>
>>> <br>
>>> <br>
>>> <b>B) Config my VM</b><b>:</b><br>
>>> <blockquote type="cite">device_model_version = "qemu-xen"<br>
>>> </blockquote>
>>> <b>B.1)</b><br>
>>> My VM is starting! %) But It have a problem...<br>
>>> Please, look at attach file. <br>
>>> <br>
>>> qemu-dm file is have size 5.1Mb. Are you sure attaching file in
>>> here? <br>
>>> <br>
>>> nvidia card into VM: Region 1: Memory at 100000000 (64-bit,
>>> prefetchable) [size=4G]<br>
>>> nvidia card into DOM0: Region 1: Memory at 5800000000 (64-bit,
>>> prefetchable) [size=16G]<br>
>>> <br>
>>> Why? Where 12G was lost?<br>
>> If you included the logs that I asked I could help you a bit to
>> figure that out. You can also stash them on web-server and point us to it.
>> Or compress them and send them here
>>
>>> <br>
>>> <br>
>>> <br>
>>> I try use memory for VM == 1G... there's no difference at all<br>
>>> <br>
>>> <div class="moz-cite-prefix">10.06.2014 16:58, Konrad Rzeszutek
>>> Wilk пишет:<br>
>>> </div>
>>> <blockquote
>>> cite="mid:20140610125855.GA28932@laptop.dumpdata.com"
>>> type="cite">
>>> <pre wrap="">On Tue, Jun 10, 2014 at 01:10:01PM +0400, Maxim Gordeev wrote:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Sorry, Xen don`t map memory BAR1 when I use "qemu-dm" or
>>> "qemu-xen-traditional"...
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">Could you attach your qemu-dm files, the lspci -vvv from dom0 and
>>> from the guest.
>>>
>>> Does it work if you use less memory? Say mem=2G?
>>>
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">10.06.2014 10:56, Maxim Gordeev пишет:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Hi!
>>>
>>> Thanks for your answer!
>>>
>>> I tried starting my VM with device_model_version = "qemu-xen.
>>> VM is working, but I don`t see NVIDIA in list pci devices...
>>>
>>> This is output message of command "xl create:"
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Hi!
>>>
>>> Thanks for your answer!
>>>
>>> I tried starting my VM with device_model_version = "qemu-xen.
>>> VM is working, but I don`t see NVIDIA in list pci devices...
>>>
>>> This is output message of command xl create:
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">dmesg:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">[81234.316270] xen_pciback: vpci: 0000:03:00.0: assign to virtual slot 0
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">It is All.
>>>
>>> Maybe I will try use this parameter in Xen 4.3?
>>>
>>> 09.06.2014 16:48, Gordan Bobic пишет:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Yes, I think so. I have a sneaky suspicion that qemu cannot handle
>>> BARs over a certain size. Have you tried with
>>> device_model_version = "qemu-xen"
>>> instead of qemu-xen-traditional ?
>>>
>>> On 06/09/2014 01:42 PM, Maxim Gordeev wrote:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Do you understand me? :)
>>>
>>> I can give you logs!
>>> 09.06.2014 16:40, Maxim Gordeev пишет:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">no, no.
>>> With 4.3 is bad work! With 4.4 is do not starting.
>>> I see into lspci: BAR1 is not possible assignment. With 4.3 can not
>>> maping BAR1.
>>> Thanks!
>>>
>>> 09.06.2014 16:29, Gordan Bobic пишет:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">On 06/09/2014 01:21 PM, Maxim Gordeev wrote:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">16Gb this is BAR1.
>>> This is example my VM config:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">/builder='hvm'//
>>> //memory = 16000//
>>> //name = "xen-hvm-cheap1"//
>>> //vcpus=8//
>>> //acpi=0//
>>> //disk = [ //
>>> //// '<a moz-do-not-send="true" class="moz-txt-link-freetext" href="file:/opt/VM/cheap1_glinux-1.img,hda,w%27,//">file:/opt/VM/cheap1_glinux-1.img,hda,w',//</a>
>>> // '<a moz-do-not-send="true" class="moz-txt-link-freetext" href="file:/opt/VM/cheap1_glinux-2.img,hdb,w%27//">file:/opt/VM/cheap1_glinux-2.img,hdb,w'//</a>
>>> // ]//
>>> // xen_platform_pci = 1//
>>> //on_poweroff = 'destroy'//
>>> //on_reboot = 'restart'//
>>> //on_crash = 'restart'//
>>> //device_model_version = 'qemu-xen-traditional'//
>>> //boot="c"//
>>> //vnc=1//
>>> //vnclisten="0.0.0.0"//
>>> //vncdisplay=1//
>>> //vncunused=1//
>>> //vncpasswd=''//
>>> //stdvga=0//
>>> //serial='pty'//
>>> //monitor=1//
>>> //gfx_passthru=0//
>>> //pci=['03:00.0' ] /
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">Xen 4.3 start this VM, but Xen 4.4 is not starting VM.
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">So you are saying that this works fine with 4.3 but breaks with 4.4?
>>>
>>> Gordan
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a>
>>> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.xen.org/xen-devel">http://lists.xen.org/xen-devel</a>
>>> </pre>
>>> </blockquote>
>>> </blockquote>
>>> </blockquote>
>>> <pre wrap="">_______________________________________________
>>> Xen-devel mailing list
>>> <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a>
>>> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.xen.org/xen-devel">http://lists.xen.org/xen-devel</a>
>>> </pre>
>>> </blockquote>
>>> </blockquote>
>>> <pre wrap="">_______________________________________________
>>> Xen-devel mailing list
>>> <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a>
>>> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.xen.org/xen-devel">http://lists.xen.org/xen-devel</a>
>>> </pre>
>>> </blockquote>
>>> </blockquote>
>>> <br>
>>> <br>
>>> <fieldset class="mimeAttachmentHeader"></fieldset>
>>> <br>
>>> <pre wrap="">_______________________________________________
>>> Xen-devel mailing list
>>> <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a>
>>> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.xen.org/xen-devel">http://lists.xen.org/xen-devel</a>
>>> </pre>
>>> </blockquote>
>>> <br>
>>> </blockquote>
>>> <br>
>>> </body>
>>> </html>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-06-16 10:01 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 [this message]
2014-06-16 17:17 ` Konrad Rzeszutek Wilk
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=539EC07F.1010303@ntc-vulkan.ru \
--to=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.