From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: qemu-kvm and initrd Date: Tue, 14 Sep 2010 09:38:13 -0600 Message-ID: <4C8F96E5.4040707@cisco.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Nirmal Guhan Return-path: Received: from sj-iport-4.cisco.com ([171.68.10.86]:45969 "EHLO sj-iport-4.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750932Ab0INPiO (ORCPT ); Tue, 14 Sep 2010 11:38:14 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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) 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >