Dear self,
This is the second time this has happened to me, so I'm writing to you, my future self, a quick note so you don't have to relearn this a second time.
If when restarting a DomU, the DomU hangs at "Checking for hardware changes", check on the Dom0 to see if your xenconsoled has died. If so, restart it (ie. /usr/sbin/xenconsoled) and it should immediately fix the hanging DomUs.
This guy has a blog post with same issue, but I don't think he ever figured it out because he took a scorched-earth route to fix the problem. However, it does have a nice screen shot of what the hung DomU looks like.
Yours truely,
yourself
Subscribe to:
Post Comments (Atom)
2 comments:
Thanks, this gave me a pointer to try. I restarted xendomains also and that seemed to break through the checking hardware changes logjam.
Thx for sharing! I saw a similar post, however, my xenconsoled wasn't dead, it was running in the process table but definitely acting like a zombie proc. I copied it's flags and ran "xenconsoled --log none --timestamp none --log-dir /var/log/xen/console", had an open vncviewer session for the console and saw my DomU finally pass "Checking for hardware changes".
Post a Comment