Hi jgfrm, On 01/06/2018 06:41 PM, jgfrm wrote: > Package: linux-image-4.9.0-5-amd64 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > Upgrade of linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64 > > * What exactly did you do (or not do) that was effective (or > ineffective)? > Disable hvm guest boot in hypervisor > > * What was the outcome of this action? > Guest boots in pv mode > * What outcome did you expect instead? > Use hvm mode in guest config file, such that guest boots in hvm mode > > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: 8.10 > APT prefers oldstable > APT policy: (500, 'oldstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) >
The first step here is to collect more information. Things that are or are not working with Xen setups can be difficult to track down, since it can be related to any combination of anything like hardware, hypervisor, dom0, domU etc... >From your description I guess that changing domU from linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64 while all other things remain the same caused the issue. Is that right? ---- I see you're using Debian Release: 8.10, which might imply Xen 4.4 and the jessie kernel for the dom0. As seen from the dom0, can you please reply with `uname -a`, `xen info` and `lspci -v` output. Since the domU is running linux-image-4.9.0-5-amd64 that can only mean it's the kernel update just done, which is version 4.9.65-3+deb9u2 When reporting kernel versions, note that the package name and the actual version can be different. So please always include the real package version, like 4.9.65-3 or whatever in case of linux-image-4.9.0-4-amd64. Anything you could do yourself to narrow down the issue would help. With enough information, someone else might be able to reproduce the same situation and confirm the issue. Hans van Kranenburg
