Xen users - Jun 2011 - 64bit Windows Guest Blue Screens on install

Hi,

We have a XEN Server running on CentOS 5.5. Details are given below.

We have several guest OSs running, but we are unable to install Windows  
2008 R2. We can install any 32-bit version of Windows (Vista, 7 etc).

When we attempt the install, the process starts as normal, but when the  
process finishes loading files from the media (just before it enters GUI  
mode), it Blue Screens with a STOP message.

The XEN install is the most recent version that is available from the  
CentOS repos. I''ve tried installing directly from DVD, and from an ISO
file. I''ve also verified the installation media works on a separate
system.

Could anyone offer any advise? I''ve read that a compile-from-source may
be
required, but I''d really like to avoid that if possible, primarily
because
a V4 pre-compiled kernel from CentOS isn''t available, and I''d
have to
compile a kernel for what is one of our more critical systems.


XEN
###

host                   : vm-server
release                : 2.6.18-194.17.4.el5xen
version                : #1 SMP Mon Oct 25 16:36:31 EDT 2010
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1995
hw_caps                :  
bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001
total_memory           : 12278
free_memory            : 1042
node_to_cpu            : node0:0-1
xen_major              : 3
xen_minor              : 1
xen_extra              : .2-194.17.4.el5
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32  
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
cc_compile_by          : mockbuild
cc_compile_domain      : centos.org
cc_compile_date        : Mon Oct 25 15:40:33 EDT 2010
xend_config_format     : 2

SERVER
######

Linux vm-server 2.6.18-194.17.4.el5xen #1 SMP Mon Oct 25 16:36:31 EDT 2010  
x86_64 x86_64 x86_64 GNU/Linux

GUEST CONFIG
############

kernel = ''/usr/lib/xen/boot/hvmloader''
builder = ''hvm''
import os, re
memory = 1024
shadow_memory = 8
name = "win2008r2-01-server"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
acpi = 1
apic = 1
disk = [ ''file:/vm/win2008r2-01.img,hda,w'',  
''file:/root/iso/w2008rc2.iso,hdc:cdrom,r'' ]
device_model = ''/usr/lib64/xen/bin/qemu-dm''
boot="dc"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''''

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Jun 20, 2011 at 4:37 PM, Garreth McDaid
<garreth.mcdaid@mttnow.com> wrote:
> Hi,
>
> We have a XEN Server running on CentOS 5.5. Details are given below.
> GUEST CONFIG
> ############
>
> kernel = ''/usr/lib/xen/boot/hvmloader''
> builder = ''hvm''
> import os, re
> memory = 1024
> shadow_memory = 8
> name = "win2008r2-01-server"
> vif = [ ''type=ioemu, bridge=xenbr0'' ]
dump "type=ioemu", you don''t need it. You SHOULD add a
"mac=xxxxx"
part though. Otherwise weird things can happen (like windows keep
saying it''s not activated no matter what you do)
> acpi = 1
> apic = 1
you need "pae=1" as well
> disk = [ ''file:/vm/win2008r2-01.img,hda,w'',
> ''file:/root/iso/w2008rc2.iso,hdc:cdrom,r'' ]
don''t use "file:/". Use "tap:aio:/"
> device_model = ''/usr/lib64/xen/bin/qemu-dm''
> boot="dc"
> sdl=0
> vnc=1
> vncconsole=1
> vncpasswd=''''
I''d usually dump "vncconsole=1". Better use "xm
vncviewer" manually later.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thanks. Tried those changes, but no change in behavior. It still Blue  
Screens.

G

