On Mon, 16 Jul 2018 21:57:19 +0100 =?ISO-8859-1?Q?Fran=E7ois?= Guerraz
<kubr...@fgv6.net> wrote:
> Package: src:linux
> Version: 3.16.57-2
> Severity: important
>
>
> After upgrading linux-image-3.16.0-6-amd64 (3.16.57-2) over (3.16.56-
> 1+deb8u1) on a VM host and its guests, the guests were not able to
> boot-up any more (see Guest Kernel Log below).
>
> I found a workaround which is to change the cpu of the host from
> <cpu mode='host-model'>
> <model fallback='allow'/>
> </cpu>
> to
> <cpu mode='custom' match='exact'>
> <model fallback='allow'>SandyBridge</model>
> </cpu>
[...]
We have the same problem. And the guests were not able to boot-up no matter the
vm host had installed the current intel-microcode or not. Guests will reboot
immediately after boot message showing 'Booting SMP configuration'
** Guest Kernel log:
[ 0.302539] x86: Booting SMP configuration:
[ 0.302541] .... node #1, CPUs: #1
Some Workaround we found:
1. Start the guest with nosmp kernel option or only one cpu config, it can do a
normal boot-up.
2. Downgrade the vm host kernel version or Downgrade the guest kernel, Both of
them work.
2. Change the cpu type of guest to custom. It also works.
<cpu mode='host-model'>
<model fallback='allow'/>
</cpu>
to
<cpu mode='custom' match='exact'>
<model fallback='allow'>SandyBridge</model>
</cpu>
