Re: [Xen-devel] [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume device

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct resume 
device"):
> On Fri, Oct 20, 2017 at 02:42:53PM +0100, Ian Jackson wrote:
> > Wei Liu writes ("Re: [OSSTEST PATCH 11/16] ts-debian-fixup: use correct 
> > resume device"):
> > I'm not sure what you mean here.  We are using the config template
> > provided by xen-tools.  The reuse of the host's initrd is suggested by
> > the xen-create-image documentation.
> 
> TBH I don't know what to write in a report. What is the expected
> behaviour?

How about this ?  Adjust to taste, correcting any
lies/misunderstandings, maybe adding references, etc.


Steps to reproduce:

  Follow instructions in xen-create-image, including suggestion to
  re-use host's initrd, to make a guest running stretch.  Try to boot
  it.

Expected behaviour:

  Guest boots promptly.

Observed behaviour:

  Guest pauses for a long time during boot waiting for the "resume
  device" to become available.

Analysis:

  This is because the initrd has the host's swap device configured.

  With stretch, and systemd, the delay is longer; earler Debian
  releases had a similar issue but the shorter timeout meant it was a
  less serious problem.

Suggested remedy:

  It is unfortunate that the initrd has the resume device baked into
  it.  Normally this kind of thing (eg root=) comes via the command
  line.  So maybe the bug is in the initrd generation.

  Alternatively, maybe xen-create-image should write a setting "extra"
  into the domain config file "resume=<swap device>".


Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel