On Thu, Jul 10, 2008 at 12:07:18AM +0100, John Levon wrote:
Why is it NULL instead of the path to pygrub? On Solaris, the path is
different.
Loader is refering specifically to the loader tag which is a BIOS
firmware blob. It seems we've not specified any tag in the capabilities
for bootloader
On Thu, Jul 10, 2008 at 12:07:18AM +0100, John Levon wrote:
Why is it NULL instead of the path to pygrub? On Solaris, the path is
different.
You mean that when dumping the capabilities on a Xen host
the sections
guest
os_typexen/os_type
arch ...
don't have a loader section under
On Thu, Jul 10, 2008 at 09:08:33AM +0100, Daniel P. Berrange wrote:
On Thu, Jul 10, 2008 at 12:07:18AM +0100, John Levon wrote:
Why is it NULL instead of the path to pygrub? On Solaris, the path is
different.
Loader is refering specifically to the loader tag which is a BIOS
firmware
Why is it NULL instead of the path to pygrub? On Solaris, the path is
different.
regards
john
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list