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-2912026 ] kvm87 crash on fedora 10
Date: Thu, 10 Dec 2009 14:31:50 +0000	[thread overview]
Message-ID: <E1NIk3a-0002kN-Eu@565xhf1.ch3.sourceforge.com> (raw)

Bugs item #2912026, was opened at 2009-12-10 23:31
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2912026&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: kvm87 crash on fedora 10

Initial Comment:
kvm keeps crashing. Sometimes right away, sometimes several seconds after start. dmesg gives:

vmwrite error: reg 6c00 value 80050033 (err 27648)
Pid: 4545, comm: qemu Not tainted 2.6.27.25-170.2.72.fc10.i686.PAE #1
 [<c06b5884>] ? printk+0xf/0x13
 [<f910e4cd>] vmwrite_error+0x25/0x2f [kvm_intel]
 [<f910e4f7>] vmcs_writel+0x20/0x24 [kvm_intel]
 [<f910e7eb>] vmx_vcpu_run+0x1e/0x196 [kvm_intel]
 [<f90821c1>] kvm_arch_vcpu_ioctl_run+0x3dc/0x5ee [kvm]
 [<f907c3af>] kvm_vcpu_ioctl+0xfe/0x3da [kvm]
 [<c04292da>] ? enqueue_entity+0x203/0x20b
 [<c0424848>] ? resched_task+0x3a/0x6e
 [<c042b546>] ? check_preempt_wakeup+0x1bb/0x1c3
 [<c06b76eb>] ? _spin_unlock_irqrestore+0x22/0x38
 [<c042d1c9>] ? try_to_wake_up+0x230/0x23b
 [<c042d1df>] ? default_wake_function+0xb/0xd
 [<c042594e>] ? __wake_up_common+0x35/0x5b
 [<c0426f63>] ? __wake_up+0x31/0x3b
 [<c044dad4>] ? wake_futex+0x1f/0x2c
 [<c044db9d>] ? futex_wake+0xbc/0xc6
 [<c042752b>] ? __dequeue_entity+0x73/0x7b
 [<c04275be>] ? set_next_entity+0x8b/0xf7
 [<f907d901>] ? kvm_vm_ioctl+0x1db/0x1ee [kvm]
 [<c042fff7>] ? finish_task_switch+0x2f/0xb0
 [<c06b60c7>] ? schedule+0x6ee/0x70d
 [<f907c2b1>] ? kvm_vcpu_ioctl+0x0/0x3da [kvm]
 [<c04a2a16>] vfs_ioctl+0x22/0x69
 [<c04a2c98>] do_vfs_ioctl+0x23b/0x247
 [<c0466d4e>] ? audit_syscall_entry+0xf9/0x123
 [<c04a2ce4>] sys_ioctl+0x40/0x5c
 [<c0408c8a>] syscall_call+0x7/0xb
 =======================

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

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

             reply	other threads:[~2009-12-10 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 14:31 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-10 16:29 [ kvm-Bugs-2912026 ] kvm87 crash on fedora 10 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=E1NIk3a-0002kN-Eu@565xhf1.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