Xen devel - Jul 2013 - Intel HD Graphics 4600 Xen VGA Passthrough to Windows 7 Ultimate HVM domU

Hi,

I have just compiled and installed Xen 4.4-unstable changeset 27262 and 
Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU configuration 
file is as attached.

I tried to passthrough the onboard Intel HD Graphics 4600 IGD to Windows 
7 Ultimate HVM domU.

However, there are only 16 colors on the monitor. Please refer to the 
following screenshots.

http://i.imgur.com/AVVPQFs.jpg

http://i.imgur.com/390ORY0.jpg

http://i.imgur.com/ihc0bR0.jpg

http://i.imgur.com/FlNhjum.jpg

http://i.imgur.com/sMrBKCq.jpg

Please advise.

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)



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

Hi,

I have just compiled and installed Xen 4.4-unstable changeset 27262 and 
Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU configuration 
file is as attached.

I tried to passthrough the onboard Intel HD Graphics 4600 IGD to Windows 
7 Ultimate HVM domU.

However, there are only 16 colors on the monitor. Please refer to the 
following screenshots.

http://i.imgur.com/AVVPQFs.jpg

http://i.imgur.com/390ORY0.jpg

http://i.imgur.com/ihc0bR0.jpg

http://i.imgur.com/FlNhjum.jpg

http://i.imgur.com/sMrBKCq.jpg

Please advise.

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)



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

On 20/07/2013 17:55, Singapore Citizen Mr. Teo En Ming (Zhang Enming)
wrote:
> Hi,
>
> I have just compiled and installed Xen 4.4-unstable changeset 27262 
> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU 
> configuration file is as attached.
>
> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to 
> Windows 7 Ultimate HVM domU.
>
> However, there are only 16 colors on the monitor. Please refer to the 
> following screenshots.
>
> http://i.imgur.com/AVVPQFs.jpg
>
> http://i.imgur.com/390ORY0.jpg
>
> http://i.imgur.com/ihc0bR0.jpg
>
> http://i.imgur.com/FlNhjum.jpg
>
> http://i.imgur.com/sMrBKCq.jpg
>
> Please advise.
>
> Thank you very much.
>
Any Intel engineers here who can advise?

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On 20/07/2013 17:55, Singapore Citizen Mr. Teo En Ming (Zhang Enming)
wrote:
> Hi,
>
> I have just compiled and installed Xen 4.4-unstable changeset 27262 
> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU 
> configuration file is as attached.
>
> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to 
> Windows 7 Ultimate HVM domU.
>
> However, there are only 16 colors on the monitor. Please refer to the 
> following screenshots.
>
> http://i.imgur.com/AVVPQFs.jpg
>
> http://i.imgur.com/390ORY0.jpg
>
> http://i.imgur.com/ihc0bR0.jpg
>
> http://i.imgur.com/FlNhjum.jpg
>
> http://i.imgur.com/sMrBKCq.jpg
>
> Please advise.
>
> Thank you very much.
>
Any Intel engineers here who can advise?

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

> -----Original Message-----
> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> [mailto:singapore.mr.teo.en.ming@gmail.com]
> Sent: Saturday, July 20, 2013 6:10 PM
> To: singapore.mr.teo.en.ming@gmail.com
> Cc: xen-users@lists.xen.org; xen-devel@lists.xen.org; Ren, Yongjie; Zhang,
> Xiantao
> Subject: Re: Intel HD Graphics 4600 Xen VGA Passthrough to Windows 7
> Ultimate HVM domU
> 
> On 20/07/2013 17:55, Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> wrote:
> > Hi,
> >
> > I have just compiled and installed Xen 4.4-unstable changeset 27262
> > and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
> > configuration file is as attached.
> >
> > I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
> > Windows 7 Ultimate HVM domU.
> >
> > However, there are only 16 colors on the monitor. Please refer to the
> > following screenshots.
> >
> > http://i.imgur.com/AVVPQFs.jpg
> >
> > http://i.imgur.com/390ORY0.jpg
> >
> > http://i.imgur.com/ihc0bR0.jpg
> >
> > http://i.imgur.com/FlNhjum.jpg
> >
> > http://i.imgur.com/sMrBKCq.jpg
> >
> > Please advise.
> >
> > Thank you very much.
> >
> 
> Any Intel engineers here who can advise?
> 
I''m also doing some testing but seems we didn''t meet a similar
issue with yours.
Which CPU are you using? 
My Haswell desktop CPU (Core i5-4670) doesn''t have the same IGD as
yours.
And, I''ll have some update after I doing more testing.

Best Regards,
     Yongjie (Jay)
> --
> Yours sincerely,
> 
> Singapore Citizen Mr. Teo En Ming (Zhang Enming)

> -----Original Message-----
> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> [mailto:singapore.mr.teo.en.ming@gmail.com]
> Sent: Saturday, July 20, 2013 6:10 PM
> To: singapore.mr.teo.en.ming@gmail.com
> Cc: xen-users@lists.xen.org; xen-devel@lists.xen.org; Ren, Yongjie; Zhang,
> Xiantao
> Subject: Re: Intel HD Graphics 4600 Xen VGA Passthrough to Windows 7
> Ultimate HVM domU
> 
> On 20/07/2013 17:55, Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> wrote:
> > Hi,
> >
> > I have just compiled and installed Xen 4.4-unstable changeset 27262
> > and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
> > configuration file is as attached.
> >
> > I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
> > Windows 7 Ultimate HVM domU.
> >
> > However, there are only 16 colors on the monitor. Please refer to the
> > following screenshots.
> >
> > http://i.imgur.com/AVVPQFs.jpg
> >
> > http://i.imgur.com/390ORY0.jpg
> >
> > http://i.imgur.com/ihc0bR0.jpg
> >
> > http://i.imgur.com/FlNhjum.jpg
> >
> > http://i.imgur.com/sMrBKCq.jpg
> >
> > Please advise.
> >
> > Thank you very much.
> >
> 
> Any Intel engineers here who can advise?
> 
I''m also doing some testing but seems we didn''t meet a similar
issue with yours.
Which CPU are you using? 
My Haswell desktop CPU (Core i5-4670) doesn''t have the same IGD as
yours.
And, I''ll have some update after I doing more testing.

Best Regards,
     Yongjie (Jay)
> --
> Yours sincerely,
> 
> Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On 22/07/2013 22:57, Ren, Yongjie wrote:
>> -----Original Message-----
>> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
>> [mailto:singapore.mr.teo.en.ming@gmail.com]
>> Sent: Saturday, July 20, 2013 6:10 PM
>> To: singapore.mr.teo.en.ming@gmail.com
>> Cc: xen-users@lists.xen.org; xen-devel@lists.xen.org; Ren, Yongjie;
Zhang,
>> Xiantao
>> Subject: Re: Intel HD Graphics 4600 Xen VGA Passthrough to Windows 7
>> Ultimate HVM domU
>>
>> On 20/07/2013 17:55, Singapore Citizen Mr. Teo En Ming (Zhang Enming)
>> wrote:
>>> Hi,
>>>
>>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>>> configuration file is as attached.
>>>
>>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>>> Windows 7 Ultimate HVM domU.
>>>
>>> However, there are only 16 colors on the monitor. Please refer to
the
>>> following screenshots.
>>>
>>> http://i.imgur.com/AVVPQFs.jpg
>>>
>>> http://i.imgur.com/390ORY0.jpg
>>>
>>> http://i.imgur.com/ihc0bR0.jpg
>>>
>>> http://i.imgur.com/FlNhjum.jpg
>>>
>>> http://i.imgur.com/sMrBKCq.jpg
>>>
>>> Please advise.
>>>
>>> Thank you very much.
>>>
>> Any Intel engineers here who can advise?
>>
> I''m also doing some testing but seems we didn''t meet a
similar issue with yours.
> Which CPU are you using?
> My Haswell desktop CPU (Core i5-4670) doesn''t have the same IGD as
yours.
> And, I''ll have some update after I doing more testing.
>
> Best Regards,
>       Yongjie (Jay)
>
>> --
>> Yours sincerely,
>>
>> Singapore Citizen Mr. Teo En Ming (Zhang Enming)
Hi Yongjie,

I am using Intel Core i5-4430 Quad Core 6 MB @ 3.0 GHz.

Can you share how you configure, compile and install Xen and Linux kernel?

Which version of Xen and Linux kernel are you using?

Did you apply any patches? If so, where can I find the patches?

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On 22/07/2013 22:57, Ren, Yongjie wrote:
>> -----Original Message-----
>> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
>> [mailto:singapore.mr.teo.en.ming@gmail.com]
>> Sent: Saturday, July 20, 2013 6:10 PM
>> To: singapore.mr.teo.en.ming@gmail.com
>> Cc: xen-users@lists.xen.org; xen-devel@lists.xen.org; Ren, Yongjie;
Zhang,
>> Xiantao
>> Subject: Re: Intel HD Graphics 4600 Xen VGA Passthrough to Windows 7
>> Ultimate HVM domU
>>
>> On 20/07/2013 17:55, Singapore Citizen Mr. Teo En Ming (Zhang Enming)
>> wrote:
>>> Hi,
>>>
>>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>>> configuration file is as attached.
>>>
>>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>>> Windows 7 Ultimate HVM domU.
>>>
>>> However, there are only 16 colors on the monitor. Please refer to
the
>>> following screenshots.
>>>
>>> http://i.imgur.com/AVVPQFs.jpg
>>>
>>> http://i.imgur.com/390ORY0.jpg
>>>
>>> http://i.imgur.com/ihc0bR0.jpg
>>>
>>> http://i.imgur.com/FlNhjum.jpg
>>>
>>> http://i.imgur.com/sMrBKCq.jpg
>>>
>>> Please advise.
>>>
>>> Thank you very much.
>>>
>> Any Intel engineers here who can advise?
>>
> I''m also doing some testing but seems we didn''t meet a
similar issue with yours.
> Which CPU are you using?
> My Haswell desktop CPU (Core i5-4670) doesn''t have the same IGD as
yours.
> And, I''ll have some update after I doing more testing.
>
> Best Regards,
>       Yongjie (Jay)
>
>> --
>> Yours sincerely,
>>
>> Singapore Citizen Mr. Teo En Ming (Zhang Enming)
Hi Yongjie,

I am using Intel Core i5-4430 Quad Core 6 MB @ 3.0 GHz.

Can you share how you configure, compile and install Xen and Linux kernel?

Which version of Xen and Linux kernel are you using?

Did you apply any patches? If so, where can I find the patches?

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie
wrote:
> > 
> > Any Intel engineers here who can advise?
> > 
> I''m also doing some testing but seems we didn''t meet a
similar issue with yours.
> Which CPU are you using? 
> My Haswell desktop CPU (Core i5-4670) doesn''t have the same IGD as
yours.
> And, I''ll have some update after I doing more testing.
> 
> Best Regards,
>      Yongjie (Jay)
> 
Hello Yongjie,

Can you please describe the following info about your GPU passthru setup:

- Xen hypervisor version/changeset
- Any patches to Xen? 
- Cmdline options to Xen
- dom0 linux kernel version
- Cmdline options to dom0 linux kernel
- HVM guest OS/version
- IGD driver version in the HVM guest
- dom0 configuration and settings; I assume you''re using xen-pciback?
Did you blacklist igd driver in dom0 kernel? etc.

