On 09/14/10 13:38, Nirmal Guhan wrote: > On Tue, Sep 14, 2010 at 8:38 AM, David S. Ahern <daahern@xxxxxxxxx> wrote: >> >> >> On 09/14/10 00:35, Nirmal Guhan wrote: >>> Hi, >>> >>> Getting an error while booting my guest with -initrd option as in : >>> >>> qemu-kvm -net nic,macaddr=$macaddress -net tap,script=/etc/qemu-ifup >>> -m 512 -hda /root/kvm/x86/vdisk.img -kernel /root/mvroot/bzImage >>> -initrd /root/kvm/mv/ramdisk.img -append "root=/dev/ram0" >>> >>> No filesystem could mount root, tried : ext3 ext2 ext4 vfat msds iso9660 >>> Kernel panic >>> >>> #file ramdisk.img >>> #ramdisk.img: Linux rev 1.0 ext2 filesystem data (mounted or unclean) > > I tried with both initrd and initramfs. Sizes are 42314699 and > 71271136 respectively. Sizes do seem larger but I created them from > the nfsroot created as part of the build (the nfsroot works > apparently). See if you can drop the image size as a test. I had to do that recently to get the kernel/initrd/append option to work. As I recall I was getting the same error message until I dropped the initrd size. David > >> >> What's the size of ramdisk.img? >> >> David >> >> >>> >>> I tried with both above initrd and gzipped initrd but same error. >>> >>> If I try to mount the same file and do a -append "ip=dhcp >>> root=/dev/nfs rw nfsroot=xxxx:/root/kvm/mv/mnt" instead of -initrd >>> option, it works fine. So am guessing this is initrd related. >>> >>> Any help would be much appreciated. >>> >>> Thanks, >>> Nirmal >>> -- >>> To unsubscribe from this list: send the line "unsubscribe kvm" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
