Description of problem:
when i transfer big size data from guest to host via virtconsole with TCP socket, but met guest calltrace and fail to complete transfer data when i do a second transfer.

Version-Release number of selected component (if applicable):
host info:
2.6.32-398.el6.x86_64
qemu-kvm-0.12.1.2-2.378.el6.x86_64
guest info:
2.6.32-398.el6.x86_64

How reproducible:
only hit once

Steps to Reproduce:
1.boot guest with virtconsole via TCP socket.
e.g:...-device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=foo,host=localhost,port=12345,server,nowait -device virtconsole,chardev=foo,name=com.redhat.rhevm.vdsm.1,bus=virtio-serial0.0,id=port1,nr=1
2.repeatly transfer big data from guest to host.
guest]# ls -lh guest-file 
-rw-r--r--. 1 root root 2.0G Jul 17 19:10 guest-file
guest]# cat guest-file > /dev/hvc0
host ]# nc localhost 12345 >> recieve1
host ]# ls -lh recieve1
-rw-r--r--. 1 root root 2.0G Jul 19 17:01 recieve1

guest]# cat guest-file > /dev/hvc0
host ]# nc localhost 12345 >> recieve2

Actual results:
after step 2, fail to complete transfer and the guest side connection quit with 
'kernel:Disabling IRQ #11', and guest call trace.
# cat guest-file > /dev/hvc0

Message from syslogd@dhcp-8-219 at Jul 20 01:01:39 ...
 kernel:Disabling IRQ #11

# dmesg
irq 11: nobody cared (try booting with the "irqpoll" option)
Pid: 2681, comm: cat Not tainted 2.6.32-398.el6.x86_64 #1
Call Trace:
 <IRQ>  [<ffffffff810e4bdb>] ? __report_bad_irq+0x2b/0xa0
 [<ffffffff810e4ddc>] ? note_interrupt+0x18c/0x1d0
 [<ffffffff81032089>] ? ack_apic_level+0x79/0x1b0
 [<ffffffff810e557d>] ? handle_fasteoi_irq+0xcd/0xf0
 [<ffffffff8100de89>] ? handle_irq+0x49/0xa0
 [<ffffffff8152442c>] ? do_IRQ+0x6c/0xf0
 [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11
 <EOI>  [<ffffffff8151d7b7>] ? _spin_unlock_irqrestore+0x17/0x20
 [<ffffffff81344e09>] ? hvc_write+0xf9/0x120
 [<ffffffff8132eff0>] ? n_tty_write+0x1c0/0x460
 [<ffffffff81063d60>] ? default_wake_function+0x0/0x20
 [<ffffffff8132bee1>] ? tty_write+0x1b1/0x2a0
 [<ffffffff8132ee30>] ? n_tty_write+0x0/0x460
 [<ffffffff811834b8>] ? vfs_write+0xb8/0x1a0
 [<ffffffff81183d0b>] ? sys_read+0x3b/0x90
 [<ffffffff81183db1>] ? sys_write+0x51/0x90
 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
handlers:
[<ffffffffa00556b0>] (vp_interrupt+0x0/0x60 [virtio_pci])
Disabling IRQ #11

Expected results:
it should no any call trace, it can complete transfer data successfully.

Additional info:
# /usr/libexec/qemu-kvm -S -M rhel6.5.0 -cpu SandyBridge -enable-kvm -m 4096 -smp 4,sockets=2,cores=2,threads=1 -no-kvm-pit-reinjection -name sluo -uuid 43425b70-86e5-4664-bf2c-3b76699b8bec -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=foo,host=localhost,port=12345,server,nowait -device virtconsole,chardev=foo,name=com.redhat.rhevm.vdsm.1,bus=virtio-serial0.0,id=port1,nr=1 -drive file=/home/RHEL6.5-20130712.n.0-6.5-Server-x64.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK1" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-system-disk,id=system-disk,bootindex=1 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x5 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=2C:41:38:B6:40:21,bus=pci.0,addr=0x6,bootindex=2 -drive file=/home/my-data-disk.qcow2,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK2" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk,bootindex=3 -k en-us -boot menu=on -qmp tcp:0:4444,server,nowait -vnc :1 -spice port=5931,disable-ticketing -monitor stdio