From: gnafou <fmgre-liste01deb@yahoo.fr>
To: kvm@vger.kernel.org
Subject: user: time jump in slave machine leads to freeze
Date: Tue, 25 Jan 2011 15:21:41 +0000 (GMT) [thread overview]
Message-ID: <717572.90356.qm@web29502.mail.ird.yahoo.com> (raw)
Hello
We have had several cases where a slave machine freezes, eating all available
cpu. ( this happends randomly, say, after 3 months of correct functionning )
After reboot, looking at the syslog when the freeze occured, the few ( ~5 )
last lines written show a date which has jumped in the future ( roughly, 15 days
ahead ), but nothing related to the crash is logged.
our salves machines are ntp-synchronized
we run under debian/lenny
we launch the machines with the kvm command
kernel of host : 2.6.26-2-amd64
kernel of host : 2.6.26-2-686
command launched :
kvm -name svn -drive file=xxx -net tap -m 256 -net nic,macaddr=xxx -pidfile
/var/run/kvm/xx.pid -daemonize -k fr -vnc :63006 -monitor
unix:xx_monitor,server,nowait -vnc unix:xx_vnc
If you ever have an idea how to solve or to debug the problem ...
Thanks
Fred
next reply other threads:[~2011-01-25 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 15:21 gnafou [this message]
2011-01-25 17:57 ` user: time jump in slave machine leads to freeze Brian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=717572.90356.qm@web29502.mail.ird.yahoo.com \
--to=fmgre-liste01deb@yahoo.fr \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox