The key point here is that you're using the OS's own utilities to configure
things. The virtualization layer only provides as much as the hardware would on
bare iron. Everything else is the responsibility of whatever OS you're
installing in the VM.
Regards,
Tres
Tres Wong-Godfrey
driver schema or just try plugging in the old driver.
Thanks so much for your time and any clarity you can give on this.
And I do apologize if there is an RTFM answer for this; if there is, I haven't
had much luck finding it.
Regards,
Tres
Tres Wong-Godfrey
___
On Sep 7, 2010, at 1:35 PM, Shi Jin wrote:
> Right. I actually commented out the delete action since some failure
> shouldn't cause a deletion.
Yeah, I actually did the same. I'm hoping to see a "PERSISTENT_VM" lifecycle or
something that could be configured from the one conf file.
> I guess
On Sep 7, 2010, at 11:54 AM, Shi Jin wrote:
> In short, after rescuing a failed VM, how to bring it back to OpenNebula?
Hi Shi,
Not sure about OpenNebula 2.0, but in 1.4, the lifecycle manager actually
automatically deletes a VM immediately upon falling into a failed state; all
that remains o