For what-the-heck reasons, git bisection miserably failed to reveal what patch caused this regression. It narrowed it down however and together with the dumped state of a hanging guest, I think I tracked to problem down to
commit ddacf5ef684a655abe2bb50c4b2a5b72ae0d5e05 Author: Olaf Hering <[email protected]> Date: Thu Sep 22 16:14:49 2011 +0200 xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel The problem seems to be that (at least up to the version of Xen which I am using right now, and I deliberately did not update) xenstore seems to just ignore the message and not return an error. And for that reason the whole init remains stuck in xs_init(), while waiting for the reply to the reset watches message. Now, right now this can mean two things: 1. The hypervisor (actually xenstord in dom0) is supposed to be updated to return an error, if it cannot handle a message. 2. The kernel messaging code should expect no answer and trigger a timeout error. I need to start a discussion upstream to find out the answer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901305 Title: precise fails boot on ec2 hvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/901305/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
