Hide Forgot
Description of problem: When you ask clusvcadm to start a VM that does not have a corresponding foo.xml file in the 'path="/..."' attribute, it reports: ===== Feb 22 22:20:54 an-node02 rgmanager[19481]: [vm] Could not find vm02-win or vm02-win.xml in search path /shared/definitions/ Feb 22 22:20:55 an-node02 rgmanager[19528]: [vm] Cannot find 'xm'; is it installed? Feb 22 22:20:55 an-node02 rgmanager[19567]: [vm] Could not find vm02-win or vm02-win.xml in search path /shared/definitions/ Feb 22 22:20:55 an-node02 rgmanager[19614]: [vm] Cannot find 'xm'; is it installed? Feb 22 22:20:55 an-node02 rgmanager[14505]: start on vm "vm02-win" returned 2 (invalid argument(s)) Feb 22 22:20:55 an-node02 rgmanager[14505]: #68: Failed to start vm:vm02-win; return value: 1 Feb 22 22:20:55 an-node02 rgmanager[14505]: Stopping service vm:vm02-win ===== This provides all the needed info, "Could not find vm02-win or vm02-win.xml in search path /shared/definitions/", but it also shows "Cannot find 'xm'; is it installed?" which seems quite unrelated. Version-Release number of selected component (if applicable): rgmanager-3.0.12.1-5.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Use clusvcadm to start a VM without an XML definition file defined 2. Read /var/log/messages 3. ... 4. Profit? Actual results: unhelpful log messages. Expected results: Only helpful log messages. Additional info: Lowest priority bug ever.
The extra "Cannot find 'xm'; is it installed?" comes from vm.sh resource agent. Reassigning.
If this is a KVM cluster, I also believe that you need to specify: use_virsh=1 to set the management tools for VM to virsh. xm is checkd in case it is a xen VM you are managing.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Bumping to 6.5 since this fix didn't make the devel freeze. (Feel free to move back to 6.4 with an exception or blocker flag if it's needed for the release).
(In reply to Fabio Massimo Di Nitto from comment #3) > If this is a KVM cluster, I also believe that you need to specify: > > use_virsh=1 > > to set the management tools for VM to virsh. > > xm is checkd in case it is a xen VM you are managing. The log messages actually are related. The domain's xml file can't be found because it doesn't exist. During the validate function after the xml file isn't found it thinks you are trying to use xen's xm configuration tool and takes that approach. That's why you see the message about 'xm' not being found. The agent is telling us something we need to know about its behavior. Set use_virsh=1 and this goes away. I would like to close this issue if no one has any objections. -- Vossel