On Mon, 20 Jun 2011 10:46:14 +0100, Fajar A. Nugraha <list@fajar.net>  
wrote:
> On Mon, Jun 20, 2011 at 4:37 PM, Garreth McDaid
> <garreth.mcdaid@mttnow.com> wrote:
>> Hi,
>>
>> We have a XEN Server running on CentOS 5.5. Details are given below.
>
>
>> GUEST CONFIG
>> ############
>>
>> kernel = ''/usr/lib/xen/boot/hvmloader''
>> builder = ''hvm''
>> import os, re
>> memory = 1024
>> shadow_memory = 8
>> name = "win2008r2-01-server"
>> vif = [ ''type=ioemu, bridge=xenbr0'' ]
>
> dump "type=ioemu", you don''t need it. You SHOULD add a
"mac=xxxxx"
> part though. Otherwise weird things can happen (like windows keep
> saying it''s not activated no matter what you do)
>
>> acpi = 1
>> apic = 1
>
> you need "pae=1" as well
>
>> disk = [ ''file:/vm/win2008r2-01.img,hda,w'',
>> ''file:/root/iso/w2008rc2.iso,hdc:cdrom,r'' ]
>
> don''t use "file:/". Use "tap:aio:/"
>
>> device_model = ''/usr/lib64/xen/bin/qemu-dm''
>> boot="dc"
>> sdl=0
>> vnc=1
>> vncconsole=1
>> vncpasswd=''''
>
> I''d usually dump "vncconsole=1". Better use "xm
vncviewer" manually
> later.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 20/06/2011 11:47, Garreth McDaid wrote:
> Thanks. Tried those changes, but no change in behavior. It still Blue 
> Screens.
>
> G
>
> On Mon, 20 Jun 2011 10:46:14 +0100, Fajar A. Nugraha <list@fajar.net>
> wrote:
>
>> On Mon, Jun 20, 2011 at 4:37 PM, Garreth McDaid
>> <garreth.mcdaid@mttnow.com> wrote:
>>> Hi,
>>>
>>> We have a XEN Server running on CentOS 5.5. Details are given
below.
>>
>>
>>> GUEST CONFIG
>>> ############
>>>
>>> kernel = ''/usr/lib/xen/boot/hvmloader''
>>> builder = ''hvm''
>>> import os, re
>>> memory = 1024
>>> shadow_memory = 8
>>> name = "win2008r2-01-server"
>>> vif = [ ''type=ioemu, bridge=xenbr0'' ]
>>
>> dump "type=ioemu", you don''t need it. You SHOULD add
a "mac=xxxxx"
>> part though. Otherwise weird things can happen (like windows keep
>> saying it''s not activated no matter what you do)
>>
>>> acpi = 1
>>> apic = 1
>>
>> you need "pae=1" as well
>>
>>> disk = [ ''file:/vm/win2008r2-01.img,hda,w'',
>>> ''file:/root/iso/w2008rc2.iso,hdc:cdrom,r'' ]
>>
>> don''t use "file:/". Use "tap:aio:/"
>>
>>> device_model = ''/usr/lib64/xen/bin/qemu-dm''
>>> boot="dc"
>>> sdl=0
>>> vnc=1
>>> vncconsole=1
>>> vncpasswd=''''
>>
>> I''d usually dump "vncconsole=1". Better use "xm
vncviewer" manually
>> later.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
I had a similar problem, and the way I fixed it was I re-downloaded the 
ISO, so it may of just been bad media for me.

With the Technet/MSDN ISO and the official OEM DVD I was getting BSOD 
just like you, after it loaded files, prior to GUI with STOP message 
"bad_system_config_info".

However I downloaded the evaluation ISO at 
http://download.microsoft.com/download/7/5/E/75EC4E54-5B02-42D6-8879-D8D3A25FBEF7/7601.17514.101119-1850_x64fre_server_eval_en-us-GRMSXEVAL_EN_DVD.iso
and it worked fine, and activated with my OEM key.

YMMV HTH

-- 
May the ping be with you ..


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> I had a similar problem, and the way I fixed it was I re-downloaded the  
> ISO, so it may of just been bad media for me.
>
> With the Technet/MSDN ISO and the official OEM DVD I was getting BSOD  
> just like you, after it loaded files, prior to GUI with STOP message  
> "bad_system_config_info".
>
> However I downloaded the evaluation ISO at  
>
http://download.microsoft.com/download/7/5/E/75EC4E54-5B02-42D6-8879-D8D3A25FBEF7/7601.17514.101119-1850_x64fre_server_eval_en-us-GRMSXEVAL_EN_DVD.iso
> and it worked fine, and activated with my OEM key.
>
I''m actually using the downloadable eval ISO. I''ve burned it
on to a DVD
and tested it on another system, and it works fine.

