From: John Lenz <jlenz2@math.uiuc.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Testing Report for Xen 3.0.3 rc1
Date: Sat, 30 Sep 2006 01:45:08 -0500 [thread overview]
Message-ID: <451E1274.4080300@math.uiuc.edu> (raw)
In-Reply-To: <914147B2EBD9E04EBB210628A437950802669E@pdsmsx404.ccr.corp.intel.com>
On 09/29/06 02:51, Xu, JiajunX wrote:
>
> 3. Win2k installation with ACPI enabled will give a blue screen.
>
> It also exists in latest unstable tree. Xin also met the issue. As we
> begin add more combination Windows tests, it's important to make it
> work.
>
The latest ReactOS 0.3.0 in a hvm domain also bluescreens during the
first boot. The install from the CD works fine, but after rebooting
from the hard drive, bluescreen shows up with a message about
bootvid.sys KMODE_EXCEPTION_NOT_HANDLED. I have a screenshot if anyone
is interested (14K). This is with ACPI=0, so is probably unrelated.
This is on a AMD Athlon 64 X2 with the latest xen 3.0.3 rc1 binary
release (I didn't compile it myself).
Other problems I had:
1) Installing Windows 2000 blue screened, but after installing with
qemu, xen boots a domU into Windows 2000 fine
2) Upgrading WinXP from the Windows 2000 again bluscreened during the
install, but after installing with qemu, the WinXP domain boots up fine.
3) The mouse in windows "feels" a lot slower than the old xen (3.0.2).
I don't know if this is related to bvt vs credit or what, and I don't
have any measures or anything, but mouse movement in both SDL and VNC
seem slower to update the mouse position when you move it. This is with
an idle dom0, and just WinXP in the domU, and both show no CPU use.
John
next prev parent reply other threads:[~2006-09-30 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 7:51 Testing Report for Xen 3.0.3 rc1 Xu, JiajunX
2006-09-29 14:19 ` Steven Smith
2006-09-30 6:45 ` John Lenz [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-30 3:29 Xu, JiajunX
2006-09-30 8:54 ` Ian Pratt
2006-10-02 12:49 ` Steven Smith
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=451E1274.4080300@math.uiuc.edu \
--to=jlenz2@math.uiuc.edu \
--cc=xen-devel@lists.xensource.com \
/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.