Windows Server 2003 Crashes on KVM-35

Windows Server 2003 Crashes on KVM-35

[Clive Stewell]

I have been attempting to get Windows Server 2003 running under KVM and 
am having some difficulty in doing so. I have tried it on both AMD and 
Intel-based machines and it crashes on each. Below is some basic 
information about my setup followed by the output from the crashes.

=====
CPU Model: Intel Xeon 5130 2.0 Ghz
KVM Version: 35
Host Kernel: 2.6.20 (-16-generic)
Host Kernel Arch: i386
Guest: Windows Server 2003, 32 bit
QEMU Command Line: /opt/kvm/bin/qemu-system-x86_64 -hda 
/home/kvm/images.d/accntg-apps.img -boot c -m 384 -no-acpi
Problem w/-no-kvm Switch: Does not crash, but does not progress beyond 
initial black window

Output...

Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux 
kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
unhandled vm exit:  0x9
rax 00000000fffffd60 rbx 000000008089d3f4 rcx 000000008089fd80 rdx 
00000000808a414d
rsi 0000000000000001 rdi 00000000fffe00e0 rsp 000000008089d374 rbp 
000000008089d374
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
0000000000000000
rip 000000008082646a rflags 00000246
cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt 8003f000/3ff
idt 8003f400/7ff
cr0 e001003d cr2 fffe00e0 cr3 39000 cr4 0 cr8 0 efer 0


=====
CPU Model: AMD Athlon 64 X2 Dual Core 4000+
KVM Version: 35
Host Kernel: 2.6.20 (-16-generic)
Host Kernel Arch: i386
Guest: Windows Server 2003, 32 bit
QEMU Command Line: /opt/kvm/bin/qemu-system-x86_64 -hda 
/home/kvm/images.d/accntg-apps.img -boot c -m 384 -no-acpi
Problem w/-no-kvm Switch: Does not crash, but does not progress beyond 
initial black window

Output...

Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux 
kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
unhandled vm exit:  0x3f60101
rax 00000000000000ff rbx 000000008089d3f4 rcx 0000000000000001 rdx 
00000000808a414d
rsi 0000000080a78529 rdi 00000000fffe00e0 rsp 000000008089d358 rbp 
000000008089d374
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
0000000000000000
rip 00000000808760f7 rflags 00000202
cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0)
ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt 8003f000/3ff
idt 8003f400/7ff
cr0 8001003d cr2 fffe00e0 cr3 39000 cr4 0 cr8 0 efer 0


=====
Additional Information

Both systems are running Ubuntu Feisty and each is entirely current on 
its patches. When using the Ubuntu-installed tools Windows 2003 Server 
runs on the Intel box, but not the AMD box. I am attempting to run the 
newest version of KVM for its stability and performance benefits as I 
hope to use KVM in a production environment in the next few months.

In both cases the build was configured as follows:

./configure --prefix=/opt/kvm-35 --qemu-cc="/usr/bin/gcc-3.[34]"

Note that I am unclear as to when to use the --with-patched-kernel 
option (wasn't sure if this was just for when you wanted kvm baked 
directly into the kernel -- would love clarification on exactly what a 
"patched kernel" is). Nonetheless, I tried this and the build failed. I 
can provide more information if this is, in fact, what I should have 
been doing. I assume that what I did above was right as I can run Ubuntu 
Feisty as a guest without any issues whatsoever on KVM-35.

Thanks for any help you can provide.


- Clive

-------------------------------------------------------------------------
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/

Re: Windows Server 2003 Crashes on KVM-35

[Jorge Lucángeli Obes]

On 8/16/07, Clive Stewell <dba-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org> wrote:
> I have been attempting to get Windows Server 2003 running under KVM and
> am having some difficulty in doing so. I have tried it on both AMD and
> Intel-based machines and it crashes on each. Below is some basic
> information about my setup followed by the output from the crashes.
>
> =====
> Additional Information
>
> Both systems are running Ubuntu Feisty and each is entirely current on
> its patches. When using the Ubuntu-installed tools Windows 2003 Server
> runs on the Intel box, but not the AMD box.

I'm running a 32-bit Windows 2003 Server guest on a 64-bit Xubuntu
Feisty host (Core 2 Duo 5600) using kvm-35 with no problem: don't
despair, it can be done =).

