On 07/28/2011 12:44 AM, Blue Swirl wrote:
On Wed, Jul 27, 2011 at 9:42 PM, Luiz Capitulino<lcapitul...@redhat.com> wrote:
> This function should be used when the VM is not supposed to resume
> execution (eg. by issuing 'cont' monitor command).
>
> Today, we allow the user to resume execution even when:
>
> o the guest shuts down and -no-shutdown is used
> o there's a kvm internal error
> o loading the VM state with -loadvm or "loadvm" in the monitor fails
>
> I think only badness can happen from the cases above.
I'd suppose a system_reset should bring the system back to sanity and
then clear vm_permanent_stopped (where's -ly?) except maybe for KVM
internal error if that can't be recovered. Then it would not very
permanent anymore, so the name would need adjusting.
Currently, all kvm internal errors are recoverable by reset (and
possibly by fiddling with memory/registers).
--
error compiling committee.c: too many arguments to function
