Sorry for the precedent post that was written a bit too fast. Libreboot was
flashed when I wrote it, which is the equivalent of a having vt-d
deactivated (iommu=0). Thanks to a user that read this post and wrote to me
personally so I could do my mea culpa. Sorry for the precedent misleading
post.
The problem wasn't with xen iommu support but kms/drm and i915 driver.
Passing to the kernel i915.preliminary_hw_support=1 fixes it all :)
Thanks
Le sam. 20 févr. 2016 à 22:44, Thierry Laurion
a écrit :
> Le mar. 26 janv. 2016 à 05:52, Jan Beulich a écrit :
>
>> >>> On 25.01.16 at 22:49, wro
Le mar. 26 janv. 2016 à 05:52, Jan Beulich a écrit :
> >>> On 25.01.16 at 22:49, wrote:
> > The case is 1) disabling iommu for IGD, unilaterally since i915 + gm45
> > doesn't play well together. Iommu is still desired to isolate usb and
> > network devices, so we don't want to disable iommu comp
Le lun. 1 févr. 2016 à 07:35, Jan Beulich a écrit :
> >>> On 01.02.16 at 13:28, wrote:
> > On Mon, Feb 01, 2016 at 12:59:00AM -0700, Jan Beulich wrote:
> >> >>> On 30.01.16 at 02:47, wrote:
> >> > On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
> >> >> (re-adding xen-devel)
> >> >>
>>> On 01.02.16 at 13:28, wrote:
> On Mon, Feb 01, 2016 at 12:59:00AM -0700, Jan Beulich wrote:
>> >>> On 30.01.16 at 02:47, wrote:
>> > On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
>> >> (re-adding xen-devel)
>> >>
>> >> >>> On 26.01.16 at 12:28, wrote:
>> >> > Iommu=0 let the
On Mon, Feb 01, 2016 at 12:59:00AM -0700, Jan Beulich wrote:
> >>> On 30.01.16 at 02:47, wrote:
> > On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
> >> (re-adding xen-devel)
> >>
> >> >>> On 26.01.16 at 12:28, wrote:
> >> > Iommu=0 let the whole Qubes system work, without enforcing
>>> On 30.01.16 at 02:47, wrote:
> On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
>> (re-adding xen-devel)
>>
>> >>> On 26.01.16 at 12:28, wrote:
>> > Iommu=0 let the whole Qubes system work, without enforcing hardware
>> > compartimentalisation (iommu is enforced in software mode)
On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
> (re-adding xen-devel)
>
> >>> On 26.01.16 at 12:28, wrote:
> > Iommu=0 let the whole Qubes system work, without enforcing hardware
> > compartimentalisation (iommu is enforced in software mode)
> >
> > When iommu=no-igfx is enforced,
It seems that IGD iommu is not completely deactivated, yes, since memory
corruption happens (graphic glitches and then system hang)
General iommu is still reported as being active by xen, as desired.
Thierry
Le mar. 26 janv. 2016 17:21, Tian, Kevin a écrit :
> > From: Jan Beulich
> > Sent: Tue
> From: Jan Beulich
> Sent: Tuesday, January 26, 2016 8:28 PM
>
> >>> On 26.01.16 at 12:57, wrote:
> > Only dom0 talks directly to the i915 driver, other appvm being pv, which is
> > why I put in question the complete deactivation of IGD by iommu=no-igfx.
> >
> > Is there anything I can provide t
>>> On 26.01.16 at 12:57, wrote:
> Only dom0 talks directly to the i915 driver, other appvm being pv, which is
> why I put in question the complete deactivation of IGD by iommu=no-igfx.
>
> Is there anything I can provide to troubleshoot?
Hard to tell. The VT-d maintainers may be able to give yo
Only dom0 talks directly to the i915 driver, other appvm being pv, which is
why I put in question the complete deactivation of IGD by iommu=no-igfx.
Is there anything I can provide to troubleshoot?
Le mar. 26 janv. 2016 06:37, Jan Beulich a écrit :
> (re-adding xen-devel)
>
> >>> On 26.01.16 at
(re-adding xen-devel)
>>> On 26.01.16 at 12:28, wrote:
> Iommu=0 let the whole Qubes system work, without enforcing hardware
> compartimentalisation (iommu is enforced in software mode)
>
> When iommu=no-igfx is enforced, shell console boot up works flawlessly. All
> domu machines get booted up.
>>> On 25.01.16 at 22:49, wrote:
> The case is 1) disabling iommu for IGD, unilaterally since i915 + gm45
> doesn't play well together. Iommu is still desired to isolate usb and
> network devices, so we don't want to disable iommu completely. The side
> effect of this would be to have IGD only for
The case is 1) disabling iommu for IGD, unilaterally since i915 + gm45
doesn't play well together. Iommu is still desired to isolate usb and
network devices, so we don't want to disable iommu completely. The side
effect of this would be to have IGD only for dom0, which would also
completely make se
>>> On 23.01.16 at 08:38, wrote:
> Thinkpad x200 p8600 laptops have vt-d, vt-x and tpm. They also have intel
> integrated graphics 4 Series (gm45 chipset), supported through i915 driver.
>
> In December, a fix got introduced to Xen 4.6 through iommu=no-igfx switch.
> Before that fix, it was impos
On 24/01/16 18:21, Thierry Laurion wrote:
> Hi devs!
>
> XEN devs:
> As per short discussion with ktemkin earlier in January in #xen:
>
> "ktemkin Jan 10, 2016 16:21:50
> This test patch did appear to make the system work, though:
> https://gist.github.com/ktemkin/0e81b93654ae800a5609
>
> ktemkin J
Hi devs!
XEN devs:
As per short discussion with ktemkin earlier in January in #xen:
"ktemkin Jan 10, 2016 16:21:50
This test patch did appear to make the system work, though:
https://gist.github.com/ktemkin/0e81b93654ae800a5609
ktemkin Jan 10, 2016 16:24:55
Only real difference I see between tha
Hey devs,
Thinkpad x200 p8600 laptops have vt-d, vt-x and tpm. They also have intel
integrated graphics 4 Series (gm45 chipset), supported through i915 driver.
In December, a fix got introduced to Xen 4.6 through iommu=no-igfx switch.
Before that fix, it was impossible to boot xen without passing
19 matches
Mail list logo
