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.

Description of problem:

In RHEVM, two hypervisors A,B are in the failover domain with  hyperthreading on, if hypervisor A is down, the virtual machine on A would be relocate to B, and this relocation would cause all virtual machine on B get stuck.


Version-Release number of selected component (if applicable):

RHEV-hypervisor 6.x

How reproducible:


Steps to Reproduce:
1. Setup rhevm, 2 rhev-hypervisor and  2 rhev-hypervisor are in the cluster with failover.

2. On 2 hypervisors, turn hyperthreading on,

3. Shutdown one of the hypervisor.

4. Virtual machines are relocated which causes virtual machine on the other hypervisor hang.
  
Actual results:

virtual machine on the other hypervisor hang.

Expected results:

virtual machines are relocated smoothly.

Additional info:

Hi, Geng Sheng

Could you help provide more detail information?
(1) What is the kernel and qemu-kvm version for the two host? 
(2) What is the rhevm, vdsm, libvirt version? 
(3) So the hyperthreading is off originally?
(4) What is your command to turn on the hyperthreading? 
(5) What is the qemu command line? (ps ax | grep qemu)


Thanks,
Qunfang

Last update to Customer Portal case: May 24, 2013
Status of Customer Portal case: Closed

Closing as INSU.