Red Hat Bugzilla – Bug 979919
Win 2008 standard Bsod every day
Last modified: 2013-07-29 06:13:35 EDT
Created attachment 767259 [details]
This is a Dump Files
My Virtio Driver is a virtio-win-0.1-49.iso
my guest is a Windows 2008 Standard SP2 and dump every day my Antivirus is Symantec Endpoint 12.1
please See my dump files
I think that it is a virtio driver bug
and host write this
virtio_ioport_write: unexpected address 0x13 value 0x1
Pls provide following info:
qemu-kvm commandline via #ps aux|grep qemu-kvm
qemu-kvm virtio-win version
root 14389 0.0 0.0 103244 884 pts/3 S+ 12:00 0:00 grep qemu-kvm
qemu 24937 28.6 58.1 30527860 28747200 ? Sl Jun27 1535:10 /usr/libexec/qemu-kvm -S -M rhel6.3.0 -cpu Westmere,+rdtscp,+pdpe1gb,+dca,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 28672 -smp 10,sockets=10,cores=1,threads=1 -name server2 -uuid fc777dac-c05e-181a-a100-29f7530c4de8 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/server2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/mapper/mpathcp1,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=native -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/vfs/iso/virtio-win-0.1-49.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3e:46:c6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
virtio-win version - virtio-win-0.1-49
Looks like completely random crashes to me. How does it work with e1000 instead of netkvm and without balloon? Can you also switch to kernel memory dump option instead of small memory dump? And how does it work when you disable avtivirus?
Dear Vadim I Don't switch kernel memory dump to small memory dump , and can not disable Antivirus it is a Terminal Server and 40 users online and i didn't try e1000
Thanks a lot
Please Help Vadim What can i do in steps ?
Next time, when your system is down, please try switching
to the "Kernel Memory Dump" option http://support.microsoft.com/kb/969028.
Kernel dump provides more information and much better for the crash analysis
Thanks vadim I will change the small memory dump and write when my system is crash
(In reply to Razmik from comment #8)
> Thanks vadim I will change the small memory dump and write when my system is
Why can not change dump from minidump to kernel memeory Dump ,Guest will not reboot and users could not be affects
Dear Mike i Changed Kernel Memory dump to small memory dump(128kb)
Just to be clear. The "virtio_ioport_write: unexpected address 0x13 value 0x1" is an indication that the NetKVM driver caught this BSOD, so it does not add any new information. This was already removed in the newer versions.
Dear Ronen how i can uninstall NetKVM driver completely and install newer version and what version is a good for Server 2008 SP2
is it the solution of my problem ?
(In reply to Razmik from comment #12)
> Dear Ronen how i can uninstall NetKVM driver completely and install newer
> version and what version is a good for Server 2008 SP2
Pls generate kernel memory Dump first when guest crash(pls use "zip" instead of "rar"),and let developer to analyze what the root cause is
Dear Mike is the C://Windows/Memory.dmp full memory Dump ?
file size 800mb
(In reply to Razmik from comment #15)
> Dear Mike is the C://Windows/Memory.dmp full memory Dump ?
> file size 800mb
it may be full memory dump or kernel memory dump .Can you compress it to zip format and upload it someone for developer to check ?
Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
This is a Full Memory Dump
(In reply to Razmik from comment #18)
> This is a Full Memory Dump
The crash, you've got here, (SYSTEM_SERVICE_EXCEPTION) indicates a problem when switching from user mode to kernel. I would suggest checking the host memory first, and then, if memory test did find any problem, trying to run the guest in safe mode.
We suspect that the problem is specific to the user's computer.