[Bug 815897] New: xen 4.1.4 -not run the virtual machine using the physical device (Xen PCI Passthrough)
https://bugzilla.novell.com/show_bug.cgi?id=815897 https://bugzilla.novell.com/show_bug.cgi?id=815897#c0 Summary: xen 4.1.4 -not run the virtual machine using the physical device (Xen PCI Passthrough) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: yury@gy.pp.ru QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120909 Firefox/15.0.1 Lightning/2.2b1 After the upgrade from version xen 4.1.3 to version 4.1.4 stopped running virtual machines using physical pci device. When the command xm start <vm>, the message that the system is turned off option vt-d (iommu) or the device is not under the control of the driver pciback. After rolling back to a version xen 4.1.3 performance is restored. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=815897 https://bugzilla.novell.com/show_bug.cgi?id=815897#c1 Daniel Delin <subscribe@unix.no-ip.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |subscribe@unix.no-ip.org --- Comment #1 from Daniel Delin <subscribe@unix.no-ip.org> 2013-04-21 21:50:06 UTC --- I have this problem too, after reverting to 4.1.3 it works again. Running AMD-8350 on a Gigabyte GA-990FXA-UD5 Bios version F11. -- 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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=815897 https://bugzilla.novell.com/show_bug.cgi?id=815897#c3 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|yury@gy.pp.ru | Resolution| |NORESPONSE --- Comment #3 from Charles Arnold <carnold@suse.com> 2013-05-07 14:35:48 UTC --- No response. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com