From: Tony Smolar <tony.smolar-H+0wwilmMs3R7s880joybQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: problem upgrading to kvm-33
Date: Fri, 10 Aug 2007 23:18:41 -0400 [thread overview]
Message-ID: <46BD2A91.6010106@verizon.net> (raw)
Hi, I was currently using kvm-24, and I decided to try to upgrade to
the latest.
My guest is XP-SP2 Home full edition. When I tried to boot it under
kvm-33, I eventually got a blue screen and a IRQL_NOT_LESS_OR_EQUAL error.
I removed 33, and installed kvm-26. I was able to boot the VM
successfully with that. So I guess this problem was introduced
somewhere between 27 and 33. Is there a way to tweak the guest to get
around this problem?
Thanks,
Tony Smolar
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-08-11 3:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 3:18 Tony Smolar [this message]
[not found] ` <46BD2A91.6010106-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2007-08-12 15:52 ` problem upgrading to kvm-33 Amit Shah
[not found] ` <200708122122.13947.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-12 17:19 ` Tony Smolar
2007-08-12 20:03 ` Izik Eidus
[not found] ` <46BF4139.3040100-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2007-08-12 21:13 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D2413DB-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-13 0:56 ` Tony Smolar
2007-08-14 2:01 ` Tony Smolar
[not found] ` <46C10D0C.9080509-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2007-08-19 8:53 ` Avi Kivity
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=46BD2A91.6010106@verizon.net \
--to=tony.smolar-h+0wwilmms3r7s880joybq@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.