https://bugzilla.novell.com/show_bug.cgi?id=815897 https://bugzilla.novell.com/show_bug.cgi?id=815897#c2 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jbeulich@suse.com InfoProvider| |yury@gy.pp.ru AssignedTo|jdouglas@suse.com |carnold@suse.com QAContact|qa-bugs@suse.de |jdouglas@suse.com --- Comment #2 from Charles Arnold <carnold@suse.com> 2013-04-22 15:36:01 UTC --- I believe you are seeing the results of a fix due to the following Xen Security Advisory specific to AMD processors. http://lists.xen.org/archives/html/xen-announce/2013-02/msg00002.html "Note that on certain systems (SP5100 chipsets with erratum 28 present, or such with broken IVRS ACPI table) these patches will result in the IOMMU not being enabled anymore. This should be dealt with by a BIOS update, if available. Alternatively the check can be overridden by specifying "iommu=no-amd-iommu-perdev-intremap" on the Xen command line ("iommu=amd-iommu-global-intremap" on 4.1.x), at the price of re-opening the security hole addressed by these patches." The above paragraph describes a work around solution. Please try the Xen command line flag (iommu=amd-iommu-global-intremap). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.