From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 40872] windows XP Guest node crashes using kvm-86
Date: Wed, 10 Aug 2011 16:45:55 GMT [thread overview]
Message-ID: <201108101645.p7AGjtXI023067@demeter2.kernel.org> (raw)
In-Reply-To: <bug-40872-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=40872
Avi Kivity <avi@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |avi@redhat.com
AssignedTo|virtualization_kvm@kernel-b |avi@redhat.com
|ugs.osdl.org |
Status|NEW |RESOLVED
Resolution| |OBSOLETE
--- Comment #1 from Avi Kivity <avi@redhat.com> 2011-08-10 16:45:55 ---
kvm-86 is no longer supported. Please try a recent kernel like Linux 3.0. If
you're using RHEL, use RHEL's KVM and report bugs through Red Hat bugzilla.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2011-08-10 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 16:40 [Bug 40872] New: windows XP Guest node crashes using kvm-86 bugzilla-daemon
2011-08-10 16:45 ` bugzilla-daemon [this message]
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=201108101645.p7AGjtXI023067@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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