As far as I can tell, yes the package builds properly. I installed following
Boris' directions, which again have always been totally correct, as far as I
can tell. The "missing" qemu-dm issue is probably due to some distros using a
separate lib64 directory while others do not. I spent about 10 minutes looking
around in tools/ioemu-qemu-xen, but saw nothing that would tell me how to
select lib64 for install. Running #file qemu-dm shows a 64-bit binary in
dist/install/usr/lib/xen/bin, so the build seems to be doing the right thing;
its just install that is not getting the right directory for a Fedora distro?
The target box was formerly used for developing our own hypervisor code, but
any stray settings from that were overwritten (I hope) by formatting the drives
during installation of F13.
On Sep 4, 2010, at 8:20 AM, Pasi Kärkkäinen wrote:
> On Fri, Sep 03, 2010 at 08:41:52AM -0400, John McDermott (U.S. Navy Employee)
>> Xen Users,
>> When trying to install a 64-bit Fedora 13 HVM on 64-bit Xen 4.0.1, built
>> using the xen-4.0.1-0.2.fc13.src.rpm from http://pasik.reaktio.net,
>> virt-install complains that it cannot find /usr/lib64/xen/bin/qemu-dm. This
>> is not surprising, since there is no corresponding emulator file in the
>> BUILD/xen-4.0.1/dist directory structure, just the 32-bit
>> lib/xen/bin/qemu-dm file. Has anyone else seen this problem, or should I
>> tinker with the .spec file myself?
> Are you sure the rpms got built/installed properly?
> Did you check the required packages from:
> that xen-4.0.1-0.2.fc13.src.rpm on my site is downloaded from Fedora koji.
> -- Pasi
> Xen-users mailing list
What is the formal meaning of the one-line program
J.P. McDermott building 12
Code 5542 mcdermott@xxxxxxxxxxxxxxxx
Naval Research Laboratory voice: +1 202.404.8301
Washington, DC 20375, US fax: +1 202.404.7942
Xen-users mailing list