On Sat, Aug 25, 2012 at 5:08 PM, lei yang <yanglei.fage@xxxxxxxxx> wrote: > On Sat, Aug 25, 2012 at 2:47 PM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote: >> On Sat, Aug 25, 2012 at 2:34 AM, lei yang <yanglei.fage@xxxxxxxxx> wrote: >>> I used the redhat RHEL6 boot with initrd but it failed, can sb help me >>> ( I have tried /dev/ram /dev/ram0 and >>> initrd-2.6.32-279.el6.x86_64kdump.img) >>> >>> [root@localhost boot]# /usr/libexec/qemu-kvm --enable-kvm -smp 8 -m >>> 1024 -net nic,model=virtio -net tap,script=/etc/qemu-ifup -initrd >>> /boot/initramfs-2.6.32-279.el6.x86_64.img -kernel >>> /boot/vmlinuz-2.6.32-279.el6.x86_64 -append "root=/dev/ram rw >>> console=ttyS0,115200 " -nographic >> >> What are you trying to do? >> >> A kernel and initramfs have been specified. The boot is working up >> until the point where the initramfs wants to mount the root file > > Is there a way to see the contents from initramfs? and it seems > initrmafs contains > the kernel modules not contain the rootfs > > For redhat, how chould I get a rootfs for guest use? Normally the root file system is on disk and has been put there by the installer. You haven't described what you are trying to do, but maybe you just want to test guest OS booting. In that case you could use a Live CD (Fedora, Debian, etc) or try TinyCore (12 MB): http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/TinyCore-current.iso Some people also use QEMU's -drive snapshot feature to boot a system identical to their host. Changes made inside the guest are not saved to disk: qemu-kvm -m 1024 -snapshot -drive if=virtio,cache=unsafe,file=/dev/sda Which option works best depends on what you are trying to do. Stefan -- 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
