* Brad Campbell (lists2...@fnarfbargle.com) wrote: > On 2/9/19 6:23 pm, Brad Campbell wrote: > > > > > Here is the holdup : > > > > 11725@1567416625.003504:qxl_ring_command_check 0 native > > 11725@1567416625.102653:qxl_io_write 0 native addr=0 (QXL_IO_NOTIFY_CMD) > > val=0 size=1 async=0 > > > > ~100ms delay prior to each logged QXL_IO_NOTIFY_CMD on the AMD box which > > explains the performance difference. Now I just need to figure out if > > that lies in the guest, the guest QXL driver, QEMU or SPICE and why it > > exhibits on the AMD box and not the i7. > > > > To get to this point, I recompiled the kernel on the i7 box with both > > AMD and Intel KVM modules. Once that was running I cloned the drive and > > put it in the AMD box, so the OS, software stack and all dependencies > > are identical. > > Reacp : > > I have a machine with a Windows 7 VM which is running on an i7-3770. This > works perfectly. > > Clone the disk and put it in a new(ish) AMD Ryzen 1500x machine and the > display output using qxl/spice is now limited to ~5-7fps. > > I originally cloned the entire machine to keep the software versions > identical. > > To simplify debugging and reproduction I'm now using : > - An identical SPICE version to that on the i7. > - A fresh 64 bit Windows 7 VM. > - The D2D benchmark from Crystalmark 2004R7. > > The machine is booted with : > > qemu -enable-kvm \ > -m 8192\ > -rtc base=localtime\ > -vga qxl\ > -device qxl\ > -global qxl-vga.guestdebug=3\ > -global qxl-vga.cmdlog=1\ > -global qxl-vga.vram_size=65536\ > -global qxl.vram_size=65536\ > -global qxl-vga.ram_size=65536\ > -global qxl.ram_size=65536\ > -net nic,model=virtio\ > -net tap,ifname=tap0,script=/etc/qemu-ifup,vhost=on\ > -usbdevice tablet\ > -spice port=5930,disable-ticketing\ > -device virtio-serial\ > -chardev spicevmc,id=vdagent,name=vdagent\ > -device virtserialport,chardev=vdagent,name=com.redhat.spice.0\ > -smp 3,maxcpus=3,cores=3,threads=1,sockets=1\ > -cpu qemu64,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time \
-cpu qemu64 is almost always a bad idea; does -cpu host help ? Dave > -drive > file=/server/VM/Cadbox.raw,if=virtio,aio=threads,format=raw,cache=unsafe > -boot c \ > -drive > file=/server/VM/Cadbox_swap.raw,if=virtio,aio=threads,format=raw,cache=unsafe > \ > > > The D2D benchmark runs through a series of Sprites (stars) and it just > shuffles them around the screen. > > With KVM enabled I get : > > Sprite 10 - 8.66fps > Sprite 100 - 8.47fps > Sprite 500 - 8.45fps > Sprite 1000 - 8.18fps > Sprite 5000 - 7.64fps > Sprite 10000 - 7.26fps > > With the identical system, with KVM disabled I get : > > Sprite 10 - 28.97fps > Sprite 100 - 27.24fps > Sprite 500 - 23.85fps > Sprite 1000 - 22.00fps > Sprite 5000 - 11.11fps > Sprite 10000 - 4.50fps > > On the i7 with the same software version and kvm enabled : > > Sprite 10 - 88.58fps > Sprite 100 - 88.35fps > Sprite 500 - 85.64fps > Sprite 1000 - 83.33fps > Sprite 5000 - 58.08fps > Sprite 10000 - 45.29fps > > > cpuinfo from the host : > processor : 7 > vendor_id : AuthenticAMD > cpu family : 23 > model : 1 > model name : AMD Ryzen 5 1500X Quad-Core Processor > stepping : 1 > microcode : 0x8001138 > cpu MHz : 2877.596 > cache size : 512 KB > physical id : 0 > siblings : 8 > core id : 5 > cpu cores : 4 > apicid : 11 > initial apicid : 11 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat > pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp > lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni > pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx > f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse > 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext > perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 > avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 > xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale > vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic > v_vmsave_vmload vgif overflow_recov succor smca > bugs : sysret_ss_attrs null_seg spectre_v1 spectre_v2 > spec_store_bypass > bogomips : 6985.80 > TLB size : 2560 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 43 bits physical, 48 bits virtual > power management: ts ttp tm hwpstate eff_freq_ro [13] [14] > > qemu configured with : > PKG_CONFIG_PATH=/usr/local/libvirt/lib/pkgconfig:/usr/local/libvirt/share/pkgconfig/ > ./configure --target-list=x86_64-softmmu --disable-gtk && make -j6 > test:~# uname -a > > Linux test 5.2.9 #42 SMP Tue Aug 20 16:41:13 AWST 2019 x86_64 GNU/Linux > > test:~# zgrep KVM /proc/config.gz > CONFIG_HAVE_KVM=y > CONFIG_HAVE_KVM_IRQCHIP=y > CONFIG_HAVE_KVM_IRQFD=y > CONFIG_HAVE_KVM_IRQ_ROUTING=y > CONFIG_HAVE_KVM_EVENTFD=y > CONFIG_KVM_MMIO=y > CONFIG_KVM_ASYNC_PF=y > CONFIG_HAVE_KVM_MSI=y > CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y > CONFIG_KVM_VFIO=y > CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y > CONFIG_KVM_COMPAT=y > CONFIG_HAVE_KVM_IRQ_BYPASS=y > CONFIG_KVM=m > # CONFIG_KVM_INTEL is not set > CONFIG_KVM_AMD=m > # CONFIG_KVM_MMU_AUDIT is not set > > test:~# qemu --version > QEMU emulator version 4.1.50 (v4.1.0-714-g90b1e3a) > Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers > > To be clear, I'm not chasing benchmarks. This is a real issue with trying to > run CAD on a Windows 7 VM on a Ryzen machine. > > I've tried it on two machines (a 1500x and an 1800x) with the same result. > The same configuration on the i7 box works perfectly. > > I've tried several versions of SPICE, multiple versions of KVM, kernels back > as far as 4.0 with KVM enabled, different old and new windows VMs and driver > versions. The only constant is it is limited on the AMD box if KVM is > enabled. > > I was leaning towards it being something in the qemu/spice software stack, > but the fact that without kvm enabled it goes as fast as the CPU will allow > it would indicate perhaps the fault likes in some relationship with kvm, so > I'm cross-posting to qemu-devel to see if this jogs someones memory, or if > there are any other things I can try to attempt to solve this one. > > Regards, > Brad > -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK