On Mon, 2018-07-16 at 21:57 +0100, François Guerraz 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> [...] Do you have the current intel-microcode installed on the VM host? (This shouldn't happen in either case, but it may help to track down the bug. I originally tested on a desktop Sandy Bridge system with the updated microcode installed.) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part