public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2702210 ] -cpu core2duo still crashes linux guests under kvm-84
Date: Tue, 24 Mar 2009 10:48:22 +0000	[thread overview]
Message-ID: <E1Lm4BC-0002CC-GG@d55xhf1.ch3.sourceforge.com> (raw)

Bugs item #2702210, was opened at 2009-03-22 10:27
Message generated for change (Comment added) made by amitshah
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2702210&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: klondike (franxisco1988)
Assigned to: Nobody/Anonymous (nobody)
Summary: -cpu core2duo still crashes linux guests under kvm-84

Initial Comment:
Using kvm-84 and -cpu core2duo still crashes the guest.

Related bug #2413430

cpuinfo output:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz
stepping        : 6
cpu MHz         : 1862.000
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow
bogomips        : 3739.71
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz
stepping        : 6
cpu MHz         : 1862.000
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow
bogomips        : 3739.68
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

Distribution: gentoo hardened 64-bit.

----------------------------------------------------------------------

>Comment By: Amit Shah (amitshah)
Date: 2009-03-24 16:18

Message:
I can't reproduce this with the development git tree (both kernel and
userspace).

The error message you mention in the host kernel log is also quite old and
has been fixed.

Can you try the development git snapshot or a nightly build to see if this
works for you too?

I tried on a 64-bit host with the 64-bit 2008.0 gentoo live cd.

----------------------------------------------------------------------

Comment By: klondike (franxisco1988)
Date: 2009-03-22 20:18

Message:
My fault, the only reference to the crash is a 100% CPU usage for more than
15 minutes when trying to start a Gentoo 2008.0 Live CD

The last lines on the guest are:
Feeing unused kernel memory: 256k freed
input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/serio1/input2

On the host, dmesg says:
kvm: 5613: cpu0 unhandled wrmsr: 0xc0010117 data 0

And qemu outputs nothing.

----------------------------------------------------------------------

Comment By: Amit Shah (amitshah)
Date: 2009-03-22 14:12

Message:
Please give more information: the logs in host kernel related to the crash,
guest kernel output before the crash, qemu output on the host.

I tried this and it worked for me with a 64-bit Debian Lenny guest.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2702210&group_id=180599

             reply	other threads:[~2009-03-24 10:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 10:48 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-28 20:16 [ kvm-Bugs-2702210 ] -cpu core2duo still crashes linux guests under kvm-84 SourceForge.net
2009-03-22 14:48 SourceForge.net
2009-03-22  8:42 SourceForge.net
2009-03-22  4:57 SourceForge.net

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=E1Lm4BC-0002CC-GG@d55xhf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /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