it's probably of my limit knowledge on the matter, but I still don't understand why? I and would be very thankful if someone could explain the issue? If it is a needed hardware feature (CPU/Chipset), why does it work with older machine types? Is it because QEMU is able to emulating this *synic* feature on those older machine types, and not the newer ones?
On Thu, Aug 8, 2019 at 5:18 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the qemu-kvm package: > > #934070: No support for HyperV synIC in machine type > pc-i440fx-3.0 > > It has been closed by Michael Tokarev <m...@tls.msk.ru>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Tokarev < > m...@tls.msk.ru> by > replying to this email. > > > -- > 934070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934070 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Michael Tokarev <m...@tls.msk.ru> > To: Brian Wengel <m40636...@gmail.com>, 934070-d...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 8 Aug 2019 18:05:29 +0300 > Subject: Re: Bug#934070: No support for HyperV synIC in machine type > > pc-i440fx-3.0 > 06.08.2019 20:31, Brian Wengel wrote: > > Package: qemu-kvm > > Version: 1:3.1+dfsg-7 (QEMU 3.1.0 / Kernel 4.19) > [] > > "error: internal error: process exited while connecting to monitor: > Hyper-V SynIC (requested by 'hv-synic' cpu flag) requires Hyper-V VP_INDEX > > ('hv-vpindex') > > 2019-08-06T13:29:14.114943Z qemu-system-x86_64: kvm_init_vcpu failed: > Function not implemented" > > > https://bugzilla.redhat.com/show_bug.cgi?id=1738244 > > As per https://bugzilla.redhat.com/show_bug.cgi?id=1738244#c6 (comment 6), > this is expected behavour, so closing this bugreport. > > Thanks, > > /mjt > > > ---------- Forwarded message ---------- > From: Brian Wengel <m40636...@gmail.com> > To: sub...@bugs.debian.org > Cc: > Bcc: > Date: Tue, 6 Aug 2019 19:31:56 +0200 > Subject: No support for HyperV synIC in machine type > pc-i440fx-3.0 > > Package: qemu-kvm > Version: 1:3.1+dfsg-7 (QEMU 3.1.0 / Kernel 4.19) > > > Running Windows 10 guest build >= 1803 will give high host CPU usage (even > though it's close to null in client) if you don't enable HyperV synIC which > can i.a. be done in Virt XML: > > <hyperv> > <relaxed state='on'/> > <vapic state='on'/> > <spinlocks state='on' retries='8191'/> > * <synic state='on'/>* > <stimer state='on'/> > </hyperv> > > > But it seem only older machine types support this property. > I've tested the following machine types: > > > pc-i440fx-2.8 (OK) > pc-i440fx-3.0 (OK) > pc-i440fx-3.1 (Fail) > pc-q35-3.1 (Fail) > > > When starting the VM you get the error: > > "error: internal error: process exited while connecting to monitor: > Hyper-V SynIC (requested by 'hv-synic' cpu flag) requires Hyper-V VP_INDEX > ('hv-vpindex') > 2019-08-06T13:29:14.114943Z qemu-system-x86_64: kvm_init_vcpu failed: > Function not implemented" > > Attached a copy of a working XML. To reproduce just specify a newer > machine type e.g. "pc-i440fx-3.1". I assume you don't need a working > Windows image file, any qcow2 file will do. > > https://bugzilla.redhat.com/show_bug.cgi?id=1738244 > > > Best regards > Brian >