My gut tells me its something to do with graphics. The Blue Screen kicks  
in just as the GUI starts.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Jun 20, 2011 at 6:24 PM, Garreth McDaid
<garreth.mcdaid@mttnow.com> wrote:
>> I had a similar problem, and the way I fixed it was I re-downloaded the
>> ISO, so it may of just been bad media for me.
>>
>> With the Technet/MSDN ISO and the official OEM DVD I was getting BSOD
just
>> like you, after it loaded files, prior to GUI with STOP message
>> "bad_system_config_info".
>>
>> However I downloaded the evaluation ISO at
>>
http://download.microsoft.com/download/7/5/E/75EC4E54-5B02-42D6-8879-D8D3A25FBEF7/7601.17514.101119-1850_x64fre_server_eval_en-us-GRMSXEVAL_EN_DVD.iso
>> and it worked fine, and activated with my OEM key.
>>
>
> I''m actually using the downloadable eval ISO. I''ve burned
it on to a DVD and
> tested it on another system, and it works fine.
>
> My gut tells me its something to do with graphics. The Blue Screen kicks in
> just as the GUI starts.
What is the text after the STOP message?

You can try adding "stdvga=0" and see if it matters.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> What is the text after the STOP message?
>
No message. Just STOP, and 2 lines of digits.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Jun 20, 2011 at 7:35 PM, Garreth McDaid
<garreth.mcdaid@mttnow.com> wrote:
>> What is the text after the STOP message?
>>
>
> No message. Just STOP, and 2 lines of digits.
>
Let me rephrase that.

What are the numbers after STOP? is it 0x0000007B? Is it something else?

The numbers really matter, you know. It''s not there just for
decoration.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> What are the numbers after STOP? is it 0x0000007B? Is it something else?
>
Its 0x0000005D

Which I think it the standard Windows Error when you try and run a 64bit  
OS on a 32bit CPU

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Jun 20, 2011 at 7:43 PM, Garreth McDaid
<garreth.mcdaid@mttnow.com> wrote:
>> What are the numbers after STOP? is it 0x0000007B? Is it something
else?
>>
>
> Its 0x0000005D
>
> Which I think it the standard Windows Error when you try and run a 64bit OS
> on a 32bit CPU

Are you SURE you have set ALL acpi, apic, and pae to 1?

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

>
> Are you SURE you have set ALL acpi, apic, and pae to 1?
>
Yes. Here''s my conf file:

