qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Purna Chandar <purnachandar.midi@oneconvergence.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: guest OS crash during shutdown/reboot
Date: Mon, 7 Dec 2009 14:32:19 +0530	[thread overview]
Message-ID: <c56848720912070102g987441rbc506f97bfe71fac@mail.gmail.com> (raw)
In-Reply-To: <c56848720910292056t8cd6e76t32617a230e215eb6@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

The culprit seems to be a soft lockup during shutdown because of the smp
code. Adding nosmp command line option to the guest kernel does not cause
this problem.

2009/10/30 Purna Chandar <purnachandar.midi@oneconvergence.com>

> Can somebody out there please help me with this issue.
>
> Thanks,
> PurnaChandar M
>
> 2009/10/26 Purna Chandar <purnachandar.midi@oneconvergence.com>
>
> Hi,
>> I have compiled qemu 0.11.0 for x86 64 bit. I run Fedora Core 10 64 bit as
>> my guest OS.
>> Sometimes, when I shutdown the guest OS gracefully (using halt command), I
>> see a kernel crash with a stack trace on guest OS window at *
>> native_machine_shutdown()*. The RIP points to *native_smp_send_stop()*.
>> This doesn't happen on every shutdown/reboot though.
>>
>> I did see this issue in older versions of qemu too(0.10.0 and 0.10.6).
>> This could be a minor issue for most of you but I need to fix this because I
>> run some automated scripts on the guest OS which reboots it.
>>
>> Does anybody has a fix or any other idea to get around this issue?
>>
>> Any bit of help on this would be really helpful.
>>
>> Thanks,
>> PurnaChandar M
>>
>
>

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

      reply	other threads:[~2009-12-07  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  7:03 [Qemu-devel] guest OS crash during shutdown/reboot Purna Chandar
2009-10-30  3:56 ` [Qemu-devel] " Purna Chandar
2009-12-07  9:02   ` Purna Chandar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c56848720912070102g987441rbc506f97bfe71fac@mail.gmail.com \
    --to=purnachandar.midi@oneconvergence.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).