[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] After upgrade from 4.1 -> 4.3 domU will not boot with iommu=soft

  • To: xen-users@xxxxxxxxxxxxx
  • From: Tomas Agartz <tlund@xxxxxx>
  • Date: Sun, 22 Dec 2013 16:28:30 +0100 (CET)
  • Delivery-date: Sun, 22 Dec 2013 15:29:47 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

My system is a Thinkpad x220 laptop with Debian 7.3 x64 (kernel 3.2 and xen 4.1).

I have one DomU and it has two PCI-devices assigned. The domU kernel needs to boot with "iommu=soft" for this to work properly. Everything working as expected in both dom0 and domU except dom0 acpi suspend/resume. (suspends fine, but does not wake up on resume).

After spening some time on google I find out that resume is not really working with 3.2 kernel and xen 4.1 (needs atleast 3.11 and 4.2.2).

I upgrade to the 3.12 kernel and xen 4.3 packages from from debian unstable. Doing acpi suspend/resume now works witout any other modification to the system.

However, the domU will no longer boot. When pygrub starts the kernel (after running "xm start -c domu"), there is ZERO output and I get the prompt of the dom0 back after about 3-4 seconds. (I removed the "quiet" option from the kernel, ofc). xend.log just says "Domain has crashed".

If i remove the "iommu=soft" option from the domU kernel, it boots fine (but the PCI devices are not working in the domU).

After searching for people with similar problems I increased the domU memory from 256 to 512 Mbyte. I also tried upgrading the domU kernel to the same 3.12 kernel as the dom0 is using, but neither of those things helped.

Looking for any hints on how to go forwards :)

Best regards,

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.