> In both cases the build was configured as follows:
>
> ./configure --prefix=/opt/kvm-35 --qemu-cc="/usr/bin/gcc-3.[34]"
>
> Note that I am unclear as to when to use the --with-patched-kernel
> option (wasn't sure if this was just for when you wanted kvm baked
> directly into the kernel -- would love clarification on exactly what a
> "patched kernel" is).

--with-patched-kernel simply uses the kernel modules bundled with your
kernel (since 2.6.20) instead of using the modules bundled with the
kvm release. Most of the times, the modules bundled with the release
are newer than the ones in the kernel, with the (only?) exception of
using git repos directly (for example kvm.git).

> been doing. I assume that what I did above was right as I can run Ubuntu
> Feisty as a guest without any issues whatsoever on KVM-35.

It seems what you are doing is correct. However, try removing
'no-acpi' from your command line. Right now I'm not using 'no-acpi' on
my 2003 command line:

qemu-system-x86_64 -m 512 -no-reboot -localtime -net nic,model=rtl8139
stuff/qemu/2003.img -net user

And when I add it I get the same unhandled VM exit as you.

Cheers,
Jorge

-------------------------------------------------------------------------
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/

Re: Windows Server 2003 Crashes on KVM-35

[Clive Stewell]

Jorge -

Just wanted to drop you a message to say a belated "thanks" (been so 
busy didn't have time to check everything on both systems until 
yesterday)! Anyway, your mention that you were successfully running 
Windows Server 2003 inspired me to redouble my efforts. I did a new, 
clean installation using kvm-35 and, much to my satisfaction, it worked 
straightaway on the AMD box. I then copied the drive image over to the 
Intel box and that, too, worked without a hitch.

So, something was hosed in my original drive image. Not sure what, but 
whereas time is at a premium these days, I've already deleted them and 
am happily testing my working installation with visions of going 
production in the next couple of months.

I very much appreciate your help and (especially) the respect with which 
you treated my inquiry. Many, many thanks!

- Clive

Jorge Lucángeli Obes wrote:
> On 8/16/07, Clive Stewell <dba-hDdu9bXZKAcAvxtiuMwx3w@public.gmane.org> wrote:
>> I have been attempting to get Windows Server 2003 running under KVM and
>> am having some difficulty in doing so. I have tried it on both AMD and
>> Intel-based machines and it crashes on each. Below is some basic
>> information about my setup followed by the output from the crashes.
>>
>> =====
>> Additional Information
>>
>> Both systems are running Ubuntu Feisty and each is entirely current on
>> its patches. When using the Ubuntu-installed tools Windows 2003 Server
>> runs on the Intel box, but not the AMD box.
> 
> I'm running a 32-bit Windows 2003 Server guest on a 64-bit Xubuntu
> Feisty host (Core 2 Duo 5600) using kvm-35 with no problem: don't
> despair, it can be done =).
> 
>> In both cases the build was configured as follows:
>>
>> ./configure --prefix=/opt/kvm-35 --qemu-cc="/usr/bin/gcc-3.[34]"
>>
>> Note that I am unclear as to when to use the --with-patched-kernel
>> option (wasn't sure if this was just for when you wanted kvm baked
>> directly into the kernel -- would love clarification on exactly what a
>> "patched kernel" is).
> 
> --with-patched-kernel simply uses the kernel modules bundled with your
> kernel (since 2.6.20) instead of using the modules bundled with the
> kvm release. Most of the times, the modules bundled with the release
> are newer than the ones in the kernel, with the (only?) exception of
> using git repos directly (for example kvm.git).
> 
>> been doing. I assume that what I did above was right as I can run Ubuntu
>> Feisty as a guest without any issues whatsoever on KVM-35.
> 
> It seems what you are doing is correct. However, try removing
> 'no-acpi' from your command line. Right now I'm not using 'no-acpi' on
> my 2003 command line:
> 
> qemu-system-x86_64 -m 512 -no-reboot -localtime -net nic,model=rtl8139
> stuff/qemu/2003.img -net user
> 
> And when I add it I get the same unhandled VM exit as you.
> 
> Cheers,
> Jorge
> 


-------------------------------------------------------------------------
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/