One more thing: Considering the number of people affected and the fact that this bug has already been solved in upstream stable Xen releases I wonder why this has been given so little attention as it seems. Importance "undecided" and "unassigned" suggest that this bug is not treated with any priority.
This bug appears also in xen 4.1 used in Quantal and Precise, one of which is a LTS release affecting many users.
Would upgrading to Xen 4.1.5 stable fix this issue in Quantal and Precise ? See https:/ /bugs.launchpad .net/ubuntu/ +source/ xen/+bug/ 1180396
One more thing: Considering the number of people affected and the fact that this bug has already been solved in upstream stable Xen releases I wonder why this has been given so little attention as it seems. Importance "undecided" and "unassigned" suggest that this bug is not treated with any priority.