shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
3:17 a.m.
Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the shutdown
virtual machine, but when using virsh list --all and virsh list --state-shutoff, the
shutdown virtual machine did not display in the list. What is the cause of this, and how
can I display the shutdown virtual machine.
virsh # list --all
Please enter your authentication name: root
Please enter your password:
Id Name
State
----------------------------------------------------
4 win10E2
running
virsh # list --state-shutoff
Id Name
State
----------------------------------------------------
2:23 a.m.
New subject: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
Hi,
On Sun, Aug 30, 2020 at 9:55 AM Kyre <kyre(a)vcloudpoint.com> wrote:
Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the shutdown
virtual machine, but when using virsh list --all and virsh list --state-shutoff, the
shutdown virtual machine did not display in the list. What is the cause of this, and how
can I display the shutdown virtual machine.
You can't.
All oVirt-managed VMs are, in libvirt terms, transient. The meta-data
about them is kept in the engine's database, not in libvirt.
If you want this to plan for (or already are in) a case where the
engine is dead/unavailable, then you should make sure you keep regular
engine backups, so that you can restore it, and/or check about DR.
Best regards,
virsh # list --all
Please enter your authentication name: root
Please enter your password:
Id Name State
----------------------------------------------------
4 win10E2 running
virsh # list --state-shutoff
Id Name State
----------------------------------------------------
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JGFSRX5YF3G...
--
Didi
3:46 a.m.
New subject: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David <didi(a)redhat.com> wrote:
Hi,
On Sun, Aug 30, 2020 at 9:55 AM Kyre <kyre(a)vcloudpoint.com> wrote:
>
> Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot
the shutdown virtual machine, but when using virsh list --all and virsh
list --state-shutoff, the shutdown virtual machine did not display in the
list. What is the cause of this, and how can I display the shutdown virtual
machine.
You can't.
All oVirt-managed VMs are, in libvirt terms, transient. The meta-data
about them is kept in the engine's database, not in libvirt.
This is no longer the case - in 2017 we switched to persistent domains (
https://gerrit.ovirt.org/c/78046)
When the engine issues a 'destroy' call, VDSM undefines the VM
If you want this to plan for (or already are in) a case where the
engine is dead/unavailable, then you should make sure you keep regular
engine backups, so that you can restore it, and/or check about DR.
Best regards,
>
> virsh # list --all
> Please enter your authentication name: root
> Please enter your password:
> Id Name State
> ----------------------------------------------------
> 4 win10E2 running
>
> virsh # list --state-shutoff
> Id Name State
> ----------------------------------------------------
>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JGFSRX5YF3G...
--
Didi
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PD6Y4LWKVVN...
4:34 a.m.
New subject: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
On Sun, Aug 30, 2020 at 11:49 AM Arik Hadas <ahadas(a)redhat.com> wrote:
On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David <didi(a)redhat.com> wrote:
>
> Hi,
>
> On Sun, Aug 30, 2020 at 9:55 AM Kyre <kyre(a)vcloudpoint.com> wrote:
> >
> > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the
shutdown virtual machine, but when using virsh list --all and virsh list --state-shutoff,
the shutdown virtual machine did not display in the list. What is the cause of this, and
how can I display the shutdown virtual machine.
>
> You can't.
>
> All oVirt-managed VMs are, in libvirt terms, transient. The meta-data
> about them is kept in the engine's database, not in libvirt.
This is no longer the case - in 2017 we switched to persistent domains
(https://gerrit.ovirt.org/c/78046)
When the engine issues a 'destroy' call, VDSM undefines the VM
Which makes the VM transient.
I think the reason we switched to "persistent" VM was to use VM
metadata, and use more
common code paths that are less likely to break.
Even if we keep the VMs defined, you may not be able to start them
later since the storage
required by the VM may not be available on the host at the point you
start the VM later
(.e.g. after reboot). If the storage is available, starting a VM
behind engine back may lead
a split brain since the VM may be running on another host.
The right way to manage oVirt VMs is using engine API. Since we
removed the oVirt shell,
there is no easy way like virsh, but one can script this using the SDK.
Nir
> If you want this to plan for (or already are in) a case where
the
> engine is dead/unavailable, then you should make sure you keep regular
> engine backups, so that you can restore it, and/or check about DR.
>
> Best regards,
>
> >
> > virsh # list --all
> > Please enter your authentication name: root
> > Please enter your password:
> > Id Name State
> > ----------------------------------------------------
> > 4 win10E2 running
> >
> > virsh # list --state-shutoff
> > Id Name State
> > ----------------------------------------------------
> >
> >
> > _______________________________________________
> > Users mailing list -- users(a)ovirt.org
> > To unsubscribe send an email to users-leave(a)ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JGFSRX5YF3G...
>
>
>
> --
> Didi
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PD6Y4LWKVVN...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KXV3XVLZZQ7...
1575
days inactive
1577
days old
3 comments
4 participants
participants (4)
-
Arik Hadas -
Kyre -
Nir Soffer -
Yedidyah Bar David