Hi, I thought that some of those verbose logging notifications were errors like for example "traps.c:2685:d0v10 Domain attempted WRMSR"
Well, now the system is booting but would you have any idea why the system only boots with iommu=verbose,debug but not with iommu=1? If I pass iommu=1 as a boot parameter it fails detecting SATA drives (AHCI) with "ata1.00: failed command: IDENTIFY DEVICE" error. Also USB fails with fatal error, "ehci_hcd 0000:xx:xxx:xx: HC died". Also if I try to pass dom0pvh=1 it also crashes with iommu=verbose,debug - screen just goes completely black and system restarts itself - no way to see any error messages at all. 2015-09-09 11:56 GMT+03:00 Jan Beulich <jbeul...@suse.com>: > >>> On 08.09.15 at 15:21, <kiviniemi.valtt...@gmail.com> wrote: > > I got Xen booting now with VT-d enabled, lot's of errors and the system > is > > unstable. xl dmesg output: > > Lots of errors? I don't see much - can you point out the errors you see? > There are two interesting things: > > > (XEN) [VT-D]iommu.c:1149: drhd->address = fbffd000 iommu->reg = > ffff82c000201000 > > (XEN) [VT-D]iommu.c:1151: cap = d2008c10ef0466 ecap = f0205b > >[...] > > (XEN) [VT-D]iommu.c:1149: drhd->address = fbffc000 iommu->reg = > ffff82c000203000 > > (XEN) [VT-D]iommu.c:1151: cap = d2078c106f0466 ecap = f020df > > Two IOMMUs with different capabilities. I'll have to look at what > specifically one supports which the other doesn't, but I wouldn't > be surprised if code wouldn't fully cope with that. > > > (XEN) Failed to enable Interrupt Remapping: Will not enable x2APIC. > > But later ... > > > (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. > > (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. > > (XEN) Intel VT-d Snoop Control not enabled. > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > (XEN) Intel VT-d Queued Invalidation enabled. > > (XEN) Intel VT-d Interrupt Remapping enabled. > > ... and ... > > > (XEN) I/O virtualisation enabled > > (XEN) - Dom0 mode: Relaxed > > (XEN) Interrupt remapping enabled > > I'll have to check what this inconsistency means. > > Apart from that the request for a native kernel log with IOMMU > enabled still stands (for comparison as well as quirk identification > purposes). > > Jan > >
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
