Source: virt-manager Version: 1:1.4.0-3 Severity: normal Dear Maintainer,
there's a regression following a recent (say, last eight weeks) update
of the packages that provide virtual guests in the kvm/libvirt/
virt-manager stack: If a guest is to be rebooted, either by issuing the
reboot command inside, or even by selecting "Force reset" from
virt-manager's menu, the guest gets stuck in the (emulated) BIOS, and
the icon in virt-manager's list of machine turns to the "Pause" symbol,
the status word does the same.
This is independent from the guests kernel, and probably the easiest way
to reproduce it was to use an Debian installer or a grml rescue system
image, I've tried the latter with instant success.
Since I cannot reproduce this using bare qemu-system-x86_64, I assume
the problem is in the upper layers.
Regards,
Christoph
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.7 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: unable to detect
signature.asc
Description: Digital signature