I think that''d be helpful for others to get a similar baseline
configuration.

Thanks,

-- Pasi

On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie
wrote:
> > 
> > Any Intel engineers here who can advise?
> > 
> I''m also doing some testing but seems we didn''t meet a
similar issue with yours.
> Which CPU are you using? 
> My Haswell desktop CPU (Core i5-4670) doesn''t have the same IGD as
yours.
> And, I''ll have some update after I doing more testing.
> 
> Best Regards,
>      Yongjie (Jay)
> 
Hello Yongjie,

Can you please describe the following info about your GPU passthru setup:

- Xen hypervisor version/changeset
- Any patches to Xen? 
- Cmdline options to Xen
- dom0 linux kernel version
- Cmdline options to dom0 linux kernel
- HVM guest OS/version
- IGD driver version in the HVM guest
- dom0 configuration and settings; I assume you''re using xen-pciback?
Did you blacklist igd driver in dom0 kernel? etc.

I think that''d be helpful for others to get a similar baseline
configuration.

Thanks,

-- Pasi

On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo En Ming
(Zhang Enming) wrote:
> Hi,
> 
> I have just compiled and installed Xen 4.4-unstable changeset 27262
> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
> configuration file is as attached.
> 
> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
> Windows 7 Ultimate HVM domU.
> 
<snip>
> device_model_version="qemu-xen-traditional"
> name="Windows7"
> builder="hvm"
> vcpus=4
> memory=2048
>
There was another report that >= 2GB of RAM with GPU passthru
doesn''t work,
so please try with 1GB of RAM for the HVM guest. 

Also I think there is another PCI passthru related issue in Xen 4.4 at the
moment,
so you probably should try using Xen 4.3.0 or wait for a couple of weeks for the
4.4 issue to get sorted out.

-- Pasi

On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo En Ming
(Zhang Enming) wrote:
> Hi,
> 
> I have just compiled and installed Xen 4.4-unstable changeset 27262
> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
> configuration file is as attached.
> 
> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
> Windows 7 Ultimate HVM domU.
> 
<snip>
> device_model_version="qemu-xen-traditional"
> name="Windows7"
> builder="hvm"
> vcpus=4
> memory=2048
>
There was another report that >= 2GB of RAM with GPU passthru
doesn''t work,
so please try with 1GB of RAM for the HVM guest. 

Also I think there is another PCI passthru related issue in Xen 4.4 at the
moment,
so you probably should try using Xen 4.3.0 or wait for a couple of weeks for the
4.4 issue to get sorted out.

-- Pasi

On 23/07/2013 20:03, Pasi Kärkkäinen wrote:
> On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie wrote:
>>> Any Intel engineers here who can advise?
>>>
>> I''m also doing some testing but seems we didn''t meet
a similar issue with yours.
>> Which CPU are you using?
>> My Haswell desktop CPU (Core i5-4670) doesn''t have the same
IGD as yours.
>> And, I''ll have some update after I doing more testing.
>>
>> Best Regards,
>>       Yongjie (Jay)
>>
> Hello Yongjie,
>
> Can you please describe the following info about your GPU passthru setup:
>
> - Xen hypervisor version/changeset
> - Any patches to Xen?
> - Cmdline options to Xen
> - dom0 linux kernel version
> - Cmdline options to dom0 linux kernel
> - HVM guest OS/version
> - IGD driver version in the HVM guest
> - dom0 configuration and settings; I assume you''re using
xen-pciback? Did you blacklist igd driver in dom0 kernel? etc.
>
> I think that''d be helpful for others to get a similar baseline
configuration.
>
> Thanks,
>
> -- Pasi
>
>
Dear Yongjie,

Could you share with us your hardware and software configuration settings?

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On 23/07/2013 20:03, Pasi Kärkkäinen wrote:
> On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie wrote:
>>> Any Intel engineers here who can advise?
>>>
>> I''m also doing some testing but seems we didn''t meet
a similar issue with yours.
>> Which CPU are you using?
>> My Haswell desktop CPU (Core i5-4670) doesn''t have the same
IGD as yours.
>> And, I''ll have some update after I doing more testing.
>>
>> Best Regards,
>>       Yongjie (Jay)
>>
> Hello Yongjie,
>
> Can you please describe the following info about your GPU passthru setup:
>
> - Xen hypervisor version/changeset
> - Any patches to Xen?
> - Cmdline options to Xen
> - dom0 linux kernel version
> - Cmdline options to dom0 linux kernel
> - HVM guest OS/version
> - IGD driver version in the HVM guest
> - dom0 configuration and settings; I assume you''re using
xen-pciback? Did you blacklist igd driver in dom0 kernel? etc.
>
> I think that''d be helpful for others to get a similar baseline
configuration.
>
> Thanks,
>
> -- Pasi
>
>
Dear Yongjie,

Could you share with us your hardware and software configuration settings?

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On 24/07/2013 16:59, Pasi Kärkkäinen wrote:
> On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo En Ming
(Zhang Enming) wrote:
>> Hi,
>>
>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>> configuration file is as attached.
>>
>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>> Windows 7 Ultimate HVM domU.
>>
> <snip>
>
>> device_model_version="qemu-xen-traditional"
>> name="Windows7"
>> builder="hvm"
>> vcpus=4
>> memory=2048
>>
> There was another report that >= 2GB of RAM with GPU passthru
doesn''t work,
> so please try with 1GB of RAM for the HVM guest.
>
> Also I think there is another PCI passthru related issue in Xen 4.4 at the
moment,
> so you probably should try using Xen 4.3.0 or wait for a couple of weeks
for the 4.4 issue to get sorted out.
>
> -- Pasi
>
>
Dear Pasi,

I am still using Xen 4.4-unstable. I have tried memory=1024 for both 
Windows 8 and Windows 8.1 HVM domU but both of them couldn''t start. I 
have also tried memory=1024 for Windows 7 HVM, and although it could 
start, I still get error code 43 and 16 colors on the monitor only.

I have tried Xen 4.3.0 as well but with Windows 7 HVM domU, I still get 
error code 43 and 16 colors on the monitor.

Please advise.

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On 24/07/2013 16:59, Pasi Kärkkäinen wrote:
> On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo En Ming
(Zhang Enming) wrote:
>> Hi,
>>
>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>> configuration file is as attached.
>>
>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>> Windows 7 Ultimate HVM domU.
>>
> <snip>
>
>> device_model_version="qemu-xen-traditional"
>> name="Windows7"
>> builder="hvm"
>> vcpus=4
>> memory=2048
>>
> There was another report that >= 2GB of RAM with GPU passthru
doesn''t work,
> so please try with 1GB of RAM for the HVM guest.
>
> Also I think there is another PCI passthru related issue in Xen 4.4 at the
moment,
> so you probably should try using Xen 4.3.0 or wait for a couple of weeks
for the 4.4 issue to get sorted out.
>
> -- Pasi
>
>
Dear Pasi,

I am still using Xen 4.4-unstable. I have tried memory=1024 for both 
Windows 8 and Windows 8.1 HVM domU but both of them couldn''t start. I 
have also tried memory=1024 for Windows 7 HVM, and although it could 
start, I still get error code 43 and 16 colors on the monitor only.

I have tried Xen 4.3.0 as well but with Windows 7 HVM domU, I still get 
error code 43 and 16 colors on the monitor.

Please advise.

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

> -----Original Message-----
> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> [mailto:singapore.mr.teo.en.ming@gmail.com]
> Sent: Wednesday, July 24, 2013 5:04 PM
> To: Pasi Kärkkäinen
> Cc: Ren, Yongjie; xen-users@lists.xen.org; Zhang, Xiantao;
> xen-devel@lists.xen.org; Teo En Ming (Zhang Enming)
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
> On 23/07/2013 20:03, Pasi Kärkkäinen wrote:
> > On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie wrote:
> >>> Any Intel engineers here who can advise?
> >>>
> >> I''m also doing some testing but seems we didn''t
meet a similar issue
> with yours.
> >> Which CPU are you using?
> >> My Haswell desktop CPU (Core i5-4670) doesn''t have the
same IGD as
> yours.
> >> And, I''ll have some update after I doing more testing.
> >>
> >> Best Regards,
> >>       Yongjie (Jay)
> >>
> > Hello Yongjie,
> >
> > Can you please describe the following info about your GPU passthru
> setup:
> >
> > - Xen hypervisor version/changeset
> > - Any patches to Xen?
> > - Cmdline options to Xen
> > - dom0 linux kernel version
> > - Cmdline options to dom0 linux kernel
> > - HVM guest OS/version
> > - IGD driver version in the HVM guest
> > - dom0 configuration and settings; I assume you''re using
xen-pciback?
> Did you blacklist igd driver in dom0 kernel? etc.
> >
> > I think that''d be helpful for others to get a similar
baseline configuration.
> >
> > Thanks,
> >
> > -- Pasi
> >
> >
> 
> Dear Yongjie,
> 
> Could you share with us your hardware and software configuration
> settings?
> 
Sure. My IGD is also Intel HD Graphics 4600. :-)

1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months ago)
  traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
  Dom0 kernel: Linux 3.8.1
N.B. I didn''t use the latest traditional qemu because of the following
bug:
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865

2. no offline patch. (just use the code in the tree I mentioned above.)

3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
unrestricted_guest=1 msi=1
  dom0 kernel options: ro root=/dev/sda1

4. HVM guest: Windows 7 Enterprise

5. IGD driver version in HVM: 9.18.10.3165
  got to: https://downloadcenter.intel.com/
  then, search "4th Generation Intel Core Processors with intel hd graphics
4600" to download the driver.

6. use ''xl pci-assignable-add $BDF'' to add the IGD as
assignable.
  (it also use ''xen.pciback'' driver.)

7. dom0 kernel config is attached as file ''config-3.8.1''.

8. HVM guest config file:
builder= "hvm"
name= "vga-passthrough"
memory =1024
vcpus=4
device_model_override= ''/usr/lib/xen/bin/qemu-dm''
device_model_version= ''qemu-xen-traditional''
disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
vnc=1
serial=''pty''
usb = 1
usbdevice = ''tablet''
gfx_passthru=1
pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are mouse and keyboard.

9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to the Windows
guest. And the IGD can work fine.
  See some attached pictures for more info.


Best Regards,
     Yongjie (Jay)




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

