[Ovirt-devel] Re: ovirt-appliance panic on boot
apevec at gmail.com
Fri Nov 28 12:45:42 UTC 2008
(forgot to reply all)
On Fri, Nov 28, 2008 at 1:44 PM, Alan Pevec <apevec at gmail.com> wrote:
> On Fri, Nov 28, 2008 at 1:23 PM, Vigneswaran R <vignesh at atc.tcs.com>wrote:
>> We were also facing the same problem. We solved the problem by
>> recreating the initrd file.
>> 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-184.108.40.206-79.fc9.i686 /root
>> # mkinitrd /boot/initrd-220.127.116.11-79.fc9.i686 18.104.22.168-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: http://ovirt.org/page/TroubleShooting
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ovirt-devel