9:56 p.m.
This is a multi-part message in MIME format.
--------------050707030902010005040304
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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,
Juan Pablo Lorier
--------------050707030902010005040304
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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: medium none;">
<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>
Juan Pablo Lorier<br>
</body>
</html>
--------------050707030902010005040304--