Comment 24 for bug 144631

#17 Todd: I have just checked the xencons line and it is correct, but when booting the domU with 2.6.22 kernel it hangs after mounting the filesystem as always. As you (Stephen and you) have been discussing, I think this is related to bug #139046 as you do, and because of the similar symptoms it could be confused with this one.

#18 Stephen: "The workaround I've found in the meantime is to install the 2.6.19-4 kernel mentioned above on the xen dom0 and domU machines, then specify that as the kernel to boot from in the configuration for the domU machine."

This is working for me either, and I think Todd also said that he had managed to get domU running with this kernel. So we get to the point that something in 2.6.22 generic xen kernel could be broken or bad configured.

#19 Todd: "My question still is: what broke in the kernels after 2.6.19-4, which is when the xen kernels started matching the Ubuntu kernel numbers, that caused the hanging of guest and/or missing console?"

From my point of view, this is the million dollar question.

So to sum up. I'm using Gutsy server beta in a Poweredge 860 Dell, which has probably different network cards than yours do. Anyway I don't rule out a network related problem, but It is rare that we all suffer the same symptoms and probably the unique thing we have in common is that the 2.6.22 xen kernel doesn't work and the 2.6.19 amd64 does.

When I boot a domU with the 2.6.22, even if I create it without console it hangs and I have never seen it answering a ping (which makes impossible to ssh by default).

I hope we will fix this before the final Gutsy release.

Regards