> On 6 Dec 2018, at 12:30, David David <[email protected]> wrote: > > > > On 29 May 2018, at 16:08, David David <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > hi. > > > > > > How to start VM directly in hypervisor? ovirt-engine was crashed. > > > that is not supported yet > > > > > > > VM's id is known. > > > > > > vdsclient VM, hasn't argumets for starting vm. > > > Hello again > > > it does, but you need to connect storage and then supply the whole VM > > configuration which is not simple to do. > > Ok. How to do this ? > > I have access to FC storage, where VM placed
you can use the persisted libvirt definition on host where it was running last if the host just crashed (it’s removed on clean guest shutdown though). If you have it you can connect the appropriate storage domain using vdsm-client, and then start the VM using that libvirt definition. again, it’s not very easy to do. In all other cases it would have to be generated by the engine again as the OVF_STORE OVF backup is an OVF and you need libvirt’s XML so you would have to convert it first anyway, so again nothing simple to do. In disaster recovery scenrio you can just take the whole storage domain and import it into the new clean engine installation and you’ll get all the VMs it depends what you really want to do Thanks, michal > > вт, 29 мая 2018 г. в 18:53, Michal Skrivanek <[email protected] > <mailto:[email protected]>>: > > > > On 29 May 2018, at 16:08, David David <[email protected] > > <mailto:[email protected]>> wrote: > > > > hi. > > > > How to start VM directly in hypervisor? ovirt-engine was crashed. > > that is not supported yet > > > > > VM's id is known. > > > > vdsclient VM, hasn't argumets for starting vm. > > it does, but you need to connect storage and then supply the whole VM > configuration which is not simple to do. > > > > > Thanks. > > _______________________________________________ > > Users mailing list -- [email protected] <mailto:[email protected]> > > To unsubscribe send an email to [email protected] > > <mailto:[email protected]> > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > <https://www.ovirt.org/site/privacy-policy/> > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > <https://www.ovirt.org/community/about/community-guidelines/> > > List Archives: > > https://lists.ovirt.org/archives/list/[email protected]/message/SDTALWD2CHOEE5LMYXK6PTDFORBM2UUN/ > > > > <https://lists.ovirt.org/archives/list/[email protected]/message/SDTALWD2CHOEE5LMYXK6PTDFORBM2UUN/> >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/MOD74KYRTCG4WBT55SZWB6ME7H6ZO5X7/
