[Xen-bugs] [Bug 1644] xen does not boot when iommu is on after upgrading to xen 4.0.1-rc5 from rc3

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1644





------- Comment #23 from darkbasic4@xxxxxxxxx  2011-01-20 13:10 -------
Sorry for the late answer but I had some problems with the serial console...

xen_log.log is the log with iommu=passthrough iommu=verbose console=hvc0
earlyprintk=xen nomodeset initcall_debug debug loglevel=10.

log_only_verbose.log is a smaller log with iommu=verbose only.

Debian Squeeze gained a new hypervisor revision (it's the one I used for the
logs), here is the changelog:

linux-image-2.6.32-5-xen-amd64 2.6.32-30
xen-hypervisor-4.0-amd64 4.0.1-2

Changes:
 xen (4.0.1-2) unstable; urgency=low
  * Fix races in memory management.
  * Make sure that frame-table compression leaves enough alligned.
  * Disable XSAVE support. (closes: #595490)
  * Check for dying domain instead of raising an assertion.
  * Add C6 state with EOI errata for Intel.
  * Make some memory management interrupt safe. Unsure if really needed.
  * Raise bar for inter-socket migrations on mostly-idle systems.
  * Fix interrupt handling for legacy routed interrupts.
  * Allow to set maximal domain memory even during a running change.
  * Support new partition name in pygrub. (closes: #599243)
  * Fix some comparisions "< 0" that may be optimized away.
  * Check for MWAIT support before using it.
  * Fix endless loop on interrupts on Nehalem cpus.
  * Don't crash upon direct GDT/LDT access. (closes: #609531)
    CVE-2010-4255
  * Don't loose timer ticks after domain restore.
  * Reserve some space for IOMMU area in dom0. (closes: #608715)
  * Fix hypercall arguments after trace callout.
  * Fix some error paths in vtd support. Memory leak.
  * Reinstate ACPI DMAR table.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs