Bug#727736: Latest linux-image-686-pae fail to boot a xen domU

[Regid Ichira <regid23@nt1.in>]

Package:  linux-image-686-pae
Version:  3.10+52
Severity: normal

  This version depends on linux-image-3.10-3-686-pae.  I am the
client of a xen provider.  Unfortuntely, because of that I don't have
many details.  I think there is a similar problem with both Amazon
Web Service, and another provider.  As far as I can tell, both sell
xen domU.  3.2.0-4-686-pae works for both.  With Amazon and 3.9 or
3.10, not sure which, I got The following last lines of the the
System Log:

    ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: unknown compression format
    xc_dom_bzimageloader.c:394: panic: xc_dom_probe_bzimage_kernel: unknown compression format
    ERROR Invalid kernel: xc_dom_find_loader: no loader found
    xc_dom_core.c:523: panic: xc_dom_find_loader: no loader found
    xc_dom_parse_image returned -1
    Error 9: Unknown boot failure
    Press any key to continue... 

  I tried to run a self compiled kernel out of Debian source that
would be bzip, not xz.  Or that is what I think the compression methods
were.  I hardly remember.  I think I have changed 4 settins of the
config file, from xz to bzip.  And then made a self compiled kernel.
It was a crude guess.  And did not work.  As far as I remember, I did
manage to run several self compiled kernels before that of 3.9.  I
don't have access to the to the Amazon machine any more. 
  The issue is on https://forums.aws.amazon.com/thread.jspa?threadID=127984&tstart=0https://forums.aws.amazon.com/thread.jspa?threadID=127984&tstart=0.  As can be seen, someone responded, asking if it is
solved.

  With the 2nd xen domU provider, I currently have no means to get
the boot messages.  However the domU doesn't get to a point where I
can connect to it.  I suspect, but not sure, that it is the same 
issue.  To me, it looks similar to Amazon 1/2 checks passed.  The
control panel claims the machine is offline, while the boot process
supposedly succeeded.