Hello list, I migrated my home server to a VM last week (used MondoRescue images for the P2V process). Initially, everything seemed to work well. But for the last few days, the VM has started to show a strange behaviour:
- sometimes right after boot, sometimes after several hours of operation, its CPU usage would reach 100% (the host itself and the other VM are unaffected). - login on the console is sometimes still possible with a lot of patience, but in most cases it no longer responds - NFS mount requests fail, but the VM still answer ping requests - named dies with the following error message: ---------------------------<cut>---------------------------- Nov 28 12:06:37 wopr kernel: [1267439601.897597] Clocksource tsc unstable (delta = -161077616 ns) Nov 28 12:06:37 wopr named[2338]: timer.c:708: fatal error: Nov 28 12:06:37 wopr named[2338]: RUNTIME_CHECK(isc_time_now((&now)) == 0) failed Nov 28 12:06:37 wopr named[2338]: exiting (due to fatal error in library) ---------------------------<cut>---------------------------- - the internal clock of the server becomes completely wrong (possibly by tens of years) There's usually nothing else to do but power off the VM and restart it. PVE is version 4.1 on a HP Proliant DL380 Gen6. The OS inside the VM is OpenSuSE 11.2 32bit (kernel 2.6.31.14-0.8-desktop). Any idea as to what could cause this? If you need more info about the setup, just ask. Thanks in advance. Best regards, Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: [email protected] <http://www.iba-worldwide.com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
