Bug 1334963 - Windows VM will crash with BSOD when receive a certain package.
Summary: Windows VM will crash with BSOD when receive a certain package.
Keywords:
Status: CLOSED DUPLICATE of bug 1334736
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virtio-win
Version: unspecified
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-11 00:06 UTC by RichardZhang
Modified: 2016-08-01 15:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-01 15:09:49 UTC
Embargoed:


Attachments (Terms of Use)
the packet captured by tcpdump. (466 bytes, application/octet-stream)
2016-05-11 00:06 UTC, RichardZhang
no flags Details
BSOD message (113.71 KB, image/jpeg)
2016-05-11 00:07 UTC, RichardZhang
no flags Details
dump file in vm. (263.17 KB, application/octet-stream)
2016-05-11 00:10 UTC, RichardZhang
no flags Details

Description RichardZhang 2016-05-11 00:06:18 UTC
Created attachment 1155914 [details]
the packet captured by tcpdump.

Description of problem:
My windows VM will crash with BSOD when receive a certain network package on a virtio NIC. It's ok on rtl8139 or e1000.

Version-Release number of selected component (if applicable):
qemu-2.1.2
kernel-3.13 or kernel-4.1
virtio-win-0.1.102 or virtio-win-0.1.117

How reproducible:
I can reproduce it on both windows7 and windows2008r2. And I've tried several version of virtio-win. All of them present the same result. 
3/3

Steps to Reproduce:
1. start vm with libvirt and the qemu command line is:
/usr/bin/kvm -name win7_vs -S -machine pc-i440fx-2.1,accel=kvm,usb=off,system=windows -cpu qemu64,hv_time,hv_relaxed,hv_spinlocks=0x2000 -m size=4194304k,slots=10,maxmem=1073741824k -smp 1,maxcpus=8,sockets=8,cores=1,threads=1 -numa node,nodeid=0,cpus=0,mem=4096 -uuid 3799b110-5bfb-4004-bc76-c0ce267c19b2 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-win7_vs/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,clock=vm,driftfix=slew -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device usb-ehci,id=usb1,bus=pci.0,addr=0x4 -device nec-usb-xhci,id=usb2,bus=pci.0,addr=0x5 -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/vms/images/win7_sp1_x86_base.img,if=none,id=drive-ide0-0-1,format=qcow2,cache=directsync -device ide-hd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=1 -drive file=/vms/isos/virtio-win7.vfd,if=none,id=drive-fdc0-0-0,readonly=on,format=raw,cache=directsync -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=0c:da:41:1d:80:b5,bus=pci.0,addr=0x3 -netdev tap,fd=33,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=0c:da:41:1d:5d:c2,bus=pci.0,addr=0x8 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/win7_vs.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0 -vnc 0.0.0.0:1 -device VGA,id=video0,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
2. when the vm boot up, replay the package to correspond vnet.
tcpreplay -i vnet4 2603.pcap
3. a few seconds later, the vm will crash with BSOD.

Actual results:
The vm crashes with BSOD.

Expected results:
The vm runs smoothly.

Additional info:

Comment 1 RichardZhang 2016-05-11 00:07:23 UTC
Created attachment 1155915 [details]
BSOD message

Comment 2 RichardZhang 2016-05-11 00:10:03 UTC
Created attachment 1155916 [details]
dump file in vm.

Comment 3 Yvugenfi@redhat.com 2016-08-01 15:09:49 UTC

*** This bug has been marked as a duplicate of bug 1334736 ***


Note You need to log in before you can comment on or make changes to this bug.