Re: KVM-29 + Windows Server 2003 = kernel panic

[Alessandro Sardo <sandro.sardo-8RLafaVCWuNeoWH0uzbU5w@public.gmane.org>]

Hello,

I have tried what you suggested but I could not reproduce the problem 
anymore with KVM-32... guess it could have been fixed somewhere in 
between the new releases. However, I am noticing two new issues:

1) rebooting the guest never works

2) I *very* often get BSODs as the one I sent as attachment, mainly 
immediately after logon - with and without the "-smp 2" flag

Just to remind you all,

* CPU model: 2 x Dual-Core AMD Opteron Processor 2210
* KVM versions: KVM-32
* Host: RHEL5 x86_64, kernel 2.6.18-8.1.8.el5
* Guest: Windows Server 2003 Standard edition
* qemu command line: "kvm -hda VM.img -cdrom Win2003.iso -boot c -net
nic,model=rtl8139,macaddr=00:01:02:1E:77:96 -net
tap,script=/etc/kvm/qemu-ifup -m 1024 -smp 2 -daemonize -usb -usbdevice
tablet -vnc :1"

Please let me know if I can help in any way, thanks.

AS


Avi Kivity ha scritto:
> Alessandro Sardo wrote:
>>>
>>> Can you generate a cleaner (more readable) oops, for example by 
>>> using netconsole?
>>>
>> Hi Avi,
>>
>> would you be so kind to tell me how to do it? I have tried running 
>> KVM on the server with:
>>
>> # sudo -u kvm qemu-system-x86_64 -hda VM.img -cdrom Win2003.iso -boot 
>> d -net nic,model=rtl8139 -net tap,ifname=tap0,fd=h,script=no -m 1024 
>> -no-acpi -daemonize -usb -usbdevice tablet -vnc :1 -serial 
>> udp:<client IP>:6666
>>
>
> This redirects the guest console, not the host console.
>
>> and running nc on the client with:
>>
>> # nc -u -l -p 6666
>>
>> but all I got was this:
>>
>> kvm: emulating exchange as write
>> kvm[2865]: segfault at 00002aaaec84d000 rip 000000000046dad9 rsp 
>> 00007fffec682640 error 4
>>
>
> I use somthing like:
>
> /sbin/modprobe netconsole 
> netconsole=@10.0.11.54/eth0,10054-2+4ijDgkSvM@public.gmane.org/00:E0:81:2B:0C:C1
>
> Where:
>  10.0.11.54 == host IP address
>  10054 == udp port number
>  10.0.0.1 == logger ip address
>  00:E0:81:2B:0C:C1 == logger mac address
>
> On the logger, I run
>
>  nc -uld 10054


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