[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] what's wrong with mey qemu-kvm

From: Mike Lovell
Subject: Re: [Qemu-discuss] what's wrong with mey qemu-kvm
Date: Fri, 24 Aug 2012 20:49:23 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0

On 08/24/2012 07:30 PM, lei yang wrote:

I used the redhat RHEL6 boot with initrd but it failed, can sb help me

address@hidden 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

dracut Warning: No root device "block:/dev/ram" found

dracut Warning: Boot has failed. To debug this issue add "rdshell" to
the kernel command line.

dracut Warning: Signal caught!

dracut Warning: Boot has failed. To debug this issue add "rdshell" to
the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-279.el6.x86_64 #1
Call Trace:
  [<ffffffff814fd11a>] ? panic+0xa0/0x168
  [<ffffffff81070bd2>] ? do_exit+0x862/0x870
  [<ffffffff8117ca75>] ? fput+0x25/0x30
  [<ffffffff81070c38>] ? do_group_exit+0x58/0xd0
  [<ffffffff81070cc7>] ? sys_exit_group+0x17/0x20
  [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b

the system is complaining that it can't find a block device to mount the root filesystem from. you specify "root=/dev/ram" which isn't something that exists. /dev/ram0 does but you probably don't want to use it since its just a ram backed device with probably nothing in it. you also don't define a disk for the guest to use so there isn't another block device to mount as the root filesystem.

you need to get a system for the guest to boot. this can be done by creating a virtual disk with qemu-img, attaching the virtual disk and a rhel installation cd to the guest, and going though a rhel installation. if you aren't sure what that means, you should probably use virt-manager to configure your vm.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]