[qubes-users] Re: AMD Ryzen working with IOMMU, HCL results attached

2017-05-18 Thread skilpa3
On Tuesday, May 16, 2017 at 1:35:20 AM UTC-4, Bjoern Christoph wrote:
> Am Montag, 15. Mai 2017 23:00:25 UTC+2 schrieb Grzesiek Chodzicki:
> > W dniu poniedziałek, 15 maja 2017 21:24:30 UTC+2 użytkownik Bjoern 
> > Christoph napisał:
> > > Hi all,
> > > 
> > > Attached are the HCL results of my Ryzen system.
> > > 
> > > It did NOT work out of the box on Qubes - IOMMU was not available. 
> > > However, Ubuntu stated it's working (BIOS IOMMU looks great) so I played 
> > > around a bit.
> > > 
> > > Basically, two things are needed for working IOMMU in Xen used by Qubes:
> > > 1) Update Xen with an IOMMU patch from AMD
> > > 2) Update Xen with family 17h == Ryzen
> > > 
> > > For step 1): Apply this patch (part or Xen 4.8.0): 
> > > https://patchwork.kernel.org/patch/9145119/
> > > 
> > > For step 2): xen/arch/x86/oprofile/nmi_int.c - Create a "case 0x17:" 
> > > entry which is the same as "case 0x15:"
> > > 
> > > I installed Qubes, then proceeded as described to compile Qubes from 
> > > scratch. Before I did "make vmm-xen" I changed the above files within the 
> > > xen*.gz file. After that, I moved the files to dom0 and forced a 
> > > reinstall of the RPM files.
> > > 
> > > Rebooted and voila, you can see the resul in the files :) Now I can get a 
> > > TPM I guess ;)
> > > 
> > > I posted this nmi_int.c patch also on the xen-devel mailing list, let's 
> > > see if it's enough for them.
> > > 
> > > Maybe these two patches can be added to Qubes 3.2 (if they work 
> > > properly). Not sure if there is anything else I can do to test if IOMMU 
> > > is working properly, if something is there to test that please let me 
> > > know!
> > > 
> > > Cheers,
> > > Bjoern
> > 
> > Does PCI passthrough work for Windows VMs now that IOMMU is enabled?
> 
> Ok, it's NOT working after all. Trying to install a HVM causes a reboot... so 
> I guess there is more work left there after all.
> 
> You can ignore the HCL report then as well.

Thanks for looking into this though. I'm starting to part out a system that 
will be specifically for Qubes usage and I'm very interested in the new AMD 
chips.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/81bfbbe5-f063-41da-a45a-52bba3de4015%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: AMD Ryzen working with IOMMU, HCL results attached

2017-05-15 Thread 'Bjoern Christoph' via qubes-users
Am Montag, 15. Mai 2017 23:00:25 UTC+2 schrieb Grzesiek Chodzicki:
> W dniu poniedziałek, 15 maja 2017 21:24:30 UTC+2 użytkownik Bjoern Christoph 
> napisał:
> > Hi all,
> > 
> > Attached are the HCL results of my Ryzen system.
> > 
> > It did NOT work out of the box on Qubes - IOMMU was not available. However, 
> > Ubuntu stated it's working (BIOS IOMMU looks great) so I played around a 
> > bit.
> > 
> > Basically, two things are needed for working IOMMU in Xen used by Qubes:
> > 1) Update Xen with an IOMMU patch from AMD
> > 2) Update Xen with family 17h == Ryzen
> > 
> > For step 1): Apply this patch (part or Xen 4.8.0): 
> > https://patchwork.kernel.org/patch/9145119/
> > 
> > For step 2): xen/arch/x86/oprofile/nmi_int.c - Create a "case 0x17:" entry 
> > which is the same as "case 0x15:"
> > 
> > I installed Qubes, then proceeded as described to compile Qubes from 
> > scratch. Before I did "make vmm-xen" I changed the above files within the 
> > xen*.gz file. After that, I moved the files to dom0 and forced a reinstall 
> > of the RPM files.
> > 
> > Rebooted and voila, you can see the resul in the files :) Now I can get a 
> > TPM I guess ;)
> > 
> > I posted this nmi_int.c patch also on the xen-devel mailing list, let's see 
> > if it's enough for them.
> > 
> > Maybe these two patches can be added to Qubes 3.2 (if they work properly). 
> > Not sure if there is anything else I can do to test if IOMMU is working 
> > properly, if something is there to test that please let me know!
> > 
> > Cheers,
> > Bjoern
> 
> Does PCI passthrough work for Windows VMs now that IOMMU is enabled?

Ok, it's NOT working after all. Trying to install a HVM causes a reboot... so I 
guess there is more work left there after all.

You can ignore the HCL report then as well.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/29b1a82a-0d42-495e-b9a1-2377f5bbc1a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: AMD Ryzen working with IOMMU, HCL results attached

2017-05-15 Thread Grzesiek Chodzicki
W dniu poniedziałek, 15 maja 2017 21:24:30 UTC+2 użytkownik Bjoern Christoph 
napisał:
> Hi all,
> 
> Attached are the HCL results of my Ryzen system.
> 
> It did NOT work out of the box on Qubes - IOMMU was not available. However, 
> Ubuntu stated it's working (BIOS IOMMU looks great) so I played around a bit.
> 
> Basically, two things are needed for working IOMMU in Xen used by Qubes:
> 1) Update Xen with an IOMMU patch from AMD
> 2) Update Xen with family 17h == Ryzen
> 
> For step 1): Apply this patch (part or Xen 4.8.0): 
> https://patchwork.kernel.org/patch/9145119/
> 
> For step 2): xen/arch/x86/oprofile/nmi_int.c - Create a "case 0x17:" entry 
> which is the same as "case 0x15:"
> 
> I installed Qubes, then proceeded as described to compile Qubes from scratch. 
> Before I did "make vmm-xen" I changed the above files within the xen*.gz 
> file. After that, I moved the files to dom0 and forced a reinstall of the RPM 
> files.
> 
> Rebooted and voila, you can see the resul in the files :) Now I can get a TPM 
> I guess ;)
> 
> I posted this nmi_int.c patch also on the xen-devel mailing list, let's see 
> if it's enough for them.
> 
> Maybe these two patches can be added to Qubes 3.2 (if they work properly). 
> Not sure if there is anything else I can do to test if IOMMU is working 
> properly, if something is there to test that please let me know!
> 
> Cheers,
> Bjoern

Does PCI passthrough work for Windows VMs now that IOMMU is enabled?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/91813d9e-c936-4a32-82cc-2fad02e453ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.