Hi,
Yesterday I decided to upgrade my Xen version from 4.6.0 to 4.8.0. I
compiled it from source and at the same time I compiled the latest Linux
kernel (4.10.1).
When rebooting I decided to try if dom0 PVH would work (with previous Xen
version it just caused kernel panic). Seemed to boot fine un
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
PCI routing entry (9-2 -> 0xc8 -> IRQ 26 Mode:1
Active:1)
(XEN) IOAPIC[1]: Set PCI routing entry (9-8 -> 0x21 -> IRQ 32 Mode:1
Active:1)
(XEN) IOAPIC[1]: Set PCI routing entry (9-16 -> 0x39 -> IRQ 40 Mode:1
Active:1)
(XEN) d0: Forcing read-only access to MFN fed00
(XEN) IOAPIC[
Hi,
Sorry about that, I'm using gmail and misclicked reply instead of
reply-all. No Idea how to fix the line wrapping though.
Any ideas how to enable IOMMU in vanilla kernel? I checked from kernel
documentation that the parameters are intel_iommu=on and iommu=force and
they were passed as a boot
Hi,
Well, getting a boot log with Xen seems to be really hard. Meanwhile,
here's a boot log from native 4.2.0 kernel with IOMMU enabled.
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 4.2.0-dom0 (root@xen) (gcc version 4.9.2
(Debian 4.9.2-10) ) #2 SMP Mon Sep 7 15:24:1
S/Xen bug that
VMware has been able to solve (or then they do something differently).
I'm happy to help to debug this further if needed, but so far I'm not able
to boot the system at all without iommu=0 boot parameter.
Best regards,
Valtteri Kiviniemi
___
