Sebastian,
Could you be dealing with a locked screen where the first reboot command is
sending a "ctl-alt-del" that unlocks the screen and the second reboot command
send a second "ctl-alt-del" that is actually telling Windows-10 to reboot?
One way that might be useful to see if that is th
Sebastian,
Could you be dealing with a locked screen where the first reboot command is
sending a "ctl-alt-del" that unlocks the screen and the second reboot command
send a second "ctl-alt-del" that is actually telling Windows-10 to reboot?
One way that might be useful to see if that is th
All the 8 Windows 10 vm's I have will only reboot if I issue the reboot
command twice. They simply don't react on the first reboot command. I
use virsh to issue the command - but I am guessing it is nothing to do
with virsh itself (but I am ready to be corrected on this). Has anybody
else seen
* Laszlo Ersek (ler...@redhat.com) wrote:
> CC Dave
>
> On 03/01/18 12:21, Thomas Lamprecht wrote:
> > Hi,
> >
> > I'm currently evaluating how to update the firmware (OVMF) code image
> > without impacting a KVM/QEMU VM on live migration. I.e., the FW code lives
> > under /usr/share/OVMF/OVMF_CO
CC Dave
On 03/01/18 12:21, Thomas Lamprecht wrote:
> Hi,
>
> I'm currently evaluating how to update the firmware (OVMF) code image
> without impacting a KVM/QEMU VM on live migration. I.e., the FW code lives
> under /usr/share/OVMF/OVMF_CODE.fd and gets passed to the QEMU command with:
>
> qemu-
