Hi, please allow me to dive in here, i do have a very similar problem.
one of my VPS is running on a providers host system, that seems to use an old Xen version, which can't boot the Jessie-Kernel. at the moment im using the wheezy-Kernel on jessie, but that's not the best solution... do i have to self-build the kernel or is there another way to get an uncompressed oder gz-compressed kernel? (building it from upstream is easy, is there a guide to build it directly from debians sources?) i have no influence on the host system whatsoever and even need to contact their support, if the boot fails - like it does with jessies kernel. Regards Andreas Am 05.02.2016 um 12:05 schrieb Ian Campbell: > On Thu, 2016-02-04 at 15:40 -0200, Tiago Ilieve wrote: >> Sorry for the delay in my response. In the past couple days I was >> confirming with Oracle if my findings (using virt-what, as you >> suggested) where right and, indeed, they are supporting Xen HVM right >> now. > > Great! > >> >> So, there's no need for an uncompressed/gzipped kernel anymore and the >> default one boots just fine. Although I'm still curious regarding the >> possibility of booting an uncompressed kernel on >> native/full-virtualization, I guess this does not makes sense. > > WRT virtualisation, not in general no. > > If possible you really want to do the decompression in guest context, to > avoid issues with potentially malicious compressed binaries. > > For native there generally isn't much point, but for x86 at least there is > also a bunch of necessary setup and gathering of information (e.g. from the > BIOS in 16 bit mode) which is done in the same preamble as where the > decompressor runs (more or less) and which you would need to replicate > before booting the uncompressed image's entry point -- it's really not > worth the effort in general. > >> I'm really thankful for you support and inclination to help us on the >> matter. > > No problem! > > Ian. >
