-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
rhel-9.8, rhel-10.2
-
None
-
None
-
None
-
rhel-virt-core-libvirt-1
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Start a guest with cpu host-model, check pdcm feature setting by virsh dumpxml is 'disable', but in guest qemu cmdline pdcm feature is on.
Please provide the package NVR for which the bug is seen:
Host cpu: Intel(R) Xeon(R) Silver 4214 CPU @ 2.20GHz
1. on rhel10.2
# rpm -q libvirt qemu-kvm libvirt-11.10.0-1.el10.x86_64 qemu-kvm-10.1.0-9.el10.x86_64
2. on rhel9.8
# rpm -q libvirt qemu-kvm libvirt-11.10.0-2.el9.x86_64 qemu-kvm-10.1.0-10.el9.x86_64
How reproducible is this bug?:100%
Steps to reproduce
- Start a guest with cpu host-model:
<cpu mode='host-model' check='partial'/> - Check the cpu features by virsh dumpxml, and pdcm is 'disable'
# virsh dumpxml vm1 ... <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Cascadelake-Server</model> <vendor>Intel</vendor> <feature policy='require' name='vmx'/> <feature policy='disable' name='pdcm'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='ss'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='fdp-excptn-only'/> <feature policy='require' name='zero-fcs-fds'/> ...
3. Check the qemu cmdline of the guest, found pdcm is on.
# ps -ef | grep qemu-kvm ...-cpu Cascadelake-Server,vmx=on,pdcm=on,hypervisor=on,ss=on,tsc-adjust=on,fdp-excptn-only=on,zero-fcs-fds=on,mpx=on,umip=on,pku=on,md-clear=on,...
4. Login into guest and found no pdcm cpu flag in guest.
# lscpu | grep pdcm
Expected results
the pdcm feature get from virsh dumpxml should be same with qemu cmdline.
Actual results
the pdcm feature get from virsh dumpxml is different from qemu cmdline.
