(forgot to reply all) On Fri, Nov 28, 2008 at 1:44 PM, Alan Pevec <<a href="mailto:apevec@gmail.com">apevec@gmail.com</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Fri, Nov 28, 2008 at 1:23 PM, Vigneswaran R <<a href="mailto:vignesh@atc.tcs.com" target="_blank">vignesh@atc.tcs.com</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> We were also facing the same problem. We solved the problem by recreating the initrd file. Details, 1. mount the ovirt-appliance image # nohup qemu-nbd /var/lib/libvirt/images/ovirt-appliance.img & # modprobe nbd # nbd-client localhost 1024 /dev/nbd0 # kpartx -a /dev/nbd0 # mount /dev/mapper/nbd0p2 /mnt # mount /dev/mapper/nbd0p1 /mnt/boot 2. do a chroot, backup the initrd image and recreate it # chroot /mnt # mv /boot/initrd-2.6.26.6-79.fc9.i686 /root # mkinitrd /boot/initrd-2.6.26.6-79.fc9.i686 2.6.26.6-79.fc9.i686 # exit 3. unmount # umount /mnt # kpartx -d /dev/nbd0 # nbd-client -d /dev/nbd0 4. boot the machine # virsh start ovirt-appliance It solved our problem. ref: <a href="http://ovirt.org/page/TroubleShooting" target="_blank">http://ovirt.org/page/TroubleShooting</a> </blockquote></div> </div>Excellent, thanks for solving this! It's strange that appliance-creator produced broken i386 initrd while x86_64 is ok and there were no errors reported in the build log. I'll take special care of i386 when doing the next build. Cheers, Alan </blockquote></div>