This is a multi-part message in MIME format. --------------020202070501060009040909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Juan Pablo Lorier wrote:
Hi,
I need to get ovirt to production as my XEN environment is falling apart. I've been dealing with the problem of been unable to run any VM on the updated- reinstalled ovirt from 3.1 to 3.2 Any VM I try to start exits with this error:
VM SambaDC1 is down. Exit message: internal error process exited while connecting to monitor: Supported machines are: pc RHEL 6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default) rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC .
The VMs are centos 6.4 and were fresh installed in each VM iscsi LUN while using 3.1 but though I deleted the original VMs (purged the database with engine-cleanup as part of the reinstall process) and created them in 3.2, it fails to work. Please let me know what info I need to get this running. Regards,
From a thread from a couple of days back:<br> <br> our host is EL, and engine sends non-EL values for 'emulatedMachine' <div>are you using engine from latest master?</div> <div>if so, you need to select for the cluster the correct emulated machine (rhel 6.4)<br> </div> if not, change with ovirt-config the "EmulatedMachine" value to <span
From a thread from a couple of days back: our host is EL, and engine sends non-EL values for 'emulatedMachine' are you using engine from latest master? if so, you need to select for the cluster the correct emulated machine (rhel 6.4) if not, change with ovirt-config the "EmulatedMachine" value to rhel6.4.0 for the right cluster compatibility version (i assume 3.3 or 3.2) engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.3 Look at the cluster version of your installation and adapt the above. run a engine-config -g EmulatedMachine first and make sure you have backups. Regards, Joop --------------020202070501060009040909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Juan Pablo Lorier wrote: <blockquote cite="mid:51DB195C.502@gmail.com" type="cite"> <meta http-equiv="content-type" content="text/html; "> Hi,<br> <br> I need to get ovirt to production as my XEN environment is falling apart.<br> I've been dealing with the problem of been unable to run any VM on the updated- reinstalled ovirt from 3.1 to 3.2<br> Any VM I try to start exits with this error:<br> <br> <div title="VM SambaDC1 is down. Exit message: internal error process exited while connecting to monitor: Supported machines are: pc RHEL 6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default) rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC ." style="outline-color: invert; outline-style: none; outline-width: medium;"> <div id="gwt-uid-1428_col2_row4">VM SambaDC1 is down. Exit message: internal error process exited while connecting to monitor: Supported machines are: pc RHEL 6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default) rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC .</div> </div> <br> <br> The VMs are centos 6.4 and were fresh installed in each VM iscsi LUN while using 3.1 but though I deleted the original VMs (purged the database with engine-cleanup as part of the reinstall process) and created them in 3.2, it fails to work.<br> Please let me know what info I need to get this running.<br> Regards,<br> <br> </blockquote> style="font-family: Verdana;" data-mce-style="font-family: Verdana;"><span style="font-size: 12px;" data-mce-style="font-size: 12px;">rhel6.4.0</span></span> for the right cluster compatibility version (i assume 3.3 or 3.2)<br> <br> <tt> engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.3<br> <br> Look at the cluster version of your installation and adapt the above.<br> run a engine-config -g EmulatedMachine first and make sure you have backups.<br> <br> Regards,<br> <br> Joop<br> <br> </tt> </body> </html> --------------020202070501060009040909--