From: Brian Jackson <iggy@theiggy.com>
To: gnafou <fmgre-liste01deb@yahoo.fr>
Cc: kvm@vger.kernel.org
Subject: Re: user: time jump in slave machine leads to freeze
Date: Tue, 25 Jan 2011 11:57:48 -0600 [thread overview]
Message-ID: <4D3F0F1C.4070603@theiggy.com> (raw)
In-Reply-To: <717572.90356.qm@web29502.mail.ird.yahoo.com>
On 1/25/2011 9:21 AM, gnafou wrote:
> 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
I'm pretty sure this issue has been fixed in newer versions of qemu-kvm
and the kernel. You might want to try using the versions from backports.
You are unlikely to get much support on a kernel that's 10 releases old
and iirc, the kvm that came with lenny was only a development snapshot.
> 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
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-01-25 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 15:21 user: time jump in slave machine leads to freeze gnafou
2011-01-25 17:57 ` Brian Jackson [this message]
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=4D3F0F1C.4070603@theiggy.com \
--to=iggy@theiggy.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.