kernel = ''/usr/lib/xen/boot/hvmloader''
builder = ''hvm''
import os, re
memory = 1024
shadow_memory = 8
name = "win2008r2-01-server"
vif = [ ''bridge=xenbr0'' ]
acpi = 1
apic = 1
pae = 1
disk = [ ''file:/vm/win2008r2-01.img,hda,w'',  
''tap:aio:/root/iso/w2008rc2.iso,hdc:cdrom,r'' ]
device_model = ''/usr/lib64/xen/bin/qemu-dm''
boot="dc"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''''

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> > What are the numbers after STOP? is it 0x0000007B? Is it something
else?
> >
> 
> Its 0x0000005D
> 
> Which I think it the standard Windows Error when you try and run a 64bit
> OS on a 32bit CPU
> 
That would be one reason. 0x5D is "UNSUPPORTED_PROCESSOR" so it could
be a number of things but a lack of 64 bit support is probably most likely.

Does 64 bit Linux work?

What is Dom0?

Cat you post the output of both 'xm info' and 'cat
/proc/cpuinfo'?

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Does 64 bit Linux work?
Yes
>
> What is Dom0?
Linux vm-server 2.6.18-194.17.4.el5xen #1 SMP Mon Oct 25 16:36:31 EDT 2010  
x86_64 x86_64 x86_64 GNU/Linux

CentOS release 5.5 (Final)
Kernel \r on an \m
>
> Cat you post the output of both ''xm info'' and
''cat /proc/cpuinfo''?

host                   : vm-server
release                : 2.6.18-194.17.4.el5xen
version                : #1 SMP Mon Oct 25 16:36:31 EDT 2010
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1995
hw_caps                :  
bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001
total_memory           : 12278
free_memory            : 1
node_to_cpu            : node0:0-1
xen_major              : 3
xen_minor              : 1
xen_extra              : .2-194.17.4.el5
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32  
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
cc_compile_by          : mockbuild
cc_compile_domain      : centos.org
cc_compile_date        : Mon Oct 25 15:40:33 EDT 2010
xend_config_format     : 2


processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 26
model name	: Intel(R) Xeon(R) CPU           E5503  @ 2.00GHz
stepping	: 5
cpu MHz		: 1994.999
cache size	: 4096 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 11
wp		: yes
flags		: fpu tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse  
sse2 ss ht syscall nx lm constant_tsc pni vmx est ssse3 cx16 sse4_1 sse4_2  
popcnt lahf_lm
bogomips	: 4988.82
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 26
model name	: Intel(R) Xeon(R) CPU           E5503  @ 2.00GHz
stepping	: 5
cpu MHz		: 1994.999
cache size	: 4096 KB
physical id	: 1
siblings	: 1
core id		: 0
cpu cores	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 11
wp		: yes
flags		: fpu tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse  
sse2 ss ht syscall nx lm constant_tsc pni vmx est ssse3 cx16 sse4_1 sse4_2  
popcnt lahf_lm
bogomips	: 4988.82
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:

>
> James
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> xen_major              : 3
> xen_minor              : 1
> xen_extra              : .2-194.17.4.el5
That's pretty old. You might be able to fudge support via cpuid entries in
your config but I strongly suggest running a newer version of xen.

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> That''s pretty old. You might be able to fudge support via cpuid
entries
> in your config but I strongly suggest running a newer version of xen.
>
Its a CentOS RPM, so the major version isn''t actually the major
version,
as all updates after that major release are backported into the RPM.

The most recent version of the RPM is 2.6.18-194.32.1.el5xen, which
I''ve
also tested with, but the behavior is the same.

In my OP, I noted that compiling-from-source was an option I wanted to  
avoid, as it involves compiling a new kernel on a mission critical server.

Garreth

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

You can use the GITCO repository (http://www.gitco.de/repo/) for newer versions
of Xen (e.g. the proven 3.4.3). It''s quite popular among CentOS users.
:)

Regards

Matej
________________________________________
From: xen-users-bounces@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of Garreth McDaid
[garreth.mcdaid@mttnow.com]
Sent: 20 June 2011 16:25
To: Fajar A. Nugraha; James Harper
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] 64bit Windows Guest Blue Screens on install
> That''s pretty old. You might be able to fudge support via cpuid
entries
> in your config but I strongly suggest running a newer version of xen.
>
Its a CentOS RPM, so the major version isn''t actually the major
version,
as all updates after that major release are backported into the RPM.

The most recent version of the RPM is 2.6.18-194.32.1.el5xen, which
I''ve
also tested with, but the behavior is the same.

In my OP, I noted that compiling-from-source was an option I wanted to
avoid, as it involves compiling a new kernel on a mission critical server.

Garreth

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> You can use the GITCO repository (http://www.gitco.de/repo/) for newer  
> versions of Xen (e.g. the proven 3.4.3). It''s quite popular among
CentOS
> users. :)
Yeah, that might work, *if* my current kernel is compatible with 3.4.3.

Also, its hard to tell if those rpms contain newer/older code than the  
CentOS el5 backport.

Will give it a whirl and update accordingly.

I still think its something to do with my config, however. No else appears  
to be having problems with 64-bit Windows.

Thx
>
> Regards
>
> Matej
> ________________________________________
> From: xen-users-bounces@lists.xensource.com  
> [xen-users-bounces@lists.xensource.com] On Behalf Of Garreth McDaid  
> [garreth.mcdaid@mttnow.com]
> Sent: 20 June 2011 16:25
> To: Fajar A. Nugraha; James Harper
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] 64bit Windows Guest Blue Screens on install
>
>> That''s pretty old. You might be able to fudge support via
cpuid entries
>> in your config but I strongly suggest running a newer version of xen.
>>
>
> Its a CentOS RPM, so the major version isn''t actually the major
version,
> as all updates after that major release are backported into the RPM.
>
> The most recent version of the RPM is 2.6.18-194.32.1.el5xen, which
I''ve
> also tested with, but the behavior is the same.
>
> In my OP, I noted that compiling-from-source was an option I wanted to
> avoid, as it involves compiling a new kernel on a mission critical  
> server.
>
> Garreth
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

-- 
Operations Support
Mobile Travel Technologies

Dublin HQ
Digital Court
Rainsford Street
The Digital Hub
Dublin 8
Ireland

Tel: 01 485 3452 (Intl: +353 1 485 3452)
Mobile Intl: +353 87 688 5867
Email: garreth.mcdaid@mttnow.com
Web: www.mttnow.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users