It might be related to this:
https://bugzilla.redhat.com/show_bug.cgi?id=1584775
On Wed, Aug 8, 2018 at 7:49 AM, Nir Soffer wrote:
> On Sun, Aug 5, 2018 at 1:40 PM Paul.LKW wrote:
>
>> Dear All:
>> I just upgraded my oVIrt-4.2.4 to 4.2.5 and nightmare begin, FreeBSD VMs
>> hangs once the VM's
On Sun, Aug 5, 2018 at 1:40 PM Paul.LKW wrote:
> Dear All:
> I just upgraded my oVIrt-4.2.4 to 4.2.5 and nightmare begin, FreeBSD VMs
> hangs once the VM's VirtIO harddisk is some loading (eg. extracting a
> big tar ball, portsnap extract, etc.), I tried to create a VMs using
> back the IDE do
I forgot to mention the Monitor, if available.
The "info status" would give you a lean status of the VM: either
running or paused.
I think the best way is QMP and, of course, the qemu-guest-agent
running inside the VM.
2018-08-07 17:32 GMT+02:00 Vincenzo Romano :
> Ping cannot be a solution.
> If
Ping cannot be a solution.
If you have QMP in place, just issue a "query-status".
If not, you need to use the ol' school VNC console (or whatever applies).
--
Vincenzo Romano
Il mar 7 ago 2018, 17:27 司兵松 ha scritto:
>
> Hello everyone,
>
> How can i detect a vm is crashed on the host via
Hello everyone,
How can i detect a vm is crashed on the host via command. Because of
network isolation, ping cannot do this.
Thank you for your time.
