Description of problem: CU powered off a Windows 2008 R2 Enterprise Server VM and then when he tried to start it back the VM got paused on RHEV with no other messages on the GUI Version-Release number of selected component (if applicable): Manager rhevm-3.2.2-0.41.el6ev.noarch qemu-kvm-rhev-0.12.1.2-2.355.el6_4.9.x86_64 Hypervisor Red Hat Enterprise Virtualization Hypervisor release 6.4 (20130709.0.el6_4) qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64 How reproducible: Not known at this time Steps to Reproduce: 1. Install and run a Windows 2008 R2 VM on RHEV 3.2 with 2 vCPU, 2. Ensure that there is no suficient CPU's on the hypervisor where the VM is running or remove some of them. 3. Power off the VM and try to start it back. Actual results: VM won't boot leaving the spice console in black with no information inside RHEV GUI Expected results: RHEV should print a message indicating that there are no enough CPUs to start the VM on the selected hypervisor. Additional info: As a workaround CU added 4 more CPUs to their hypervisor and after that he was able to start the VM Adding the logs as priv attachments for analysis
This should have been resolved by the new RHEV scheduler starting RHEV 3.3. Gilad, can please verify it?
component seems wrong?
(In reply to Itamar Heim from comment #6) > component seems wrong? let's leave it on sla, till I test Doron's request.
(In reply to Gilad Chaplik from comment #7) > (In reply to Itamar Heim from comment #6) > > component seems wrong? > > let's leave it on sla, till I test Doron's request. I misunderstood. I will check it out while checking it.
Starting rhev 3.3 the new scheduler provides the relevant information for each host if it cannot start a VM. So failure on network or memory or cpu info is propagated to the user, and also appears in the log file. Moving to be tested in 3.4.
Verified on rhevm 6 with rhevh RHEV Hypervisor - 6.5 - 20140408.0.el6ev Vm have 8 cpus(8 sockets), host have 4 socets, when try to run vm, appear error message: Error while executing action: vm1: Cannot run VM. There are no available running Hosts with enough cores in VM's Cluster . Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: The host rose01.qa.lab.tlv.redhat.com did not satisfy internal filter CPU. the same thing appear in engine.log
Changing component to rhev-hypervisor as we are going to move qemu-kvm-rhev component to RHEL7 product to be able to follow RHEL release cycle for qemu-kvm-rhev-2.0.0 and newer. Please check correct component assignment.
Miroslav, why is this specific for rhev-h and not any hypervisor? ie- as you can see from the verification in comment 10, the issue is handled in the engine regardless of the hypervisor type. So if any this should have been an engine issue. Component set accordingly.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html