From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2001121 ] Windows 2003 x64 - SESSION5_INITIALIZATION_FAILED
Date: Fri, 09 Jan 2009 15:02:33 +0000 [thread overview]
Message-ID: <E1LLIsb-0000ui-D8@155xhf1.ch3.sourceforge.com> (raw)
Bugs item #2001121, was opened at 2008-06-23 21:09
Message generated for change (Comment added) made by masc82
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2001121&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: intel
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andreas 'ac0v' Specht (ac0v)
Assigned to: Nobody/Anonymous (nobody)
Summary: Windows 2003 x64 - SESSION5_INITIALIZATION_FAILED
Initial Comment:
Host Machine:
CPU: 2x Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
Kernel: Linux version 2.6.25-gentoo-r4
Arch: x86_64
KVM: tried kvm-69 and kvm-70
Guest System:
tried Windows 2003 x64 and Windows 2003 x64 with slipstreamed Service Pack 2
Hi,
I get a BSoD (see attachment) while installing Windows 2003 x64 which contains the error message SESSION5_INITIALIZATION_FAILED
Serial log is empty.
I start my KVM via this command:
kvm -hda /dev/lvg1/sap-test -boot d -cdrom /srv/install/iso/windows/2003-server-x64.iso -vnc :4 -m 3048 -smp 4 -daemonize
Using -no-kvm or the -no-kvm-pit switch doesn't help and shows only the message "Setup is starting Windows".
The -no-kvm-irqchip switch has no effect (same BSoD).
Any Ideas?
Regards,
Andreas 'ac0v' Specht
----------------------------------------------------------------------
Comment By: MaSc82 (masc82)
Date: 2009-01-09 16:02
Message:
The issue persists with kvm-82 modules. Neither win2003 x64 r2 CD nor
installed system will boot, failing with BSOD
SESSION5_INITIALIZATION_FAILED. Had to revert to older 2.6.28 modules
having block virtio disabled again :(
----------------------------------------------------------------------
Comment By: MaSc82 (masc82)
Date: 2008-12-25 17:35
Message:
Updated to 2.6.28 including kvm modules, which seem to work very well with
kvm81, at the same time supporting win2003 x64, so all mentioned issues are
resolved for me, but only when using the kvm modules of linux kernel
2.6.28.
----------------------------------------------------------------------
Comment By: MaSc82 (masc82)
Date: 2008-12-22 16:58
Message:
I've got the same issue with kvm-81 and Linux version 2.6.27-gentoo-r7.
The problem does not occur when using the kvm modules coming with the
kernel, but these (probably older?) modules still have bugs with smp and
block device virtio (temporary freeze)..
Can anyone shed some light on this, please?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2001121&group_id=180599
next reply other threads:[~2009-01-09 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 15:02 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-25 13:32 [ kvm-Bugs-2001121 ] Windows 2003 x64 - SESSION5_INITIALIZATION_FAILED SourceForge.net
2008-12-25 16:35 SourceForge.net
2008-12-22 15:58 SourceForge.net
2008-06-23 21:33 SourceForge.net
2008-06-23 19:09 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=E1LLIsb-0000ui-D8@155xhf1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox