Your message dated Thu, 8 Aug 2019 18:05:29 +0300
with message-id <[email protected]>
and subject line Re: Bug#934070: No support for HyperV synIC in machine type >
pc-i440fx-3.0
has caused the Debian Bug report #934070,
regarding No support for HyperV synIC in machine type > pc-i440fx-3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
934070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934070
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
<domain type='kvm'>
<name>W10_tmp1</name>
<uuid>eb67095c-f97b-4b98-8e88-635010602585</uuid>
<description>Win10</description>
<metadata>
<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0";>
<libosinfo:os id="http://microsoft.com/win/10"/>
</libosinfo:libosinfo>
</metadata>
<memory unit='KiB'>2097152</memory>
<currentMemory unit='KiB'>2097152</currentMemory>
<vcpu placement='static'>2</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/mnt/NVMe_OLD_ROOT/VMs/W10_tmpX.fd</nvram>
<boot dev='hd'/>
<boot dev='cdrom'/>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='8191'/>
<synic state='on'/>
<stimer state='on'/>
</hyperv>
</features>
<cpu mode='host-model' check='partial'>
<model fallback='allow'/>
</cpu>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
<timer name='hypervclock' present='yes'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<pm>
<suspend-to-mem enabled='no'/>
<suspend-to-disk enabled='no'/>
</pm>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='sda' bus='scsi'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none' discard='unmap'/>
<source file='/mnt/VMs/W10/disk1.qcow2'/>
<target dev='sdc' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='2'/>
</disk>
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<controller type='usb' index='0' model='qemu-xhci' ports='15'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</controller>
<controller type='sata' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='scsi' index='0' model='virtio-scsi'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</controller>
<controller type='scsi' index='1' model='virtio-scsi'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:8f:98:46'/>
<source bridge='brLAN'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='2'/>
</channel>
<input type='tablet' bus='usb'>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<graphics type='vnc' port='5901' autoport='no' listen='0.0.0.0' keymap='da' passwd='xxxx'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='vga' vram='16384' heads='1' primary='yes'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
</memballoon>
</devices>
</domain>
--- End Message ---
--- Begin Message ---
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
--- End Message ---
