On 12/10/2012, at 8:59 PM, Marco Mornati wrote:
Hello Justin,
thanks a lot for your response.
I spent some hours on the IRC channel to find out the problem.
And, in the end, it seems is impossible for OZ project to build an RHEV image if it's
installed in a virtual machine (I created a VM with aeolus to test it out).
Ahhh, yeah. That's the "needs to run on bare metal" thing
kicking in.
Have you tried the nested vm approach? That's a possible workaround
some people have reported decent success with.
Apparently it's still in in early stages of development, would be
worth trying if you haven't yet.
oVirt nesting instructions:
http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested...
Plain KVM nesting instructions:
http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-i...
(just do the "kvm_intel.nested=1" setup I think)
Does that help?
Regards and best wishes,
Justin Clift
Anyway, here the rpm output about my environment:
[root@aeolus ~]# rpm -qa | egrep
"aeolus|audrey|configure|conductor|imagefactory|iwhd|libvirt|oz" | sort
aeolus-all-0.10.4-1.fc17.noarch
aeolus-conductor-0.10.4-1.fc17.noarch
aeolus-conductor-daemons-0.10.4-1.fc17.noarch
aeolus-conductor-doc-0.10.4-1.fc17.noarch
aeolus-configure-2.6.1-1.fc17.noarch
imagefactory-1.1.1-1.fc17.noarch
imagefactory-jeosconf-ec2-fedora-1.1.1-1.fc17.noarch
imagefactory-jeosconf-ec2-rhel-1.1.1-1.fc17.noarch
iwhd-1.5-1.fc17.x86_64
libproxy-mozjs-0.4.7-4.fc17.x86_64
libvirt-0.9.11.5-3.fc17.x86_64
libvirt-client-0.9.11.5-3.fc17.x86_64
libvirt-daemon-0.9.11.5-3.fc17.x86_64
libvirt-daemon-config-network-0.9.11.5-3.fc17.x86_64
libvirt-daemon-config-nwfilter-0.9.11.5-3.fc17.x86_64
libvirt-python-0.9.11.5-3.fc17.x86_64
mozilla-filesystem-1.9-7.fc17.x86_64
oz-0.9.0-1.fc17.noarch
rubygem-aeolus-cli-0.5.0-1.fc17.noarch
rubygem-aeolus-image-0.5.0-1.fc17.noarch
totem-mozplugin-3.4.3-1.fc17.x86_64
--
Aeolus Community Manager
http://www.aeolusproject.org