Hi
The recommended way is to recover the VMs manually and let the
monitorization process update the state in oned, as you describe in your
email. UNKNOWN state is to accommodate these failure situations (that may
require different recover procedures).
Note also that we can re-send from
Ruben S. Montero rsmont...@opennebula.org writes:
Hi
Hello,
[...]
Note also that we can re-send from OpenNebula a deploy action (virsh
create, in your case) with onevm boot (or through the play icon in
Sunstone) for UNKNOWN, however there is no way to send from OpenNebula a
'virsh
Hello,
I just encounter an issue with KVM based VMs when the non shared system
datastore became full.
The libvirt/kvm paused the VMs trying to write on their discs and I have
to run:
for vm in $(virsh -c qemu:///system list | awk '/paused/ {print $1}')
do
virsh -c qemu:///system
