Jan Beulich writes ("[PATCH] libxc: don't fail domain creation when unpacking initrd fails"): > At least Linux kernels have been able to work with gzip-ed initrd for > quite some time; initrd compressed with other methods aren't even being > attempted to unpack. Furthermore the unzip-ing routine used here isn't > capable of dealing with various forms of concatenated files, each of > which was gzip-ed separately (it is this particular case which has been > the source of observed VM creation failures).
I'm not sure I really like this approach of attempting to ungzip it and then falling back. (And the size-checking logic is not particularly easy to follow.) Is there no way to tell that a kernel supports gzipped initrds by looking at the kernel ? A heuristic would probably do: it's OK if we sometimes insist on decompression ourselves, for a subset of old kernels where it's not needed. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel