Daniel P. Berrangé writes:
> On Thu, Aug 27, 2020 at 10:06:25AM +0200, Milan Zamazal wrote:
>> "Daniel P. Berrange" writes:
>>
>
>> > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
>> >> Hi,
>> >>
>> >
>> >> we have a problem in oVirt that highly available VMs don't restart aft
On Thu, Aug 27, 2020 at 10:06:25AM +0200, Milan Zamazal wrote:
> "Daniel P. Berrange" writes:
>
> > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
> >> Hi,
> >>
> >
> >> we have a problem in oVirt that highly available VMs don't restart after
> >> host poweroff because Vdsm ident
"Daniel P. Berrange" writes:
> On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
>> Hi,
>>
>
>> we have a problem in oVirt that highly available VMs don't restart after
>> host poweroff because Vdsm identifies the case as a user initiated
>> shutdown (https://bugzilla.redhat.com/180
On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
> Hi,
>
> we have a problem in oVirt that highly available VMs don't restart after
> host poweroff because Vdsm identifies the case as a user initiated
> shutdown (https://bugzilla.redhat.com/1800966).
>
> When poweroff is run on the
Hi,
we have a problem in oVirt that highly available VMs don't restart after
host poweroff because Vdsm identifies the case as a user initiated
shutdown (https://bugzilla.redhat.com/1800966).
When poweroff is run on the host, libvirt-guests service takes an
action. `virsh shutdown' is run on the