Actually this is a bug [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1005562 On 09/24/2013 09:53 AM, lof yer wrote:
That's fine, I thought there was an option in api that make the start as normal one.
2013/9/24 Itamar Heim <iheim@redhat.com <mailto:iheim@redhat.com>>
On 09/24/2013 06:34 AM, lof yer wrote:
Ok, that's easy to accomplish. But when I use restapi to start a VM, why does the log show me that it runs in RUNONCE mode rather than NORMAL START?
since the api allows you to pass any parameter to affect the run. does it matter?
2013/9/24 lofyer <lofyer@gmail.com <mailto:lofyer@gmail.com> <mailto:lofyer@gmail.com <mailto:lofyer@gmail.com>>>
On 2013/9/24 6:03, Itamar Heim wrote:
On 09/23/2013 06:18 PM, lofyer wrote:
Besides assigning a watchdog device to it, are there any other ways to make the VM autostart even if an user shutdown it manually? ___________________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users>
<http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>>
if a user shut down a vm from inside or via engine? i suggest an external script on engine monitoring its status and starting it for such a use case
You mean a anacrontab script?
-- Michael Pasternak RedHat, ENG-Virtualization R&D