> -----Original Message-----
> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> [mailto:singapore.mr.teo.en.ming@gmail.com]
> Sent: Wednesday, July 24, 2013 5:04 PM
> To: Pasi Kärkkäinen
> Cc: Ren, Yongjie; xen-users@lists.xen.org; Zhang, Xiantao;
> xen-devel@lists.xen.org; Teo En Ming (Zhang Enming)
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
> On 23/07/2013 20:03, Pasi Kärkkäinen wrote:
> > On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie wrote:
> >>> Any Intel engineers here who can advise?
> >>>
> >> I''m also doing some testing but seems we didn''t
meet a similar issue
> with yours.
> >> Which CPU are you using?
> >> My Haswell desktop CPU (Core i5-4670) doesn''t have the
same IGD as
> yours.
> >> And, I''ll have some update after I doing more testing.
> >>
> >> Best Regards,
> >>       Yongjie (Jay)
> >>
> > Hello Yongjie,
> >
> > Can you please describe the following info about your GPU passthru
> setup:
> >
> > - Xen hypervisor version/changeset
> > - Any patches to Xen?
> > - Cmdline options to Xen
> > - dom0 linux kernel version
> > - Cmdline options to dom0 linux kernel
> > - HVM guest OS/version
> > - IGD driver version in the HVM guest
> > - dom0 configuration and settings; I assume you''re using
xen-pciback?
> Did you blacklist igd driver in dom0 kernel? etc.
> >
> > I think that''d be helpful for others to get a similar
baseline configuration.
> >
> > Thanks,
> >
> > -- Pasi
> >
> >
> 
> Dear Yongjie,
> 
> Could you share with us your hardware and software configuration
> settings?
> 
Sure. My IGD is also Intel HD Graphics 4600. :-)

1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months ago)
  traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
  Dom0 kernel: Linux 3.8.1
N.B. I didn''t use the latest traditional qemu because of the following
bug:
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865

2. no offline patch. (just use the code in the tree I mentioned above.)

3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
unrestricted_guest=1 msi=1
  dom0 kernel options: ro root=/dev/sda1

4. HVM guest: Windows 7 Enterprise

5. IGD driver version in HVM: 9.18.10.3165
  got to: https://downloadcenter.intel.com/
  then, search "4th Generation Intel Core Processors with intel hd graphics
4600" to download the driver.

6. use ''xl pci-assignable-add $BDF'' to add the IGD as
assignable.
  (it also use ''xen.pciback'' driver.)

7. dom0 kernel config is attached as file ''config-3.8.1''.

8. HVM guest config file:
builder= "hvm"
name= "vga-passthrough"
memory =1024
vcpus=4
device_model_override= ''/usr/lib/xen/bin/qemu-dm''
device_model_version= ''qemu-xen-traditional''
disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
vnc=1
serial=''pty''
usb = 1
usbdevice = ''tablet''
gfx_passthru=1
pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are mouse and keyboard.

9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to the Windows
guest. And the IGD can work fine.
  See some attached pictures for more info.


Best Regards,
     Yongjie (Jay)




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

On 24/07/2013 18:33, Ren, Yongjie wrote:
>> -----Original Message-----
>> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
>> [mailto:singapore.mr.teo.en.ming@gmail.com]
>> Sent: Wednesday, July 24, 2013 5:04 PM
>> To: Pasi Kärkkäinen
>> Cc: Ren, Yongjie; xen-users@lists.xen.org; Zhang, Xiantao;
>> xen-devel@lists.xen.org; Teo En Ming (Zhang Enming)
>> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
>> Windows 7 Ultimate HVM domU
>>
>> On 23/07/2013 20:03, Pasi Kärkkäinen wrote:
>>> On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie wrote:
>>>>> Any Intel engineers here who can advise?
>>>>>
>>>> I''m also doing some testing but seems we
didn''t meet a similar issue
>> with yours.
>>>> Which CPU are you using?
>>>> My Haswell desktop CPU (Core i5-4670) doesn''t have the
same IGD as
>> yours.
>>>> And, I''ll have some update after I doing more testing.
>>>>
>>>> Best Regards,
>>>>        Yongjie (Jay)
>>>>
>>> Hello Yongjie,
>>>
>>> Can you please describe the following info about your GPU passthru
>> setup:
>>> - Xen hypervisor version/changeset
>>> - Any patches to Xen?
>>> - Cmdline options to Xen
>>> - dom0 linux kernel version
>>> - Cmdline options to dom0 linux kernel
>>> - HVM guest OS/version
>>> - IGD driver version in the HVM guest
>>> - dom0 configuration and settings; I assume you''re using
xen-pciback?
>> Did you blacklist igd driver in dom0 kernel? etc.
>>> I think that''d be helpful for others to get a similar
baseline configuration.
>>>
>>> Thanks,
>>>
>>> -- Pasi
>>>
>>>
>> Dear Yongjie,
>>
>> Could you share with us your hardware and software configuration
>> settings?
>>
> Sure. My IGD is also Intel HD Graphics 4600. :-)
>
> 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months ago)
>    traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
>    Dom0 kernel: Linux 3.8.1
> N.B. I didn''t use the latest traditional qemu because of the
following bug:
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>
> 2. no offline patch. (just use the code in the tree I mentioned above.)
>
> 3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
unrestricted_guest=1 msi=1
>    dom0 kernel options: ro root=/dev/sda1
>
> 4. HVM guest: Windows 7 Enterprise
>
> 5. IGD driver version in HVM: 9.18.10.3165
>    got to: https://downloadcenter.intel.com/
>    then, search "4th Generation Intel Core Processors with intel hd
graphics 4600" to download the driver.
>
> 6. use ''xl pci-assignable-add $BDF'' to add the IGD as
assignable.
>    (it also use ''xen.pciback'' driver.)
>
> 7. dom0 kernel config is attached as file ''config-3.8.1''.
>
> 8. HVM guest config file:
> builder= "hvm"
> name= "vga-passthrough"
> memory =1024
> vcpus=4
> device_model_override= ''/usr/lib/xen/bin/qemu-dm''
> device_model_version= ''qemu-xen-traditional''
> disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
> vnc=1
> serial=''pty''
> usb = 1
> usbdevice = ''tablet''
> gfx_passthru=1
> pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are mouse and keyboard.
>
> 9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to the
Windows guest. And the IGD can work fine.
>    See some attached pictures for more info.
>
>
> Best Regards,
>       Yongjie (Jay)
Hi,

I was trying to compile Xen 4.3-unstable changeset 26666 when I 
encountered the following error.

