[Users] Can't start vm

[Federico Simoncelli]

----- Original Message -----
> From: "kumar shantanu" <k.shantanu2006 at gmail.com>
> To: "users" <users at ovirt.org>
> Sent: Monday, March 12, 2012 9:16:34 AM
> Subject: [Users] Can't start vm
> 
> 
> Hi all,
> 
> I created host from ovirt manager but when trying to run it's failing
> with the error,
> 
> ==> vdsm.log <==
> Thread-180651::DEBUG::2012-03-12
> 13:42:12,482::vm::577::vm.Vm::(_startUnderlyingVm)
> vmId=`c13c4c09-f696-47e1-b8cd-8d499242e151`::_ongoingCreations
> released
> Thread-180651::ERROR::2012-03-12
> 13:42:12,482::vm::601::vm.Vm::(_startUnderlyingVm)
> vmId=`c13c4c09-f696-47e1-b8cd-8d499242e151`::The vm start process
> failed
> Traceback (most recent call last):
> File "/usr/share/vdsm/vm.py", line 567, in _startUnderlyingVm
> self._run()
> File "/usr/share/vdsm/libvirtvm.py", line 1306, in _run
> self._connection.createXML(domxml, flags),
> File "/usr/share/vdsm/libvirtconnection.py", line 82, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2087, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: internal error Process exited while reading console log
> output: Supported machines are:
> pc RHEL 6.2.0 PC (alias of rhel6.2.0)
> 
> 
> 
> Pythong version running is
> 
> [root at ovirt ~]# python -V
> Python 2.7
> 
> Can anyone please suggest .

Hi Kumar,
 when the engine starts a VM it also specifies a machine type.
The machine types supported by an host depend on the system (RHEL/Fedora)
and you can get the list with:

 # vdsClient 0 getVdsCaps | grep emulatedMachines
	emulatedMachines = ['pc-1.1', 'pc', 'pc-1.0', 'pc-0.15', ...

Once you discovered the types supported by your hosts you can configure
the engine with the correct value:

http://www.ovirt.org/wiki/Engine_Node_Integration

psql -U postgres engine -c "update vdc_options set option_value='pc-0.14' 
 where option_name='EmulatedMachine' and version='3.0';"

I assume that you ran the command above but your VDSM hosts are rhel6,
so you would need to use the "rhel6.2.0" value instead.

I believe that the value "pc" is an alias that works both for RHEL and
Fedora and it might be handy for testing, but in general I really discourage
its use because it would allow a mixed cluster of RHEL and Fedora hosts
which could be problematic in case of live migrations.

-- 
Federico