Juan Pablo Lorier wrote:
Hi,
I've tried with a brand new fedora vm without OS and I have the same
error. I've made the configuration change proposed by Joop not only for
3.2 version but also for 3.1 just in case something stays in the vms
after creation (as they were not exported and then import
Hi,
I've tried with a brand new fedora vm without OS and I have the same
error. I've made the configuration change proposed by Joop not only for
3.2 version but also for 3.1 just in case something stays in the vms
after creation (as they were not exported and then imported, just used
the LUN).
I h
Hi Matthew,
You may have to create your own thread as this one is for a problem I
have after the migration.
Regards,
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Hi All,
I have an environment that is 3.1 and heavily used; I am setting up
a second. In the groups opinion would it be better to create the new
environment in 3.1 and migrate it to 3.2 to experience the path; or
create it in 3.2 and attempt a 3.3 install?
Also, can I go directly f
Hi Joop,
Thanks for the post. I've tried what you've suggested but the result is
the same:
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
5 matches
Mail list logo