Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi, doun
After checking with my colleague, tried in this machine.
# rpm -q qemu-kvm
qemu-kvm-1.5.3-156.el7_5.5.x86_64
The reason is as following, you can check whether this issue can work in qemu-kvm-rhev
https://bugzilla.redhat.com/show_bug.cgi?id=1313877#c6
Just so you know,
I can see the TscInvariant on VM after installing qemu-kvm-rhev
[root@localhost /]# rpm -qa | grep qemu-kvm-rhev
qemu-kvm-rhev-2.10.0-21.el7_5.4.x86_64
Thanks
Regards
Doun
Description of problem: when i add an invtsc feature in CPU element, the VM can not start. Steps to Reproduce: 1. check TscInvariant (Hypervisor) [root@localhost ~]# cpuid | grep TscI Disclaimer: cpuid may not support decoding of all cpuid registers. TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true TscInvariant = true 2. check capabilities (Hypervisor) [root@localhost ~]# virsh capabilities | grep -i tsc <feature name='tsc_adjust'/> <feature name='invtsc'/> 3. add "feature invtsc" using virsh [root@localhost ~]# virsh edit guest2-rhel7 ... <cpu mode='host-model' check='partial'> <model fallback='allow'/> <feature policy='force' name='invtsc'/> </cpu> 4. start virtual machine. but it failed [root@localhost ~]# virsh start guest2-rhel7 error: Failed to start domain guest2-rhel7 error: unsupported configuration: host doesn't support invariant TSC Actual results: the VM(guest2-rhel7) didn't start Cannot check the TscInvariant. Expected results: the VM(guest2-rhel7) started the VM(guest2-rhel7) has "TscInvariant = true" when i checked by cpuid command Additional info: - Environments(rpms) libvirt-client-3.9.0-14.el7_5.7.x86_64 libvirt-3.9.0-14.el7_5.7.x86_64 - it works in same procedure on Fedora 25.