From: "R. Armiento" <reply-2006@armiento.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Pentium D with guest Ubuntu 6.06 server kernel panic with kqemu
Date: Thu, 06 Jul 2006 17:13:46 +0200 [thread overview]
Message-ID: <44AD28AA.7050301@armiento.net> (raw)
Hi,
Thanks to everyone involved in the qemu project, it is great software.
I have some issues with kqemu in kernel mode;
Host is running qemu-0.8.1 or qemu-cvs-2006-07-05_23, and
kqemu-1.3.0pre9. Host OS is Ubuntu 6.06 server.
To reproduce: Start qemu as:
qemu -kernel-kqemu -cdrom ubuntu-6.06-server-i386.iso -hda test.img
-boot d
select 'Install to the hard disk'. Output is as follows:
------------------------------
Uncompressing Linux... Ok, booting the kernel
ACPI: Unable to locate RSDP
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Invalid operand: 0000 [#1]
PREEMPT
Modules linked in:
CPU 0
EIP: 0060:[<c01011c6>] Not tainted VLI
EFLAGS: 00010246 (2.6.15-23-386)
EIP is at mwait_idle+0x16/0x30
[... register dump, etc ...]
<0>Kernel panic - not syncing: Attempted to kill the id
-----------------------------
Running qemu without '-kernel-kqemu' OR booting the guest install cd
with kernel option 'idle=poll' or 'idle=halt' avoids the kernel panic.
(idle=halt is much faster than idle=poll, though).
The error looks very similar to the one reported here:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg03964.html
But I believe that reported issue should not appear in recent qemu,
since SSE3 is now emulated (right?). (At least the patch in the end of
that thread seems to already be included in the sources?)
So, my hypothesis is that there is some other feature that appears in my
host CPUID, which the booting linux image tries to make use of, but
which qemu does not emulate.
The host CPU is a dual-core Pentium D. Here is relevant lines from
/proc/cpuinfo:
------------------------------
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 3.00GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
pni monitor ds_cpl vmx est cid cx16 xtpr lahf_lm
-----------------------------
Any ideas?
Best regards,
Rickard
http://www.dewmill.com
next reply other threads:[~2006-07-06 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 15:13 R. Armiento [this message]
2006-07-07 9:06 ` [Qemu-devel] Pentium D with guest Ubuntu 6.06 server kernel panic with kqemu Joachim Henke
2006-07-07 9:39 ` Jens Axboe
2006-07-07 13:39 ` R. Armiento
2006-07-07 12:30 ` [Qemu-devel] [PATCH] add 'monitor' and 'mwait' instruction Joachim Henke
2006-07-07 12:57 ` maestro
2006-07-07 13:22 ` Joachim Henke
2006-07-07 15:21 ` Joachim Henke
2006-07-07 13:18 ` [Qemu-devel] [PATCH] add 'monitor' and 'mwait' instruction (update) Joachim Henke
2006-07-07 13:20 ` Joachim Henke
2006-07-08 13:16 ` R. Armiento
2006-07-08 15:01 ` [Qemu-devel] " Joachim Henke
2006-07-08 20:50 ` R. Armiento
2006-07-09 8:54 ` Joachim Henke
2006-07-09 13:20 ` R. Armiento
2006-07-09 11:30 ` Paul Brook
2006-07-09 15:25 ` Jamie Lokier
2006-07-09 13:03 ` [Qemu-devel] 'monitor' and 'mwait' instruction Joachim Henke
2006-07-09 15:21 ` [Qemu-devel] add 'monitor' and 'mwait' instruction (update) Jamie Lokier
2006-07-09 15:11 ` Jamie Lokier
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=44AD28AA.7050301@armiento.net \
--to=reply-2006@armiento.net \
--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).