[Xen-devel] On x86_64, failed to create hvm guest with xmexample

To:	<xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] On x86_64, failed to create hvm guest with xmexample.hvm -- Xen #18089
From:	"Li, Haicheng" <haicheng.li@xxxxxxxxx>
Date:	Tue, 22 Jul 2008 13:06:43 +0800
Delivery-date:	Mon, 21 Jul 2008 22:07:52 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcjruLuXgCKtcICrTQeGg2UwBp/aaw==
Thread-topic:	On x86_64, failed to create hvm guest with xmexample.hvm -- Xen #18089

Xend.log shows: VmError: (1, 'Internal error', 'Could not open kernel
image (2 = No such file or directory)')

This is a regression introduced by c/s 18077, 

In xmexample.hvm, kernel = "/usr/" + arch_libdir + "/xen/boot/hvmloader"

But, as defined in $(XEN_ROOT)/tools/Makefile:
# hvmloader is a 32-bit protected mode binary.
# It belongs in /usr/lib, not /usr/lib64.
TARGET      := hvmloader/hvmloader
INST_DIR := $(DESTDIR)/usr/lib/xen/boot


hvmloader will be installed to /usr/lib/xen/boot, so xend cannot find
hvmloader in /usr/lib64/xen/boot, which causes guest creation failure.

-- haicheng

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] On x86_64, failed to create hvm guest with xmexample.hvm --