|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] Re: [PATCH] x86: Reboot CPU on triple fault - Version 4 |
Date: | Thu, 17 Apr 2008 07:49:04 -0500 |
User-agent: | Thunderbird 2.0.0.12 (X11/20080227) |
Jan Kiszka wrote:
Anthony Liguori wrote:Why is it so important to log triple faults? Printing something to stderr instead of logfile is just wrong. What is your use-case? I think you've got the wrong solution to the problem and I can't find an adequate description of the problem your trying to solve in this thread.You may not always sit next to your VM when it decides to reboot due to a _real_ problem that caused a triple fault.
You can always check within the guest to see if it's rebooted (via uptime for instance).
It's extremely unlikely you'll ever see an OS triple fault in the wild unless you're doing kernel development. Triple faulting requires a bad IDT or a really bad page table both of which are not something an OS is likely to do by accident. If your OS is triple faulting, I highly doubt it's just going to reboot and everything's going to be okay.
Besides, the -no-reboot flag should already satisfy your needs if you're really concerned about it.
Regards, Anthony Liguori
Jan
[Prev in Thread] | Current Thread | [Next in Thread] |