Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

On 01/07/2018 06:42 PM, Michael Stone wrote: > retitle 886491 linux-image-4.9.0-5-amd64: Does not boot as Xen guest in > PVH mode > thanks > > HVM and PVH are two different modes. The fix suggested in this bug > report (commenting out pvh=1 in the conf file) points to the problem > being the

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

retitle 886491 linux-image-4.9.0-5-amd64: Does not boot as Xen guest in PVH mode thanks HVM and PVH are two different modes. The fix suggested in this bug report (commenting out pvh=1 in the conf file) points to the problem being the latter. I can confirm that PVH guests fail to boot using

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

> -Oorspronkelijk bericht- > Van: Hans van Kranenburg [mailto:h...@knorrie.org] > Verzonden: zondag 7 januari 2018 00:27 > Aan: frm ; 886...@bugs.debian.org > Onderwerp: Re: Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as > Xen guest in HVM mode > > Hi, > >

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

Hi, Please reply-all and not only to me. On 01/07/2018 12:07 AM, frm wrote: >> 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

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

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

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

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)