Red Hat Bugzilla – Bug 865665
host boot fail and when system boots with kernel parameter intel_iommu=on
Last modified: 2013-01-09 07:10:06 EST
Description of problem:
As subject. and cann't get useful infomation from monitor. I attached host serial console log.
Hit this issue with kernel-2.6.32-328.el6、kernel-2.6.32-320.el6 and kernel-2.6.32-325.el6.
For kernel-2.6.32-279.el6(GA kernel), It works well and haven't hit this issue.
Since kvm QE have tested device assignment and don't hit this issue on rhel6.3 GA
so add 'regression' keywords.
Currently, kvm QE want to test 'device assignment' with the latest kernel, because this bug we cann't continue. so add 'blocker' flags.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot system with kernel parameter intel_iommu=on
boot fail, and monitor cann't get useful infomation.
Is this on any system at all or on a particular type of system? Moving to kernel since this is a host IOMMU bug.
2.6.32-329.el6.x86_64 boots fine on my system with intel_iommu=on, maybe something x2apic related?
I don't see attached console log.
Please also provide:
lspci, lspci -vvv, lspci -t output
dmesg log when no intel_iommu=on
Try a boot with 'intel_iommu=strict'
Created attachment 627914 [details]
host serial console log
(In reply to comment #4)
> I don't see attached console log.
I attached a console log.
> Please also provide:
> lspci, lspci -vvv, lspci -t output
> dmesg log when no intel_iommu=on
This log file include lspci, lspci -vvv, lspci -t output and dmesg information.
> Try a boot with 'intel_iommu=strict'
host boot successfully and work well.
Created attachment 627916 [details]
lspci and dmesg log
Talked to the reporter, the reporter filed the two same( bz865666 and bz865665) bug by mistaking. Close one
*** This bug has been marked as a duplicate of bug 865666 ***