On Thu, 2015-11-26 at 14:17 +0100, Stefan Bader wrote: > On 19.11.2015 11:00, Ian Campbell wrote: > > On Wed, 2015-11-18 at 23:07 +0000, Thomas Jepp wrote: > > > > > > [...] > > > xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' > > > (2 = No such file or directory): Internal error > > > > This is the wrong path, in the Debian packages it should be > > /usr/lib/xen- > > 4.6/boot/hvmloader (and this should be arranged by the packaging, i.e. > > it > > is not a configuration error on your part). > > > > However not only is the toolstack using the wrong path but the file > > seems > > to be missing from the package entirely according to > > https://packages.debian.org/sid/amd64/xen-utils-4.6/filelist > > > > So FWIW the attached patch gets me hvmloader into the right place _and_ also > reflects the correct paths in the generated libxenlight.pc which otherwise > would > likely cause the next round of issues. @XENFIRMWAREDIR@ in config/Paths.mk.in > was part of the same change to add pkg-config files. > > commit babeca328413baebfdca366a5b17c06acf4295e8 > Author: Wei Liu <[email protected]> > Date: Fri Jan 9 14:32:18 2015 +0000 > > libxl: provide xenlight.pc > > Still not really sure this is the supposed way to set things right. There does > not seem to be a better way to override the firmware directory (as far as I > can > see)...
I think that's the only way right now, anything better would need to be arranged upstream. Ian.