/usr/bin/ld: vl.o: undefined reference to symbol 
''timer_settime@@GLIBC_2.3.3''
/usr/bin/ld: note: ''timer_settime@@GLIBC_2.3.3'' is defined in
DSO
/lib/x86_64-linux-gnu/librt.so.1 so try adding it to the linker command line
/lib/x86_64-linux-gnu/librt.so.1: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[5]: *** [qemu-dm] Error 1
make[5]: Leaving directory 
`/home/teo-en-ming/xen-unstable.hg-cs26666/tools/qemu-xen-traditional-dir-remote/i386-dm''
make[4]: *** [subdir-i386-dm] Error 2
make[4]: Leaving directory 
`/home/teo-en-ming/xen-unstable.hg-cs26666/tools/qemu-xen-traditional-dir-remote''
make[3]: *** [subdir-install-qemu-xen-traditional-dir] Error 2
make[3]: Leaving directory
`/home/teo-en-ming/xen-unstable.hg-cs26666/tools''
make[2]: *** [subdirs-install] Error 2
make[2]: Leaving directory
`/home/teo-en-ming/xen-unstable.hg-cs26666/tools''
make[1]: *** [install-tools] Error 2
make[1]: Leaving directory `/home/teo-en-ming/xen-unstable.hg-cs26666''
make: *** [world] Error 2

Related information: http://www.gossamer-threads.com/lists/xen/devel/283347

How can I fix this issue?

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

On Wed, Jul 24, 2013 at 10:33:38AM +0000, Ren, Yongjie
wrote:
> > 
> > Dear Yongjie,
> > 
> > Could you share with us your hardware and software configuration
> > settings?
> > 
> Sure. My IGD is also Intel HD Graphics 4600. :-)
>
> 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months ago)
>   traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
>   Dom0 kernel: Linux 3.8.1
> N.B. I didn''t use the latest traditional qemu because of the
following bug:
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> 
Hmm.. isn''t that bug affecting qemu-traditional in general, not PCI/GPU
passthru specifically?
Or is it *only* PCI/GPU passthru that it breaks for you? 

> 2. no offline patch. (just use the code in the tree I mentioned above.)
>
Ok, so this is a pre-4.3 version. 

 
> 3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
unrestricted_guest=1 msi=1
>   dom0 kernel options: ro root=/dev/sda1
> 
> 4. HVM guest: Windows 7 Enterprise
> 
32bit or 64bit Win7? SP1 I assume? 

> 5. IGD driver version in HVM: 9.18.10.3165
>   got to: https://downloadcenter.intel.com/
>   then, search "4th Generation Intel Core Processors with intel hd
graphics 4600" to download the driver.
> 
> 6. use ''xl pci-assignable-add $BDF'' to add the IGD as
assignable.
>   (it also use ''xen.pciback'' driver.)
> 
Is IGD the primary graphics adapter on the machine, so does BIOS initialize the
IGD when you power-on the machine?
Or do you have some other graphics adapter that you use in dom0 ? 

> 7. dom0 kernel config is attached as file ''config-3.8.1''.
> 
> 8. HVM guest config file:
> builder= "hvm"
> name= "vga-passthrough"
> memory =1024
> vcpus=4
> device_model_override= ''/usr/lib/xen/bin/qemu-dm''
> device_model_version= ''qemu-xen-traditional''
> disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
> vnc=1
> serial=''pty''
> usb = 1
> usbdevice = ''tablet''
> gfx_passthru=1
> pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are mouse and keyboard.
> 
> 9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to the
Windows guest. And the IGD can work fine.
>   See some attached pictures for more info.
> 
Thanks a lot!

-- Pasi

On Wed, Jul 24, 2013 at 10:33:38AM +0000, Ren, Yongjie
wrote:
> > 
> > Dear Yongjie,
> > 
> > Could you share with us your hardware and software configuration
> > settings?
> > 
> Sure. My IGD is also Intel HD Graphics 4600. :-)
>
> 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months ago)
>   traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
>   Dom0 kernel: Linux 3.8.1
> N.B. I didn''t use the latest traditional qemu because of the
following bug:
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> 
Hmm.. isn''t that bug affecting qemu-traditional in general, not PCI/GPU
passthru specifically?
Or is it *only* PCI/GPU passthru that it breaks for you? 

> 2. no offline patch. (just use the code in the tree I mentioned above.)
>
Ok, so this is a pre-4.3 version. 

 
> 3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
unrestricted_guest=1 msi=1
>   dom0 kernel options: ro root=/dev/sda1
> 
> 4. HVM guest: Windows 7 Enterprise
> 
32bit or 64bit Win7? SP1 I assume? 

> 5. IGD driver version in HVM: 9.18.10.3165
>   got to: https://downloadcenter.intel.com/
>   then, search "4th Generation Intel Core Processors with intel hd
graphics 4600" to download the driver.
> 
> 6. use ''xl pci-assignable-add $BDF'' to add the IGD as
assignable.
>   (it also use ''xen.pciback'' driver.)
> 
Is IGD the primary graphics adapter on the machine, so does BIOS initialize the
IGD when you power-on the machine?
Or do you have some other graphics adapter that you use in dom0 ? 

> 7. dom0 kernel config is attached as file ''config-3.8.1''.
> 
> 8. HVM guest config file:
> builder= "hvm"
> name= "vga-passthrough"
> memory =1024
> vcpus=4
> device_model_override= ''/usr/lib/xen/bin/qemu-dm''
> device_model_version= ''qemu-xen-traditional''
> disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
> vnc=1
> serial=''pty''
> usb = 1
> usbdevice = ''tablet''
> gfx_passthru=1
> pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are mouse and keyboard.
> 
> 9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to the
Windows guest. And the IGD can work fine.
>   See some attached pictures for more info.
> 
Thanks a lot!

-- Pasi

On Wed, Jul 24, 2013 at 4:59 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
> On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo En Ming
(Zhang Enming) wrote:
>> Hi,
>>
>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>> configuration file is as attached.
>>
>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>> Windows 7 Ultimate HVM domU.
>>
>
> <snip>
>
>> device_model_version="qemu-xen-traditional"
>> name="Windows7"
>> builder="hvm"
>> vcpus=4
>> memory=2048
>>
>
> There was another report that >= 2GB of RAM with GPU passthru
doesn''t work,
> so please try with 1GB of RAM for the HVM guest.
>
> Also I think there is another PCI passthru related issue in Xen 4.4 at the
moment,
> so you probably should try using Xen 4.3.0 or wait for a couple of weeks
for the 4.4 issue to get sorted out.
>
In my case, 2048MB works for IGD4000.
What I''m aware is that guest memory > 3GB is known to not working.
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

On Wed, Jul 24, 2013 at 4:59 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
> On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo En Ming
(Zhang Enming) wrote:
>> Hi,
>>
>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>> configuration file is as attached.
>>
>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>> Windows 7 Ultimate HVM domU.
>>
>
> <snip>
>
>> device_model_version="qemu-xen-traditional"
>> name="Windows7"
>> builder="hvm"
>> vcpus=4
>> memory=2048
>>
>
> There was another report that >= 2GB of RAM with GPU passthru
doesn''t work,
> so please try with 1GB of RAM for the HVM guest.
>
> Also I think there is another PCI passthru related issue in Xen 4.4 at the
moment,
> so you probably should try using Xen 4.3.0 or wait for a couple of weeks
for the 4.4 issue to get sorted out.
>
In my case, 2048MB works for IGD4000.
What I''m aware is that guest memory > 3GB is known to not working.
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

On Wed, 24 Jul 2013 14:57:02 +0300, Pasi Kärkkäinen <pasik@iki.fi> 
 wrote:
> On Wed, Jul 24, 2013 at 10:33:38AM +0000, Ren, Yongjie wrote:
>> >
>> > Dear Yongjie,
>> >
>> > Could you share with us your hardware and software configuration
>> > settings?
>> >
>> Sure. My IGD is also Intel HD Graphics 4600. :-)
>>
>> 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months 
>> ago)
>>   traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
>>   Dom0 kernel: Linux 3.8.1
>> N.B. I didn't use the latest traditional qemu because of the 
>> following bug:
>> 
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>>
>
> Hmm.. isn't that bug affecting qemu-traditional in general, not
> PCI/GPU passthru specifically?
> Or is it *only* PCI/GPU passthru that it breaks for you?
 PCI and GPU passthru work fine for me on 4.2.2 and 4.3.0
 using qemu-dm (traditional), but only as long as I don't
 assign > 2GB of RAM to a domU. I'm sure I saw patches
 that were expected to address this that were also
 supposed to be in 4.3.0, so either the patches didn't
 make it into 4.3.0 for some reason, or the bug I am
 hitting is a different bug with similar symptoms.

 When I get around to it I'm going to set up a
 Linux domU with GPU passthrough and > 2GB of RAM
 so I can easily compare the memory maps and where
 the GPU's BARs are mapped and see if there is an
 obvious overlap where the memory stomp happens.

 Gordan

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

On Wed, 24 Jul 2013 14:57:02 +0300, Pasi Kärkkäinen <pasik@iki.fi> 
 wrote:
> On Wed, Jul 24, 2013 at 10:33:38AM +0000, Ren, Yongjie wrote:
>> >
>> > Dear Yongjie,
>> >
>> > Could you share with us your hardware and software configuration
>> > settings?
>> >
>> Sure. My IGD is also Intel HD Graphics 4600. :-)
>>
>> 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months 
>> ago)
>>   traditional qemu commit: 5ae58eaa967495fce99b727422054c58750d252b
>>   Dom0 kernel: Linux 3.8.1
>> N.B. I didn't use the latest traditional qemu because of the 
>> following bug:
>> 
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>>
>
> Hmm.. isn't that bug affecting qemu-traditional in general, not
> PCI/GPU passthru specifically?
> Or is it *only* PCI/GPU passthru that it breaks for you?
 PCI and GPU passthru work fine for me on 4.2.2 and 4.3.0
 using qemu-dm (traditional), but only as long as I don't
 assign > 2GB of RAM to a domU. I'm sure I saw patches
 that were expected to address this that were also
 supposed to be in 4.3.0, so either the patches didn't
 make it into 4.3.0 for some reason, or the bug I am
 hitting is a different bug with similar symptoms.

 When I get around to it I'm going to set up a
 Linux domU with GPU passthrough and > 2GB of RAM
 so I can easily compare the memory maps and where
 the GPU's BARs are mapped and see if there is an
 obvious overlap where the memory stomp happens.

 Gordan

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

On Wed, 24 Jul 2013 20:17:13 +0800, "G.R." 
 <firemeteor@users.sourceforge.net> wrote:
> On Wed, Jul 24, 2013 at 4:59 PM, Pasi Kärkkäinen <pasik@iki.fi> 
> wrote:
>> On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo 
>> En Ming (Zhang Enming) wrote:
>>> Hi,
>>>
>>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>>> configuration file is as attached.
>>>
>>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>>> Windows 7 Ultimate HVM domU.
>>>
>>
>> <snip>
>>
>>> device_model_version="qemu-xen-traditional"
>>> name="Windows7"
>>> builder="hvm"
>>> vcpus=4
>>> memory=2048
>>>
>>
>> There was another report that >= 2GB of RAM with GPU passthru 
>> doesn't work,
>> so please try with 1GB of RAM for the HVM guest.
>>
>> Also I think there is another PCI passthru related issue in Xen 4.4 
>> at the moment,
>> so you probably should try using Xen 4.3.0 or wait for a couple of 
>> weeks for the 4.4 issue to get sorted out.
>>
>
> In my case, 2048MB works for IGD4000.
> What I'm aware is that guest memory > 3GB is known to not working.
 Which was supposed-to-be-but-isn't fixed in 4.3.0, as far
 as my testing shows. Except I see the problem with > 2GB,
 rather than > 3GB, so it may be the same bug or it could
 be a different bug with similar symptoms.

 Gordan

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

On Wed, 24 Jul 2013 20:17:13 +0800, "G.R." 
 <firemeteor@users.sourceforge.net> wrote:
> On Wed, Jul 24, 2013 at 4:59 PM, Pasi Kärkkäinen <pasik@iki.fi> 
> wrote:
>> On Sat, Jul 20, 2013 at 05:55:00PM +0800, Singapore Citizen Mr. Teo 
>> En Ming (Zhang Enming) wrote:
>>> Hi,
>>>
>>> I have just compiled and installed Xen 4.4-unstable changeset 27262
>>> and Linux kernel 3.11.0-rc1. My Windows 7 Ultimate HVM domU
>>> configuration file is as attached.
>>>
>>> I tried to passthrough the onboard Intel HD Graphics 4600 IGD to
>>> Windows 7 Ultimate HVM domU.
>>>
>>
>> <snip>
>>
>>> device_model_version="qemu-xen-traditional"
>>> name="Windows7"
>>> builder="hvm"
>>> vcpus=4
>>> memory=2048
>>>
>>
>> There was another report that >= 2GB of RAM with GPU passthru 
>> doesn't work,
>> so please try with 1GB of RAM for the HVM guest.
>>
>> Also I think there is another PCI passthru related issue in Xen 4.4 
>> at the moment,
>> so you probably should try using Xen 4.3.0 or wait for a couple of 
>> weeks for the 4.4 issue to get sorted out.
>>
>
> In my case, 2048MB works for IGD4000.
> What I'm aware is that guest memory > 3GB is known to not working.
 Which was supposed-to-be-but-isn't fixed in 4.3.0, as far
 as my testing shows. Except I see the problem with > 2GB,
 rather than > 3GB, so it may be the same bug or it could
 be a different bug with similar symptoms.

 Gordan

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

> -----Original Message-----
> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> [mailto:singapore.mr.teo.en.ming@gmail.com]
> Sent: Wednesday, July 24, 2013 7:33 PM
> To: Ren, Yongjie
> Cc: Pasi K?rkk?inen; Zhang, Xiantao; xen-devel@lists.xen.org; Teo En Ming
> (Zhang Enming); Ian Campbell
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
> On 24/07/2013 18:33, Ren, Yongjie wrote:
> >> -----Original Message-----
> >> From: Singapore Citizen Mr. Teo En Ming (Zhang Enming)
> >> [mailto:singapore.mr.teo.en.ming@gmail.com]
> >> Sent: Wednesday, July 24, 2013 5:04 PM
> >> To: Pasi Kärkkäinen
> >> Cc: Ren, Yongjie; xen-users@lists.xen.org; Zhang, Xiantao;
> >> xen-devel@lists.xen.org; Teo En Ming (Zhang Enming)
> >> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA
Passthrough
> to
> >> Windows 7 Ultimate HVM domU
> >>
> >> On 23/07/2013 20:03, Pasi Kärkkäinen wrote:
> >>> On Mon, Jul 22, 2013 at 02:57:08PM +0000, Ren, Yongjie wrote:
> >>>>> Any Intel engineers here who can advise?
> >>>>>
> >>>> I''m also doing some testing but seems we
didn''t meet a similar issue
> >> with yours.
> >>>> Which CPU are you using?
> >>>> My Haswell desktop CPU (Core i5-4670) doesn''t
have the same IGD
> as
> >> yours.
> >>>> And, I''ll have some update after I doing more
testing.
> >>>>
> >>>> Best Regards,
> >>>>        Yongjie (Jay)
> >>>>
> >>> Hello Yongjie,
> >>>
> >>> Can you please describe the following info about your GPU
passthru
> >> setup:
> >>> - Xen hypervisor version/changeset
> >>> - Any patches to Xen?
> >>> - Cmdline options to Xen
> >>> - dom0 linux kernel version
> >>> - Cmdline options to dom0 linux kernel
> >>> - HVM guest OS/version
> >>> - IGD driver version in the HVM guest
> >>> - dom0 configuration and settings; I assume you''re
using xen-pciback?
> >> Did you blacklist igd driver in dom0 kernel? etc.
> >>> I think that''d be helpful for others to get a similar
baseline
> configuration.
> >>>
> >>> Thanks,
> >>>
> >>> -- Pasi
> >>>
> >>>
> >> Dear Yongjie,
> >>
> >> Could you share with us your hardware and software configuration
> >> settings?
> >>
> > Sure. My IGD is also Intel HD Graphics 4600. :-)
> >
> > 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months
ago)
> >    traditional qemu commit:
> 5ae58eaa967495fce99b727422054c58750d252b
> >    Dom0 kernel: Linux 3.8.1
> > N.B. I didn''t use the latest traditional qemu because of the
following bug:
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> >
> > 2. no offline patch. (just use the code in the tree I mentioned
above.)
> >
> > 3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all
> guest_loglvl=all unrestricted_guest=1 msi=1
> >    dom0 kernel options: ro root=/dev/sda1
> >
> > 4. HVM guest: Windows 7 Enterprise
> >
> > 5. IGD driver version in HVM: 9.18.10.3165
> >    got to: https://downloadcenter.intel.com/
> >    then, search "4th Generation Intel Core Processors with intel
hd
> graphics 4600" to download the driver.
> >
> > 6. use ''xl pci-assignable-add $BDF'' to add the IGD
as assignable.
> >    (it also use ''xen.pciback'' driver.)
> >
> > 7. dom0 kernel config is attached as file
''config-3.8.1''.
> >
> > 8. HVM guest config file:
> > builder= "hvm"
> > name= "vga-passthrough"
> > memory =1024
> > vcpus=4
> > device_model_override= ''/usr/lib/xen/bin/qemu-dm''
> > device_model_version= ''qemu-xen-traditional''
> > disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
> > vnc=1
> > serial=''pty''
> > usb = 1
> > usbdevice = ''tablet''
> > gfx_passthru=1
> > pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are
> mouse and keyboard.
> >
> > 9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to
the
> Windows guest. And the IGD can work fine.
> >    See some attached pictures for more info.
> >
> >
> > Best Regards,
> >       Yongjie (Jay)
> 
> Hi,
> 
> I was trying to compile Xen 4.3-unstable changeset 26666 when I
> encountered the following error.
> 
Sorry, I''ve no idea about this since I didn''t meet that issue.
> /usr/bin/ld: vl.o: undefined reference to symbol
> ''timer_settime@@GLIBC_2.3.3''
> /usr/bin/ld: note: ''timer_settime@@GLIBC_2.3.3'' is
defined in DSO
> /lib/x86_64-linux-gnu/librt.so.1 so try adding it to the linker command
line
> /lib/x86_64-linux-gnu/librt.so.1: could not read symbols: Invalid operation
> collect2: error: ld returned 1 exit status
> make[5]: *** [qemu-dm] Error 1
> make[5]: Leaving directory
> `/home/teo-en-ming/xen-unstable.hg-cs26666/tools/qemu-xen-traditional-
> dir-remote/i386-dm''
> make[4]: *** [subdir-i386-dm] Error 2
> make[4]: Leaving directory
> `/home/teo-en-ming/xen-unstable.hg-cs26666/tools/qemu-xen-traditional-
> dir-remote''
> make[3]: *** [subdir-install-qemu-xen-traditional-dir] Error 2
> make[3]: Leaving directory
> `/home/teo-en-ming/xen-unstable.hg-cs26666/tools''
> make[2]: *** [subdirs-install] Error 2
> make[2]: Leaving directory
> `/home/teo-en-ming/xen-unstable.hg-cs26666/tools''
> make[1]: *** [install-tools] Error 2
> make[1]: Leaving directory
`/home/teo-en-ming/xen-unstable.hg-cs26666''
> make: *** [world] Error 2
> 
> Related information:
> http://www.gossamer-threads.com/lists/xen/devel/283347
> 
> How can I fix this issue?
> 
> Thank you very much.
> 
> --
> Yours sincerely,
> 
> Singapore Citizen Mr. Teo En Ming (Zhang Enming)

> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Wednesday, July 24, 2013 7:57 PM
> To: Ren, Yongjie
> Cc: singapore.mr.teo.en.ming@gmail.com; xen-users@lists.xen.org;
> Zhang, Xiantao; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
> On Wed, Jul 24, 2013 at 10:33:38AM +0000, Ren, Yongjie wrote:
> > >
> > > Dear Yongjie,
> > >
> > > Could you share with us your hardware and software configuration
> > > settings?
> > >
> > Sure. My IGD is also Intel HD Graphics 4600. :-)
> >
> > 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months
ago)
> >   traditional qemu commit:
> 5ae58eaa967495fce99b727422054c58750d252b
> >   Dom0 kernel: Linux 3.8.1
> > N.B. I didn''t use the latest traditional qemu because of the
following bug:
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> >
> 
> Hmm.. isn''t that bug affecting qemu-traditional in general, not
PCI/GPU
> passthru specifically?
> Or is it *only* PCI/GPU passthru that it breaks for you?
> 
It''s a general device assignment issue.
Any PCI device can''t be assigned to a HVM guest with the latest
qemu-traditional.
> 
> > 2. no offline patch. (just use the code in the tree I mentioned
above.)
> >
> 
> Ok, so this is a pre-4.3 version.
> 
Yes.
> 
> > 3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all
> guest_loglvl=all unrestricted_guest=1 msi=1
> >   dom0 kernel options: ro root=/dev/sda1
> >
> > 4. HVM guest: Windows 7 Enterprise
> >
> 
> 32bit or 64bit Win7? SP1 I assume?
> 
64bit Win7.  Not SP1.  but I think SP1 is also fine.
> 
> > 5. IGD driver version in HVM: 9.18.10.3165
> >   got to: https://downloadcenter.intel.com/
> >   then, search "4th Generation Intel Core Processors with intel
hd
> graphics 4600" to download the driver.
> >
> > 6. use ''xl pci-assignable-add $BDF'' to add the IGD
as assignable.
> >   (it also use ''xen.pciback'' driver.)
> >
> 
> Is IGD the primary graphics adapter on the machine, so does BIOS initialize
> the IGD when you power-on the machine?
> Or do you have some other graphics adapter that you use in dom0 ?
> 
No additional VGA. It has only Intel IGD on that system.
For Dom0, it doesn''t use graphics adapter and I control it via network
when assigning IGD to a HVM.
> 
> > 7. dom0 kernel config is attached as file
''config-3.8.1''.
> >
> > 8. HVM guest config file:
> > builder= "hvm"
> > name= "vga-passthrough"
> > memory =1024
> > vcpus=4
> > device_model_override= ''/usr/lib/xen/bin/qemu-dm''
> > device_model_version= ''qemu-xen-traditional''
> > disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
> > vnc=1
> > serial=''pty''
> > usb = 1
> > usbdevice = ''tablet''
> > gfx_passthru=1
> > pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are
> mouse and keyboard.
> >
> > 9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to
the
> Windows guest. And the IGD can work fine.
> >   See some attached pictures for more info.
> >
> 
> Thanks a lot!
> 
> -- Pasi

> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Wednesday, July 24, 2013 7:57 PM
> To: Ren, Yongjie
> Cc: singapore.mr.teo.en.ming@gmail.com; xen-users@lists.xen.org;
> Zhang, Xiantao; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
> On Wed, Jul 24, 2013 at 10:33:38AM +0000, Ren, Yongjie wrote:
> > >
> > > Dear Yongjie,
> > >
> > > Could you share with us your hardware and software configuration
> > > settings?
> > >
> > Sure. My IGD is also Intel HD Graphics 4600. :-)
> >
> > 1. hypervisor version: c/s 26666 in xen-unstable.hg tree  (5 months
ago)
> >   traditional qemu commit:
> 5ae58eaa967495fce99b727422054c58750d252b
> >   Dom0 kernel: Linux 3.8.1
> > N.B. I didn''t use the latest traditional qemu because of the
following bug:
> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> >
> 
> Hmm.. isn''t that bug affecting qemu-traditional in general, not
PCI/GPU
> passthru specifically?
> Or is it *only* PCI/GPU passthru that it breaks for you?
> 
It''s a general device assignment issue.
Any PCI device can''t be assigned to a HVM guest with the latest
qemu-traditional.
> 
> > 2. no offline patch. (just use the code in the tree I mentioned
above.)
> >
> 
> Ok, so this is a pre-4.3 version.
> 
Yes.
> 
> > 3. hypervisor options: dom0_mem=1024M iommu=1 loglvl=all
> guest_loglvl=all unrestricted_guest=1 msi=1
> >   dom0 kernel options: ro root=/dev/sda1
> >
> > 4. HVM guest: Windows 7 Enterprise
> >
> 
> 32bit or 64bit Win7? SP1 I assume?
> 
64bit Win7.  Not SP1.  but I think SP1 is also fine.
> 
> > 5. IGD driver version in HVM: 9.18.10.3165
> >   got to: https://downloadcenter.intel.com/
> >   then, search "4th Generation Intel Core Processors with intel
hd
> graphics 4600" to download the driver.
> >
> > 6. use ''xl pci-assignable-add $BDF'' to add the IGD
as assignable.
> >   (it also use ''xen.pciback'' driver.)
> >
> 
> Is IGD the primary graphics adapter on the machine, so does BIOS initialize
> the IGD when you power-on the machine?
> Or do you have some other graphics adapter that you use in dom0 ?
> 
No additional VGA. It has only Intel IGD on that system.
For Dom0, it doesn''t use graphics adapter and I control it via network
when assigning IGD to a HVM.
> 
> > 7. dom0 kernel config is attached as file
''config-3.8.1''.
> >
> > 8. HVM guest config file:
> > builder= "hvm"
> > name= "vga-passthrough"
> > memory =1024
> > vcpus=4
> > device_model_override= ''/usr/lib/xen/bin/qemu-dm''
> > device_model_version= ''qemu-xen-traditional''
> > disk = [ ''/images/ia32e_win7.qcow,qcow2,xvda,rw'' ]
> > vnc=1
> > serial=''pty''
> > usb = 1
> > usbdevice = ''tablet''
> > gfx_passthru=1
> > pci =
[''00:02.0'',''00:1d.0'',''07:00.0'']
#''00:02.0'' is IGD; the other two are
> mouse and keyboard.
> >
> > 9. I can successfully assign this IGD 4600 (in Core i5-4670 CPU) to
the
> Windows guest. And the IGD can work fine.
> >   See some attached pictures for more info.
> >
> 
> Thanks a lot!
> 
> -- Pasi

On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie
wrote:
> > > N.B. I didn''t use the latest traditional qemu because of
the following bug:
> > >
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> > >
> > 
> > Hmm.. isn''t that bug affecting qemu-traditional in general,
not PCI/GPU
> > passthru specifically?
> > Or is it *only* PCI/GPU passthru that it breaks for you?
> > 
> It''s a general device assignment issue.
> Any PCI device can''t be assigned to a HVM guest with the latest
qemu-traditional.
> 
Ok. Is there already a separate thread on xen-devel about the qemu-traditional
PCI assignment issue?
If not, we should create one.

-- Pasi

On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie
wrote:
> > > N.B. I didn''t use the latest traditional qemu because of
the following bug:
> > >
http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> > >
> > 
> > Hmm.. isn''t that bug affecting qemu-traditional in general,
not PCI/GPU
> > passthru specifically?
> > Or is it *only* PCI/GPU passthru that it breaks for you?
> > 
> It''s a general device assignment issue.
> Any PCI device can''t be assigned to a HVM guest with the latest
qemu-traditional.
> 
Ok. Is there already a separate thread on xen-devel about the qemu-traditional
PCI assignment issue?
If not, we should create one.

-- Pasi

On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen <pasik@iki.fi> 
 wrote:
> On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>> > > N.B. I didn't use the latest traditional qemu because of
the
>> following bug:
>> > > 
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>> > >
>> >
>> > Hmm.. isn't that bug affecting qemu-traditional in general,
not
>> PCI/GPU
>> > passthru specifically?
>> > Or is it *only* PCI/GPU passthru that it breaks for you?
>> >
>> It's a general device assignment issue.
>> Any PCI device can't be assigned to a HVM guest with the latest 
>> qemu-traditional.
>>
>
> Ok. Is there already a separate thread on xen-devel about the
> qemu-traditional PCI assignment issue?
> If not, we should create one.
 FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am successfully
 passing USB, audio, GPU PCI devices using it (as long as I stay under
 the 2GB domU RAM limit). So whatever the issue is it isn't generic.

 That bug report doesn't include the domU config file, and IIRC
 I saw a similar error when device_model/device_model_override and
 device_model_version don't match or are unavailable in the build
 (e.g. building without upstream and specifying traditional or
 vice versa). More info needed to verify, I think.

 Gordan

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

On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen <pasik@iki.fi> 
 wrote:
> On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>> > > N.B. I didn't use the latest traditional qemu because of
the
>> following bug:
>> > > 
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>> > >
>> >
>> > Hmm.. isn't that bug affecting qemu-traditional in general,
not
>> PCI/GPU
>> > passthru specifically?
>> > Or is it *only* PCI/GPU passthru that it breaks for you?
>> >
>> It's a general device assignment issue.
>> Any PCI device can't be assigned to a HVM guest with the latest 
>> qemu-traditional.
>>
>
> Ok. Is there already a separate thread on xen-devel about the
> qemu-traditional PCI assignment issue?
> If not, we should create one.
 FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am successfully
 passing USB, audio, GPU PCI devices using it (as long as I stay under
 the 2GB domU RAM limit). So whatever the issue is it isn't generic.

 That bug report doesn't include the domU config file, and IIRC
 I saw a similar error when device_model/device_model_override and
 device_model_version don't match or are unavailable in the build
 (e.g. building without upstream and specifying traditional or
 vice versa). More info needed to verify, I think.

 Gordan

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

All,

On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic <gordan@bobich.net> wrote:
> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
>
>> On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>>
>>> > > N.B. I didn''t use the latest traditional qemu
because of the
>>> following bug:
>>> > >
http://bugzilla-archived.**xenproject.org//bugzilla/show_**
>>>
bug.cgi?id=1865<http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865>
>>> > >
>>> >
>>> > Hmm.. isn''t that bug affecting qemu-traditional in
general, not PCI/GPU
>>> > passthru specifically?
>>> > Or is it *only* PCI/GPU passthru that it breaks for you?
>>> >
>>> It''s a general device assignment issue.
>>> Any PCI device can''t be assigned to a HVM guest with the
latest
>>> qemu-traditional.
>>>
>>>
>> Ok. Is there already a separate thread on xen-devel about the
>> qemu-traditional PCI assignment issue?
>> If not, we should create one.
>>
>
> FWIW, I''m using qemu-dm (i.e. traditional) in 4.3 and am
successfully
> passing USB, audio, GPU PCI devices using it (as long as I stay under
> the 2GB domU RAM limit). So whatever the issue is it isn''t
generic.
>
> That bug report doesn''t include the domU config file, and IIRC
> I saw a similar error when device_model/device_model_**override and
> device_model_version don''t match or are unavailable in the build
> (e.g. building without upstream and specifying traditional or
> vice versa). More info needed to verify, I think.
>
> Gordan
>
>
> ______________________________**_________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>
And just to add a little more variety, I''m also using traditional
(under
4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7 DomU
configured with 6Gb for memory. Only using a patch to work around a broken
BIOS implementation so I have IOMMU support.

Regards,

  David


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

All,

On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic <gordan@bobich.net> wrote:
> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
>
>> On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>>
>>> > > N.B. I didn''t use the latest traditional qemu
because of the
>>> following bug:
>>> > >
http://bugzilla-archived.**xenproject.org//bugzilla/show_**
>>>
bug.cgi?id=1865<http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865>
>>> > >
>>> >
>>> > Hmm.. isn''t that bug affecting qemu-traditional in
general, not PCI/GPU
>>> > passthru specifically?
>>> > Or is it *only* PCI/GPU passthru that it breaks for you?
>>> >
>>> It''s a general device assignment issue.
>>> Any PCI device can''t be assigned to a HVM guest with the
latest
>>> qemu-traditional.
>>>
>>>
>> Ok. Is there already a separate thread on xen-devel about the
>> qemu-traditional PCI assignment issue?
>> If not, we should create one.
>>
>
> FWIW, I''m using qemu-dm (i.e. traditional) in 4.3 and am
successfully
> passing USB, audio, GPU PCI devices using it (as long as I stay under
> the 2GB domU RAM limit). So whatever the issue is it isn''t
generic.
>
> That bug report doesn''t include the domU config file, and IIRC
> I saw a similar error when device_model/device_model_**override and
> device_model_version don''t match or are unavailable in the build
> (e.g. building without upstream and specifying traditional or
> vice versa). More info needed to verify, I think.
>
> Gordan
>
>
> ______________________________**_________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>
And just to add a little more variety, I''m also using traditional
(under
4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7 DomU
configured with 6Gb for memory. Only using a patch to work around a broken
BIOS implementation so I have IOMMU support.

Regards,

  David


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

On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@gmail.com> 
 wrote:
> All,
>
> On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>
> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>   On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>   > > N.B. I didn't use the latest traditional qemu because of
the
> following bug:
>  > >
> 
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> [3]
>  > >
>  >
>  > Hmm.. isn't that bug affecting qemu-traditional in general, not
> PCI/GPU
>  > passthru specifically?
>  > Or is it *only* PCI/GPU passthru that it breaks for you?
>  >
>  It's a general device assignment issue.
>  Any PCI device can't be assigned to a HVM guest with the latest
> qemu-traditional.
>
>  Ok. Is there already a separate thread on xen-devel about the
>  qemu-traditional PCI assignment issue?
>  If not, we should create one.
>
>  FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am 
> successfully
>  passing USB, audio, GPU PCI devices using it (as long as I stay 
> under
>  the 2GB domU RAM limit). So whatever the issue is it isn't generic.
>
>  That bug report doesn't include the domU config file, and IIRC
>  I saw a similar error when device_model/device_model_override and
>  device_model_version don't match or are unavailable in the build
>  (e.g. building without upstream and specifying traditional or
>  vice versa). More info needed to verify, I think.
>
> And just to add a little more variety, I'm also using traditional
> (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
> DomU configured with 6Gb for memory. Only using a patch to work 
> around
> a broken BIOS implementation so I have IOMMU support.
 And you don't suffer from a memory stomp resulting
 in frame buffer corruption shortly followed by a domU
 crash with that much RAM passed to domU?

 Gordan

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

On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@gmail.com> 
 wrote:
> All,
>
> On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>
> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>   On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>   > > N.B. I didn't use the latest traditional qemu because of
the
> following bug:
>  > >
> 
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> [3]
>  > >
>  >
>  > Hmm.. isn't that bug affecting qemu-traditional in general, not
> PCI/GPU
>  > passthru specifically?
>  > Or is it *only* PCI/GPU passthru that it breaks for you?
>  >
>  It's a general device assignment issue.
>  Any PCI device can't be assigned to a HVM guest with the latest
> qemu-traditional.
>
>  Ok. Is there already a separate thread on xen-devel about the
>  qemu-traditional PCI assignment issue?
>  If not, we should create one.
>
>  FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am 
> successfully
>  passing USB, audio, GPU PCI devices using it (as long as I stay 
> under
>  the 2GB domU RAM limit). So whatever the issue is it isn't generic.
>
>  That bug report doesn't include the domU config file, and IIRC
>  I saw a similar error when device_model/device_model_override and
>  device_model_version don't match or are unavailable in the build
>  (e.g. building without upstream and specifying traditional or
>  vice versa). More info needed to verify, I think.
>
> And just to add a little more variety, I'm also using traditional
> (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
> DomU configured with 6Gb for memory. Only using a patch to work 
> around
> a broken BIOS implementation so I have IOMMU support.
 And you don't suffer from a memory stomp resulting
 in frame buffer corruption shortly followed by a domU
 crash with that much RAM passed to domU?

 Gordan

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

> -----Original Message-----
> From: Gordan Bobic [mailto:gordan@bobich.net]
> Sent: Thursday, July 25, 2013 5:21 PM
> To: Pasi Kärkkäinen
> Cc: Ren, Yongjie; xen-users@lists.xen.org;
> singapore.mr.teo.en.ming@gmail.com; Zhang, Xiantao;
> xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
>  On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen <pasik@iki.fi>
>  wrote:
> > On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
> >> > > N.B. I didn't use the latest traditional qemu
because of the
> >> following bug:
> >> > >
> >>
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> >> > >
> >> >
> >> > Hmm.. isn't that bug affecting qemu-traditional in
general, not
> >> PCI/GPU
> >> > passthru specifically?
> >> > Or is it *only* PCI/GPU passthru that it breaks for you?
> >> >
> >> It's a general device assignment issue.
> >> Any PCI device can't be assigned to a HVM guest with the
latest
> >> qemu-traditional.
> >>
> >
> > Ok. Is there already a separate thread on xen-devel about the
> > qemu-traditional PCI assignment issue?
> > If not, we should create one.
> 
>  FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am successfully
>  passing USB, audio, GPU PCI devices using it (as long as I stay under
>  the 2GB domU RAM limit). So whatever the issue is it isn't generic.
> 
Hi Gordan,
Can you give me the commit of the traditional-qemu with which you can
successfully pass through USB/GPU to a guest ?
If your commit is before that culprit commit in that bugzilla, it should be
certainly successful for you to do device passthrough.

Best Regards,
     Yongjie (Jay)
>  That bug report doesn't include the domU config file, and IIRC
>  I saw a similar error when device_model/device_model_override and
>  device_model_version don't match or are unavailable in the build
>  (e.g. building without upstream and specifying traditional or
>  vice versa). More info needed to verify, I think.
> 
>  Gordan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

> -----Original Message-----
> From: Gordan Bobic [mailto:gordan@bobich.net]
> Sent: Thursday, July 25, 2013 5:21 PM
> To: Pasi Kärkkäinen
> Cc: Ren, Yongjie; xen-users@lists.xen.org;
> singapore.mr.teo.en.ming@gmail.com; Zhang, Xiantao;
> xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to
> Windows 7 Ultimate HVM domU
> 
>  On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen <pasik@iki.fi>
>  wrote:
> > On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
> >> > > N.B. I didn't use the latest traditional qemu
because of the
> >> following bug:
> >> > >
> >>
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> >> > >
> >> >
> >> > Hmm.. isn't that bug affecting qemu-traditional in
general, not
> >> PCI/GPU
> >> > passthru specifically?
> >> > Or is it *only* PCI/GPU passthru that it breaks for you?
> >> >
> >> It's a general device assignment issue.
> >> Any PCI device can't be assigned to a HVM guest with the
latest
> >> qemu-traditional.
> >>
> >
> > Ok. Is there already a separate thread on xen-devel about the
> > qemu-traditional PCI assignment issue?
> > If not, we should create one.
> 
>  FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am successfully
>  passing USB, audio, GPU PCI devices using it (as long as I stay under
>  the 2GB domU RAM limit). So whatever the issue is it isn't generic.
> 
Hi Gordan,
Can you give me the commit of the traditional-qemu with which you can
successfully pass through USB/GPU to a guest ?
If your commit is before that culprit commit in that bugzilla, it should be
certainly successful for you to do device passthrough.

Best Regards,
     Yongjie (Jay)
>  That bug report doesn't include the domU config file, and IIRC
>  I saw a similar error when device_model/device_model_override and
>  device_model_version don't match or are unavailable in the build
>  (e.g. building without upstream and specifying traditional or
>  vice versa). More info needed to verify, I think.
> 
>  Gordan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Thu, Jul 25, 2013 at 9:51 AM, Gordan Bobic <gordan@bobich.net> wrote:
> On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@gmail.com>
> wrote:
>
>> All,
>>
>> On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>>
>> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>>
>>   On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>>   > > N.B. I didn''t use the latest traditional qemu
because of the
>> following bug:
>>  > >
>>
>> http://bugzilla-archived.**xenproject.org//bugzilla/show_**
>>
bug.cgi?id=1865<http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865>
>> [3]
>>
>>  > >
>>  >
>>  > Hmm.. isn''t that bug affecting qemu-traditional in
general, not
>> PCI/GPU
>>  > passthru specifically?
>>  > Or is it *only* PCI/GPU passthru that it breaks for you?
>>  >
>>  It''s a general device assignment issue.
>>  Any PCI device can''t be assigned to a HVM guest with the
latest
>> qemu-traditional.
>>
>>  Ok. Is there already a separate thread on xen-devel about the
>>  qemu-traditional PCI assignment issue?
>>  If not, we should create one.
>>
>>  FWIW, I''m using qemu-dm (i.e. traditional) in 4.3 and am
successfully
>>  passing USB, audio, GPU PCI devices using it (as long as I stay under
>>  the 2GB domU RAM limit). So whatever the issue is it isn''t
generic.
>>
>>  That bug report doesn''t include the domU config file, and
IIRC
>>  I saw a similar error when device_model/device_model_**override and
>>  device_model_version don''t match or are unavailable in the
build
>>  (e.g. building without upstream and specifying traditional or
>>  vice versa). More info needed to verify, I think.
>>
>> And just to add a little more variety, I''m also using
traditional
>> (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
>> DomU configured with 6Gb for memory. Only using a patch to work around
>> a broken BIOS implementation so I have IOMMU support.
>>
>
> And you don''t suffer from a memory stomp resulting
> in frame buffer corruption shortly followed by a domU
> crash with that much RAM passed to domU?
>
> Gordan
>
Gordan,

  No, its been stable; I tend to use that VM for gaming and for management
of an XCP instance. I even have CCC installed, so I can use overscan.
Everything I''ve used on it (Defiance, Skyrim, Oblivion, Borderlands
just to
name a few) work without issue. I''ve included the config file I use to
start it.

  For booting the hypervisor and Dom0, the options I use are:

       multiboot       /boot/xen-4.3.0.gz /boot/xen-4.3.0.gz
dom0_mem=4096M,max:4096M dom0_max_vcpus=3 loglvl=all guest_loglvl=all
apic_verbosity=debug e820-verbose=1 iommu=debug,verbose
       module  /boot/vmlinuz-linux /boot/vmlinuz-linux
root=/dev/mapper/PhoenixVG00-lvRoot ro console=hvc0 console=tty0
earlyprintk=xen

  (I use Grub2, in EFI mode)

  Specs: ASUS Sabertooth 990FX, AMD 8350, 24Gb RAM, Radeon 6770, Radeon
7750.

Regards,

  David



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

On Thu, Jul 25, 2013 at 9:51 AM, Gordan Bobic <gordan@bobich.net> wrote:
> On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@gmail.com>
> wrote:
>
>> All,
>>
>> On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>>
>> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>>
>>   On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>>   > > N.B. I didn''t use the latest traditional qemu
because of the
>> following bug:
>>  > >
>>
>> http://bugzilla-archived.**xenproject.org//bugzilla/show_**
>>
bug.cgi?id=1865<http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865>
>> [3]
>>
>>  > >
>>  >
>>  > Hmm.. isn''t that bug affecting qemu-traditional in
general, not
>> PCI/GPU
>>  > passthru specifically?
>>  > Or is it *only* PCI/GPU passthru that it breaks for you?
>>  >
>>  It''s a general device assignment issue.
>>  Any PCI device can''t be assigned to a HVM guest with the
latest
>> qemu-traditional.
>>
>>  Ok. Is there already a separate thread on xen-devel about the
>>  qemu-traditional PCI assignment issue?
>>  If not, we should create one.
>>
>>  FWIW, I''m using qemu-dm (i.e. traditional) in 4.3 and am
successfully
>>  passing USB, audio, GPU PCI devices using it (as long as I stay under
>>  the 2GB domU RAM limit). So whatever the issue is it isn''t
generic.
>>
>>  That bug report doesn''t include the domU config file, and
IIRC
>>  I saw a similar error when device_model/device_model_**override and
>>  device_model_version don''t match or are unavailable in the
build
>>  (e.g. building without upstream and specifying traditional or
>>  vice versa). More info needed to verify, I think.
>>
>> And just to add a little more variety, I''m also using
traditional
>> (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
>> DomU configured with 6Gb for memory. Only using a patch to work around
>> a broken BIOS implementation so I have IOMMU support.
>>
>
> And you don''t suffer from a memory stomp resulting
> in frame buffer corruption shortly followed by a domU
> crash with that much RAM passed to domU?
>
> Gordan
>
Gordan,

  No, its been stable; I tend to use that VM for gaming and for management
of an XCP instance. I even have CCC installed, so I can use overscan.
Everything I''ve used on it (Defiance, Skyrim, Oblivion, Borderlands
just to
name a few) work without issue. I''ve included the config file I use to
start it.

  For booting the hypervisor and Dom0, the options I use are:

       multiboot       /boot/xen-4.3.0.gz /boot/xen-4.3.0.gz
dom0_mem=4096M,max:4096M dom0_max_vcpus=3 loglvl=all guest_loglvl=all
apic_verbosity=debug e820-verbose=1 iommu=debug,verbose
       module  /boot/vmlinuz-linux /boot/vmlinuz-linux
root=/dev/mapper/PhoenixVG00-lvRoot ro console=hvc0 console=tty0
earlyprintk=xen

  (I use Grub2, in EFI mode)

  Specs: ASUS Sabertooth 990FX, AMD 8350, 24Gb RAM, Radeon 6770, Radeon
7750.

Regards,

  David



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

On Thu, 25 Jul 2013 15:06:21 +0000, "Ren, Yongjie" 
 <yongjie.ren@intel.com> wrote:
>> -----Original Message-----
>> From: Gordan Bobic [mailto:gordan@bobich.net]
>> Sent: Thursday, July 25, 2013 5:21 PM
>> To: Pasi Kärkkäinen
>> Cc: Ren, Yongjie; xen-users@lists.xen.org;
>> singapore.mr.teo.en.ming@gmail.com; Zhang, Xiantao;
>> xen-devel@lists.xen.org
>> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough 
>> to
>> Windows 7 Ultimate HVM domU
>>
>>  On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen
<pasik@iki.fi>
>>  wrote:
>> > On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>> >> > > N.B. I didn't use the latest traditional qemu
because of the
>> >> following bug:
>> >> > >
>> >>
>> 
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>> >> > >
>> >> >
>> >> > Hmm.. isn't that bug affecting qemu-traditional in
general, not
>> >> PCI/GPU
>> >> > passthru specifically?
>> >> > Or is it *only* PCI/GPU passthru that it breaks for you?
>> >> >
>> >> It's a general device assignment issue.
>> >> Any PCI device can't be assigned to a HVM guest with the
latest
>> >> qemu-traditional.
>> >>
>> >
>> > Ok. Is there already a separate thread on xen-devel about the
>> > qemu-traditional PCI assignment issue?
>> > If not, we should create one.
>>
>>  FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am 
>> successfully
>>  passing USB, audio, GPU PCI devices using it (as long as I stay 
>> under
>>  the 2GB domU RAM limit). So whatever the issue is it isn't
generic.
>>
> Hi Gordan,
> Can you give me the commit of the traditional-qemu with which you can
> successfully pass through USB/GPU to a guest ?
> If your commit is before that culprit commit in that bugzilla, it 
> should be
> certainly successful for you to do device passthrough.
 I am using unpatched 4.3.0 release version. It also worked for me
 with 4.2.2. The bug report above may be bogus - there is no
 config that was being used provided, and I recall seeing a similar
 error when I had a typo in my device_model/device_model_override or
 device_model_version config options. If you are seeing a similar
 error, make sure the values you have set are as follows (adjust
 to correct path to your qemu-dm):

 device_model_override="/usr/lib/xen/bin/qemu-dm"
 device_model_version="qemu-xen-traditional"

 Gordan

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

On Thu, 25 Jul 2013 15:06:21 +0000, "Ren, Yongjie" 
 <yongjie.ren@intel.com> wrote:
>> -----Original Message-----
>> From: Gordan Bobic [mailto:gordan@bobich.net]
>> Sent: Thursday, July 25, 2013 5:21 PM
>> To: Pasi Kärkkäinen
>> Cc: Ren, Yongjie; xen-users@lists.xen.org;
>> singapore.mr.teo.en.ming@gmail.com; Zhang, Xiantao;
>> xen-devel@lists.xen.org
>> Subject: Re: [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough 
>> to
>> Windows 7 Ultimate HVM domU
>>
>>  On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen
<pasik@iki.fi>
>>  wrote:
>> > On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>> >> > > N.B. I didn't use the latest traditional qemu
because of the
>> >> following bug:
>> >> > >
>> >>
>> 
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>> >> > >
>> >> >
>> >> > Hmm.. isn't that bug affecting qemu-traditional in
general, not
>> >> PCI/GPU
>> >> > passthru specifically?
>> >> > Or is it *only* PCI/GPU passthru that it breaks for you?
>> >> >
>> >> It's a general device assignment issue.
>> >> Any PCI device can't be assigned to a HVM guest with the
latest
>> >> qemu-traditional.
>> >>
>> >
>> > Ok. Is there already a separate thread on xen-devel about the
>> > qemu-traditional PCI assignment issue?
>> > If not, we should create one.
>>
>>  FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am 
>> successfully
>>  passing USB, audio, GPU PCI devices using it (as long as I stay 
>> under
>>  the 2GB domU RAM limit). So whatever the issue is it isn't
generic.
>>
> Hi Gordan,
> Can you give me the commit of the traditional-qemu with which you can
> successfully pass through USB/GPU to a guest ?
> If your commit is before that culprit commit in that bugzilla, it 
> should be
> certainly successful for you to do device passthrough.
 I am using unpatched 4.3.0 release version. It also worked for me
 with 4.2.2. The bug report above may be bogus - there is no
 config that was being used provided, and I recall seeing a similar
 error when I had a typo in my device_model/device_model_override or
 device_model_version config options. If you are seeing a similar
 error, make sure the values you have set are as follows (adjust
 to correct path to your qemu-dm):

 device_model_override="/usr/lib/xen/bin/qemu-dm"
 device_model_version="qemu-xen-traditional"

 Gordan

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

Just to provide another input:
My first try with a IGD4000 passthrough to win7 in a 3GB RAM domU
failed with an old XEN version (about 4.1.3?).
I then step back to use 2GB without issue.
Yesterday, I decided to have another try after moving to XEN 4.3.0.
This time 3GB works for me.
I just read another thread suggesting that this may have something to
do with the PCI address space occupied by the device you passed
through.
The bigger the occupation is, the more likely to fail. I''m not sure if
it has anything to do with the memory allocation to the IGD.

My issue is that the panel constantly flashes rapidly with different
colors once the guest starts.
It lasts until the guest loads the display driver. Quite annoy, but
still usable.

On Thu, Jul 25, 2013 at 10:51 PM, Gordan Bobic <gordan@bobich.net>
wrote:
> On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@gmail.com>
wrote:
>>
>> All,
>>
>> On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>>
>> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>>
>>   On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>>   > > N.B. I didn''t use the latest traditional qemu
because of the
>> following bug:
>>  > >
>>
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>> [3]
>>
>>  > >
>>  >
>>  > Hmm.. isn''t that bug affecting qemu-traditional in
general, not
>> PCI/GPU
>>  > passthru specifically?
>>  > Or is it *only* PCI/GPU passthru that it breaks for you?
>>  >
>>  It''s a general device assignment issue.
>>  Any PCI device can''t be assigned to a HVM guest with the
latest
>> qemu-traditional.
>>
>>  Ok. Is there already a separate thread on xen-devel about the
>>  qemu-traditional PCI assignment issue?
>>  If not, we should create one.
>>
>>  FWIW, I''m using qemu-dm (i.e. traditional) in 4.3 and am
successfully
>>  passing USB, audio, GPU PCI devices using it (as long as I stay under
>>  the 2GB domU RAM limit). So whatever the issue is it isn''t
generic.
>>
>>  That bug report doesn''t include the domU config file, and
IIRC
>>  I saw a similar error when device_model/device_model_override and
>>  device_model_version don''t match or are unavailable in the
build
>>  (e.g. building without upstream and specifying traditional or
>>  vice versa). More info needed to verify, I think.
>>
>> And just to add a little more variety, I''m also using
traditional
>> (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
>> DomU configured with 6Gb for memory. Only using a patch to work around
>> a broken BIOS implementation so I have IOMMU support.
>
>
> And you don''t suffer from a memory stomp resulting
> in frame buffer corruption shortly followed by a domU
> crash with that much RAM passed to domU?
>
>
> Gordan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Just to provide another input:
My first try with a IGD4000 passthrough to win7 in a 3GB RAM domU
failed with an old XEN version (about 4.1.3?).
I then step back to use 2GB without issue.
Yesterday, I decided to have another try after moving to XEN 4.3.0.
This time 3GB works for me.
I just read another thread suggesting that this may have something to
do with the PCI address space occupied by the device you passed
through.
The bigger the occupation is, the more likely to fail. I''m not sure if
it has anything to do with the memory allocation to the IGD.

My issue is that the panel constantly flashes rapidly with different
colors once the guest starts.
It lasts until the guest loads the display driver. Quite annoy, but
still usable.

On Thu, Jul 25, 2013 at 10:51 PM, Gordan Bobic <gordan@bobich.net>
wrote:
> On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@gmail.com>
wrote:
>>
>> All,
>>
>> On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>>
>> On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>>
>>   On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>>   > > N.B. I didn''t use the latest traditional qemu
because of the
>> following bug:
>>  > >
>>
>> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
>> [3]
>>
>>  > >
>>  >
>>  > Hmm.. isn''t that bug affecting qemu-traditional in
general, not
>> PCI/GPU
>>  > passthru specifically?
>>  > Or is it *only* PCI/GPU passthru that it breaks for you?
>>  >
>>  It''s a general device assignment issue.
>>  Any PCI device can''t be assigned to a HVM guest with the
latest
>> qemu-traditional.
>>
>>  Ok. Is there already a separate thread on xen-devel about the
>>  qemu-traditional PCI assignment issue?
>>  If not, we should create one.
>>
>>  FWIW, I''m using qemu-dm (i.e. traditional) in 4.3 and am
successfully
>>  passing USB, audio, GPU PCI devices using it (as long as I stay under
>>  the 2GB domU RAM limit). So whatever the issue is it isn''t
generic.
>>
>>  That bug report doesn''t include the domU config file, and
IIRC
>>  I saw a similar error when device_model/device_model_override and
>>  device_model_version don''t match or are unavailable in the
build
>>  (e.g. building without upstream and specifying traditional or
>>  vice versa). More info needed to verify, I think.
>>
>> And just to add a little more variety, I''m also using
traditional
>> (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
>> DomU configured with 6Gb for memory. Only using a patch to work around
>> a broken BIOS implementation so I have IOMMU support.
>
>
> And you don''t suffer from a memory stomp resulting
> in frame buffer corruption shortly followed by a domU
> crash with that much RAM passed to domU?
>
>
> Gordan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

On Thu, 25 Jul 2013 10:14:41 -0500, David Sutton <kantras@gmail.com> 
 wrote:
> On Thu, Jul 25, 2013 at 9:51 AM, Gordan Bobic  wrote:
>
> On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton  wrote:
>   All,
>
>  On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>
>  On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>
>    On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>    > > N.B. I didn't use the latest traditional qemu because of
the
>  following bug:
>   > >
>
>  
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> [3]
>  [3]
>
>   > >
>   >
>   > Hmm.. isn't that bug affecting qemu-traditional in general, not
>  PCI/GPU
>   > passthru specifically?
>   > Or is it *only* PCI/GPU passthru that it breaks for you?
>   >
>   It's a general device assignment issue.
>   Any PCI device can't be assigned to a HVM guest with the latest
>  qemu-traditional.
>
>   Ok. Is there already a separate thread on xen-devel about the
>   qemu-traditional PCI assignment issue?
>   If not, we should create one.
>
>   FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am
> successfully
>   passing USB, audio, GPU PCI devices using it (as long as I stay
> under
>   the 2GB domU RAM limit). So whatever the issue is it isn't generic.
>
>   That bug report doesn't include the domU config file, and IIRC
>   I saw a similar error when device_model/device_model_override and
>   device_model_version don't match or are unavailable in the build
>   (e.g. building without upstream and specifying traditional or
>   vice versa). More info needed to verify, I think.
>
>  And just to add a little more variety, I'm also using traditional
>  (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
>  DomU configured with 6Gb for memory. Only using a patch to work
> around
>  a broken BIOS implementation so I have IOMMU support.
>
>  And you don't suffer from a memory stomp resulting
>  in frame buffer corruption shortly followed by a domU
>  crash with that much RAM passed to domU?
>
>   No, its been stable; I tend to use that VM for gaming and for
> management of an XCP instance. I even have CCC installed, so I can 
> use
> overscan. Everything I've used on it (Defiance, Skyrim, Oblivion,
> Borderlands just to name a few) work without issue. I've included the
> config file I use to start it.
>
>   For booting the hypervisor and Dom0, the options I use are:
>
>        multiboot       /boot/xen-4.3.0.gz
> /boot/xen-4.3.0.gz dom0_mem=4096M,max:4096M dom0_max_vcpus=3
> loglvl=all guest_loglvl=all apic_verbosity=debug e820-verbose=1
> iommu=debug,verbose
>         module  /boot/vmlinuz-linux /boot/vmlinuz-linux
> root=/dev/mapper/PhoenixVG00-lvRoot ro console=hvc0 console=tty0
> earlyprintk=xen
>
>   (I use Grub2, in EFI mode)
>
>    Specs: ASUS Sabertooth 990FX, AMD 8350, 24Gb RAM, Radeon 6770,
> Radeon 7750.
 Interesting. The config looks pretty much identical to mine, but mine
 works fine for hours with a 2GB domU and crashes pretty much instantly
 when firing up a 3D app with > 2GB given to domU. The only difference
 is that I have no limiting on dom0 RAM/CPU, but I cannot see that
 being the root cause of the problem; still, will try it tonight and
 see if it makes a difference.

 Gordan

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

On Thu, 25 Jul 2013 10:14:41 -0500, David Sutton <kantras@gmail.com> 
 wrote:
> On Thu, Jul 25, 2013 at 9:51 AM, Gordan Bobic  wrote:
>
> On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton  wrote:
>   All,
>
>  On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic  wrote:
>
>  On Thu, 25 Jul 2013 12:07:25 +0300, Pasi Kärkkäinen  wrote:
>
>    On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
>    > > N.B. I didn't use the latest traditional qemu because of
the
>  following bug:
>   > >
>
>  
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1865
> [3]
>  [3]
>
>   > >
>   >
>   > Hmm.. isn't that bug affecting qemu-traditional in general, not
>  PCI/GPU
>   > passthru specifically?
>   > Or is it *only* PCI/GPU passthru that it breaks for you?
>   >
>   It's a general device assignment issue.
>   Any PCI device can't be assigned to a HVM guest with the latest
>  qemu-traditional.
>
>   Ok. Is there already a separate thread on xen-devel about the
>   qemu-traditional PCI assignment issue?
>   If not, we should create one.
>
>   FWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am
> successfully
>   passing USB, audio, GPU PCI devices using it (as long as I stay
> under
>   the 2GB domU RAM limit). So whatever the issue is it isn't generic.
>
>   That bug report doesn't include the domU config file, and IIRC
>   I saw a similar error when device_model/device_model_override and
>   device_model_version don't match or are unavailable in the build
>   (e.g. building without upstream and specifying traditional or
>   vice versa). More info needed to verify, I think.
>
>  And just to add a little more variety, I'm also using traditional
>  (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
>  DomU configured with 6Gb for memory. Only using a patch to work
> around
>  a broken BIOS implementation so I have IOMMU support.
>
>  And you don't suffer from a memory stomp resulting
>  in frame buffer corruption shortly followed by a domU
>  crash with that much RAM passed to domU?
>
>   No, its been stable; I tend to use that VM for gaming and for
> management of an XCP instance. I even have CCC installed, so I can 
> use
> overscan. Everything I've used on it (Defiance, Skyrim, Oblivion,
> Borderlands just to name a few) work without issue. I've included the
> config file I use to start it.
>
>   For booting the hypervisor and Dom0, the options I use are:
>
>        multiboot       /boot/xen-4.3.0.gz
> /boot/xen-4.3.0.gz dom0_mem=4096M,max:4096M dom0_max_vcpus=3
> loglvl=all guest_loglvl=all apic_verbosity=debug e820-verbose=1
> iommu=debug,verbose
>         module  /boot/vmlinuz-linux /boot/vmlinuz-linux
> root=/dev/mapper/PhoenixVG00-lvRoot ro console=hvc0 console=tty0
> earlyprintk=xen
>
>   (I use Grub2, in EFI mode)
>
>    Specs: ASUS Sabertooth 990FX, AMD 8350, 24Gb RAM, Radeon 6770,
> Radeon 7750.
 Interesting. The config looks pretty much identical to mine, but mine
 works fine for hours with a 2GB domU and crashes pretty much instantly
 when firing up a 3D app with > 2GB given to domU. The only difference
 is that I have no limiting on dom0 RAM/CPU, but I cannot see that
 being the root cause of the problem; still, will try it tonight and
 see if it makes a difference.

 Gordan

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