>> The QEMU command line (/var/log/libvirt/qemu/[domain name].log), >> LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none >> /usr/local/bin/qemu-system-x86_64 -name ATS1 -S -M pc-0.12 -cpu qemu32 >> -enable-kvm -m 12288 -smp 4,sockets=4,cores=1,threads=1 -uuid >> 0505ec91-382d-800e-2c79-e5b286eb60b5 -no-user-config -nodefaults >> -chardev >> socket,id=charmonitor,path=/var/lib/libvirt/qemu/ATS1.monitor,server,n >> owait -mon chardev=charmonitor,id=monitor,mode=control -rtc >> base=localtime -no-shutdown -device >> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive >> file=/opt/ne/vm/ATS1.img,if=none,id=drive-virtio-disk0,format=raw,cach >> e=none -device >> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id >> =virtio-disk0,bootindex=1 -netdev >> tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device >> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:e0:fc:00:0f:00,bus=pci.0 >> ,addr=0x3,bootindex=2 -netdev >> tap,fd=22,id=hostnet1,vhost=on,vhostfd=23 -device >> virtio-net-pci,netdev=hostnet1,id=net1,mac=00:e0:fc:01:0f:00,bus=pci.0 >> ,addr=0x4 -netdev tap,fd=24,id=hostnet2,vhost=on,vhostfd=25 -device >> virtio-net-pci,netdev=hostnet2,id=net2,mac=00:e0:fc:02:0f:00,bus=pci.0 >> ,addr=0x5 -netdev tap,fd=26,id=hostnet3,vhost=on,vhostfd=27 -device >> virtio-net-pci,netdev=hostnet3,id=net3,mac=00:e0:fc:03:0f:00,bus=pci.0 >> ,addr=0x6 -netdev tap,fd=28,id=hostnet4,vhost=on,vhostfd=29 -device >> virtio-net-pci,netdev=hostnet4,id=net4,mac=00:e0:fc:0a:0f:00,bus=pci.0 >> ,addr=0x7 -netdev tap,fd=30,id=hostnet5,vhost=on,vhostfd=31 -device >> virtio-net-pci,netdev=hostnet5,id=net5,mac=00:e0:fc:0b:0f:00,bus=pci.0 >> ,addr=0x9 -chardev pty,id=charserial0 -device >> isa-serial,chardev=charserial0,id=serial0 -vnc *:0 -k en-us -vga >> cirrus -device i6300esb,id=watchdog0,bus=pci.0,addr=0xb >> -watchdog-action poweroff -device >> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa >> >Which QEMU version is this? Can you try with e1000 NICs instead of virtio? > This QEMU version is 1.0.0, but I also test QEMU 1.5.2, the same problem exists, including the performance degradation and readonly GFNs' flooding. I tried with e1000 NICs instead of virtio, including the performance degradation and readonly GFNs' flooding, the QEMU version is 1.5.2. No matter e1000 NICs or virtio NICs, the GFNs' flooding is initiated at post-restore stage (i.e. running stage), as soon as the restoring completed, the flooding is starting. Thanks, Zhang Haoyu >-- > Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
