Approaches I could imagine are:
- use counter of some interrput delivery you're sure you kernel uses 
(timer?) and see when it stops
- periodically stop kernel and ensure that PC doesn't change (but halt 
loop in idle kernel will match
that definition too)
- modify guest to perform certain action on NMI (or use guest execute 
functionality to crash inside guest)

But generally Klaus is right, definition of what you looking for is 
pretty vague.

Nikolay

06.02.2012 20:39, Barash, Danny пишет:
> When the kernel stops functioning.
>
> -----Original Message-----
> From: Klaus Espenlaub [mailto:[email protected]]
> Sent: Monday, February 06, 2012 18:28
> To: [email protected]
> Subject: Re: [vbox-dev] detecting kernel panic
>
> On 06.02.2012 15:17, Barash, Danny wrote:
>> Hi all
>> -I'm working with the Java web service interface,
>> And a guest Unix vm. (Bunt shell only 3.x)
>> I'm putting the Unix vm in kernel panic (using "injectnmi ")
>> And I just can't find a way to query, programmatically, whether the
>> Vm is stuck or not.
> What kind of "stuck" definition do you have in mind?
>
> Klaus
>
>> -I tried using metrics but they all stay the same before and after the
>> crush.
>> Thanks, Danny.
>> ---------------------------------------------------------------------
>> Intel Israel (74) Limited
> _______________________________________________
> vbox-dev mailing list
> [email protected]
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> _______________________________________________
> vbox-dev mailing list
> [email protected]
> https://www.virtualbox.org/mailman/listinfo/vbox-dev


_______________________________________________
vbox-dev mailing list
[email protected]
https://www.virtualbox.org/mailman/listinfo/vbox-dev

Reply via email to