Hi Daniel, On Tue 19 Aug 2014 (14:32), Daniel P. Berrange wrote:
On Tue, Aug 19, 2014 at 01:54:12PM +0200, Alvaro Lopez Garcia wrote:
According to the Xen documentation the full path was only needed for versions prior to 4.1: "Note: For older versions of Xen Project software (4.1 or earlier) you need to know where in the filesystem pygrub lies. (...) Newer versions of the toolstack know how to look for the path themselves." [1]
Regardless of whether they know how to find the path, it is expected that the libvirt XML is including/requiring the full path. So I'm not really considering this a bug that needs fixing
- Is it required that all the libvirt XML files needing a bootloader specify one? or - If the bootloader is specified, then it has to be a full path? If it is the former case, we have been running libvirt with xend without specifying a bootloader in the XML files for a long time. We only have found issues when we switched our hypervisors from xend to libxl. Also, if we install the bootloader in the current hardcoded path (i.e. /usr/bin/pygrub/) the guests will be able to be booted again without including a bootloader in the XML file. If it is the later, currently we are specifying it without the full path and it is working (i.e. <bootloader>pygrub</bootloader>). Thank you for your time, -- Álvaro López García aloga@ifca.unican.es Instituto de Física de Cantabria http://alvarolopez.github.io Ed. Juan Jordá, Campus UC tel: (+34) 942 200 969 Avda. de los Castros s/n 39005 Santander (SPAIN)