Hi. I've just created some virtualized VM's of the unRAID OS using v4.5.3 and v4.5.1, and while the console of the VM(s) sits idle, I've noticed a whole heap of these 'Hangcheck: hangcheck value past margin!' messages one above another.

I've never seen this message on a physical unRAID server, only on a virtualized one. I'm using Virtual Box as the virtualizer application. Any clue what it means or reason why this message is appearing? From my brief testing, their doesn't seem to be any issues with the VM(s) thus far (Though I haven't fully tested the VM rig to it's full potential). Thanks.

Weird. I've never encountered that in my use of VirtualBox.

 

It seems like it's an option enabled in the unRAID specific Kernel relating to watchdog timers.

 

http://linux.derkeiler.com/Mailing-Lists/Kernel/2006-01/msg00330.html

it means you enabled the hangcheck timer watchdog, and it seems to think

the kernel is too busy or losing time

Did you mean to enable that watchdog?

In VirtualBox you just ignore that message.

 

So nothing to be concerned about if it is running under VirtualBox? It hasn't impacted the VM from what I've seen (Though I am running these VMs on a five year old laptop), it struck me as odd as to what or why it was occuring. Thanks BRiT and purko.

 

In VirtualBox you just ignore that message.

 

With that old of a system, it may not be able to virtualize / pass-through that particular watchdog timer or it could take a longer to update that timer than the Linux Kernel is using to determine if it should log a warning.

Yeah that could explain it. The performance of the Windows OS hosting the VM is lagging in performance (Running Windows 7, as appose to previously running Windows XP). The Laptop is a +5years old  is a HP Compaq NC6220 and has a Intel Centrino 1.7GHz (no dual cores on laptops back then ), 1.5GB DDR1 RAM and using an IDE disk (not even SATA), so it is a paltry machine for VM's ld of left it on Win XP), all my good machines are servers and my current desktop is no better.

I'm planning to build a desktop with a lot more horse power this weekend, so I'll see how it cug's along on the newer Desktop and whether the Hangcheck message reappears again, or as frequently anways. Thanks BRiT.

 

With that old of a system, it may not be able to virtualize / pass-through that particular watchdog timer or it could take a longer to update that timer than the Linux Kernel is using to determine if it should log a warning.