All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2932002 ] Blue screen  BAD_POOL_HEADER windows 2k8 over kvm
Date: Thu, 14 Jan 2010 13:30:20 +0000	[thread overview]
Message-ID: <E1NVPmG-00089e-Rt@565xhf1.ch3.sourceforge.com> (raw)

Bugs item #2932002, was opened at 2010-01-14 13:10
Message generated for change (Comment added) made by loumy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2932002&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: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Cyril (loumy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Blue screen  BAD_POOL_HEADER windows 2k8 over kvm

Initial Comment:
I have lots of blue screen on a guest windows 2k8 R2 (6.1 N 7600) runing in virtual machine powered by Kvm on CentOS 5.3 x86_64.
I think it's about a virtual driver. I join two problem, one on loading driver CPU QEMU Virtual CPU version 0.9.1 and one about the blue screen.

I can give more details on demande.

Version is 83, Release : 105.el5_4.13. DOm 0 kernel is : 2.6.18-164.9.1.el5 #1 SMP Tue Dec 15 20:57:57 EST 2009 x86_64 x86_64 x86_64 GNU/Linux.
Hw physique:
2x Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz (quad core)
6go
Hw Guest :
1x Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz(quad core)
2go


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

Comment By: Cyril (loumy)
Date: 2010-01-14 14:30

Message:
thanks for your answer

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

Comment By: Avi Kivity (avik)
Date: 2010-01-14 13:34

Message:
This was fixed in kvm-kmod-2.6.32.3.

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

Comment By: Cyril (loumy)
Date: 2010-01-14 13:16

Message:
I so sorry, I didn't write hte 

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

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

             reply	other threads:[~2010-01-14 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 13:30 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-24 13:23 [ kvm-Bugs-2932002 ] Blue screen BAD_POOL_HEADER windows 2k8 over kvm SourceForge.net
2010-01-14 12:34 SourceForge.net
2010-01-14 12:16 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=E1NVPmG-00089e-Rt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.