From: "Марк Коренберг" <socketpair@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] The linux-based system runs perfectly on vmware, but kernel panic on qemu
Date: Thu, 17 Jan 2008 16:50:33 +0500 [thread overview]
Message-ID: <b8f627e0801170350w5599a9a9nb5cdcb787200f442@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hello developers.
I'm developer of ideco software product (www.ideco-software.ru)
and our products is run perfectly on vmware, but strange behaviour in qemu.
I have qemu 0.9.0 for windows with kqemu accelerator used.
i have screenshots attached. I think race condition somewhere, as the
the bug appear in different places.
The scr01.bmp - string " === qwe ===" is specially inserted in script
just before
/sbin/hwclock --localtime --hctosys
command after which kernel panic occurs.
If i test this command just after kernel booting - it works fine.
Also. our kernel doesn't support modules.
The scr202.bmp appear when md5 check of our system scripts failed (as
the string "===qwe===" inserted by me) and bash asks user to confirm
booting:
read answer
if [ "$answer" = "yes" ]; then ........
so i have no idea why kernel panic occurs.
PLEASE contact with me by email socketpair@gmail.com.
I can not use maillists and can not use kernel debugger.
Thanks.
--
Segmentation fault
[-- Attachment #2: scr.zip --]
[-- Type: application/zip, Size: 26118 bytes --]
next reply other threads:[~2008-01-17 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 11:50 Марк Коренберг [this message]
2008-01-18 2:21 ` [Qemu-devel] The linux-based system runs perfectly on vmware, but kernel panic on qemu Mulyadi Santosa
[not found] ` <b8f627e0801180210h6abce895yeede4f9950534dc@mail.gmail.com>
2008-01-18 10:17 ` Mulyadi Santosa
[not found] ` <b8f627e0801180301o23b07c89pcf08717f2450dcf4@mail.gmail.com>
2008-01-18 11:14 ` Mulyadi Santosa
[not found] ` <b8f627e0801180339y390ba860rb05b6fde5bb6502b@mail.gmail.com>
2008-01-18 12:22 ` Mulyadi Santosa
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=b8f627e0801170350w5599a9a9nb5cdcb787200f442@mail.gmail.com \
--to=socketpair@gmail.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).