From: "SourceForge.net" <noreply-pyega4qmqnRoyOMFzWx49A@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [ kvm-Bugs-1795722 ] 64bit windows guest works on intel but not amd
Date: Sun, 16 Sep 2007 04:02:29 -0700 [thread overview]
Message-ID: <E1IWrtV-000892-8P@sc8-sf-web22.sourceforge.net> (raw)
Bugs item #1795722, was opened at 2007-09-16 11:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1795722&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: Alex Moore (lightspd10)
Assigned to: Nobody/Anonymous (nobody)
Summary: 64bit windows guest works on intel but not amd
Initial Comment:
I noticed that the release notes for kvm-36 mentioned the addition of support for 64-bit windows guests, which is the feature I have been waiting for.
It does indeed work nicely on my Intel desktop machine (a Core 2 Extreme QX6700). But not on my AMD based server (an Opteron 2210).
When attempting to boot the 64-bit Windows guest on the Opteron, the guest bluescreens immediately. This occurs both when trying to boot the Windows installation CD and also when trying to boot the already-installed OS, having copied the disk image over from the Intel host. The Windows OS I'm using is Windows Server 2003 x64 Edition.
I then upgraded to the latest kvm release (kvm-39), but the problem remains.
Note that both the Intel and AMD host machines are using kernel 2.6.22 (64-bit), and in both cases I am using the kernel modules provided by the kvm package, not the ones available in the kernel itself.
This problem does NOT occur if I add the -no-kvm option to the command line on the AMD64 host (ie the guest then boots successfully).
P.S. I didn't see any info on "-no-kvm" in the man page... what am I missing out on if I run it with that switch?
Alex
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1795722&group_id=180599
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
reply other threads:[~2007-09-16 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1IWrtV-000892-8P@sc8-sf-web22.sourceforge.net \
--to=noreply-pyega4qmqnroyomfzwx49a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox