Launchpad has imported 2 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1851244.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2020-06-25T21:40:26+00:00 kevin wrote: Description of problem: virt-install currently enables hv-time,hv-relaxed,hv-vapic,hv- spinlocks=0x1fff for guests which support Hyper-V. There are several additional Hyper-V enlightenments supported by QEMU and libvirt (see https://github.com/qemu/qemu/blob/master/docs/hyperv.txt and https://libvirt.org/formatdomain.html#elementsFeatures) which could be useful to enable. In particular, hv_stimer significantly reduces CPU usage when supporting VMs are paused (see https://lore.kernel.org/kvm/20200625201046.GA179502@kevinolos/). Version-Release number of selected component (if applicable): 2.2.1/master How reproducible: 100% Steps to Reproduce: 1. virt-install --os-variant win10 --print-xml Actual results: <hyperv> <relaxed state="on"/> <vapic state="on"/> <spinlocks state="on" retries="8191"/> </hyperv> Expected results: Something more like: <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state="on" retries="8191"/> <vpindex state='on'/> <runtime state='on'/> <synic state='on'/> <stimer state='on'/> <frequencies state='on'/> <tlbflush state='on'/> <ipi state='on'/> </hyperv> Additional info: I'm not advocating for any specific Hyper-V enlightenments to be enabled, but I suspect the current defaults are sub-optimal and I would be willing to help improve them. Is there a process for evaluating which to enable, or is it simply a matter of adding defaults for features which weren't available previously? Thanks, Kevin Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1851062/comments/14 ------------------------------------------------------------------------ On 2020-09-15T21:12:18+00:00 crobinso wrote: Thanks for the report. This will take a discussion with qemu developers to understand what it will take to safely enable more options, if there's tradeoffs, etc. We are moving to using github issues for upstream virt-manager, so I moved this issue there: https://github.com/virt-manager/virt- manager/issues/154 Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1851062/comments/18 ** Changed in: virt-manager Status: Unknown => Won't Fix ** Changed in: virt-manager Importance: Unknown => Undecided ** Bug watch added: github.com/virt-manager/virt-manager/issues #154 https://github.com/virt-manager/virt-manager/issues/154 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851062 Title: Qemu using CPU even when the VM is paused To manage notifications about this bug go to: https://bugs.launchpad.net/virt-manager/+bug/1851062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
