I apologize, I didn't realize I had to restart. It's fixed. Thank you very much. Regards,
Juan Pablo Lorier On 08/07/13 17:55, Joop wrote: > 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: > > 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 >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users