| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Frozen xen domU
Mark Adams wrote:
Debian Lenny amd64, xen 3.2.1
For the first time in a couple of years, I had a paravirt VM freeze on
me the other day, running at 400% CPU in xm list (4 vcpu). The dom0
machine was still operating correctly, but the domU was not accessible
(either via ssh or xm console). Other paravirt instances on the same
dom0 were also still running correctly. After running xm destroy and
recreating the vm, it was accessible again.
Nothing in the dom0 or domU logs indicate any errors, just that
everything in the domU froze about the same time.
Has anyone seen this and could offer a reason why or advise how best I
might be able to troubleshoot this? This sounds like it's a problem with
something inside the VM rather than Xen, however why couldn't I connect
with xm console?
Yes, I get this as well.
stop xend - /etc/init.d/xend stop
find the process id for xenconsoled - ps axl | grep xenconsoled
kill it
start xend - /etc/init.d/xend start
The DomU will resume where it was. It's sort of second nature -
Nagios reports a virtual server as down, first thing I do is log into
Dom0 to check.
See this thread :
http://lists.xensource.com/archives/html/xen-users/2009-07/msg00326.html
--
Simon Hobson
Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home