diff options
Diffstat (limited to 'results/classifier/zero-shot/118/kernel/1461918')
| -rw-r--r-- | results/classifier/zero-shot/118/kernel/1461918 | 53 |
1 files changed, 53 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/kernel/1461918 b/results/classifier/zero-shot/118/kernel/1461918 new file mode 100644 index 000000000..ca4283f64 --- /dev/null +++ b/results/classifier/zero-shot/118/kernel/1461918 @@ -0,0 +1,53 @@ +kernel: 0.949 +x86: 0.946 +files: 0.941 +device: 0.924 +vnc: 0.891 +performance: 0.882 +boot: 0.878 +peripherals: 0.848 +architecture: 0.843 +network: 0.820 +graphic: 0.815 +hypervisor: 0.730 +PID: 0.707 +permissions: 0.702 +socket: 0.690 +register: 0.656 +virtual: 0.639 +semantic: 0.614 +VMM: 0.606 +debug: 0.589 +mistranslation: 0.567 +user-level: 0.566 +ppc: 0.509 +i386: 0.376 +risc-v: 0.350 +assembly: 0.304 +TCG: 0.280 +arm: 0.221 +KVM: 0.202 + +guest hangs after use ethtool to set scatter-gather on + +On the guests, i have a rtl8139 nic, I use ethtool to set scatter-gather on ( ethtool -K eth0 sg on ), +after that, at host side, I use scp to send a file into guest. As a result, guest hang. +At that point qemu is using 100% of one host CPU, about 100% guest. + +If guest is centOS6.5, with no problem. + + + +The guest system is Fedora release 19(Kernel 3.11.10-200.fc19.x86_64). + +host system is debian 7.1. +Kernel:3.10.0 +Qemu: 2.3.0 + +cmd: +/boot/qemu-2.3.0-bin/qemu-system-x86_64 -vnc :13 -enable-kvm -name fedora -smp sockets=1,cores=2 -cpu core2duo -nodefaults -vga cirrus -k en-us -boot menu=on,splash-time=8000 -m 2048 -usb -drive file=/boot/vm-disk-1.qcow2,if=none,id=drive-ide0,cache=none,aio=native -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100 -netdev type=tap,id=net0,ifname=200,script=/etc/kvm/vtp-bridge -device rtl8139,romfile=,mac=FE:FC:FE:5C:58:65,netdev=net0,bus=pci.0,addr=0x12,id=net0 + +Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU and Fedora? Or could we close this ticket nowadays? + +[Expired for QEMU because there has been no activity for 60 days.] + |