Re: [Qemu-ppc] Error in Linux Kernel Booting

[tomy]

Alex,
         Thanks for your input. The Linux is booting  and it is giving an error during the file system mounting

VFS: Cannot open root device "sda" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Call Trace:
[b701ddc0] [b00072e4] show_stack+0x44/0x160 (unreliable)
[b701de00] [b06bec5c] panic+0xe0/0x230
[b701de60] [b088bd08] mount_block_root+0x1c8/0x26c
[b701deb0] [b088bff0] mount_root+0x10c/0x120
[b701def0] [b088c1a8] prepare_namespace+0x1a4/0x1f0
[b701df00] [b088b974] kernel_init_freeable+0x1b8/0x1cc
[b701df30] [b00028c4] kernel_init+0x14/0x110
[b701df40] [b000f1c0] ret_from_kernel_thread+0x64/0x6c
Rebooting in 180 seconds..

I had given the following command and the file system type using is ext3

qemu-system-ppc -cpu e500mc -M ppce500 -kernel ./uImage_new -hdc ./rootfs-f10-dev -append "root=/dev/sda console=ttyS0" -nographic

is there anything wrong in the command which I am giving

Regards,
Tomy

On 2/3/2015 3:15 PM, Alexander Graf wrote:

On 03.02.15 10:29, tomy wrote:

Hi,
        I am trying to simulate free scale P2040 Linux in Ubuntu Linux
(using QEMU). I am using the following command for booting the Freescale
P2040  linux from Ubuntu system

qemu-system-ppc -M ppce500 -kernel ./uImage_new -append "root=0800
console=tty0" -nographic

I am getting the following boot log

/Using QEMU e500 machine description//
//Memory CAM mapping: 64/64 Mb, residual: 0Mb//
//Linux version 3.8.13-rt9 (address@hidden) (gcc version 4.6.2 (GCC) )
#250 SMP Tue Feb 3 13:55:21 IST 2015//
//CPU maps initialized for 1 thread per core//
//bootconsole [udbg0] enabled//
//setup_arch: bootmem//
//qemu_e500_setup_arch()//
//arch: exit//
//Zone ranges://
//  DMA      [mem 0x00000000-0x07ffffff]//
//  Normal   empty//
//Movable zone start for each node//
//Early memory node ranges//
//  node   0: [mem 0x00000000-0x07ffffff]//
//MMU: Allocated 1088 bytes of context maps for 255 contexts//
//PERCPU: Embedded 8 pages/cpu @b0aab000 s9024 r8192 d15552 u32768//
//Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
32512//
//Kernel command line: root=0800 console=tty0//
//PID hash table entries: 512 (order: -1, 2048 bytes)//
//Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)//
//Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)//
//Memory: 53952k/131072k available (9032k kernel code, 77120k reserved,
304k data, 547k bss, 284k init)//
//Kernel virtual memory layout://
//  * 0xfffdf000..0xfffff000  : fixmap//
//  * 0xfdffe000..0xfe000000  : early ioremap//
//  * 0xb9000000..0xfdffe000  : vmalloc & ioremap//
//Hierarchical RCU implementation.//
//    RCU debugfs-based tracing is enabled.//
//    RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.//
//NR_IRQS:512 nr_irqs:512 16//
//mpic: Setting up MPIC " OpenPIC  " version 1.2 at e0040000, max 1 CPUs//
//mpic: ISU size: 256, shift: 8, mask: ff//
//mpic: Initializing for 256 sources//
//clocksource: timebase mult[2800000] shift[24] registered//
//Console: colour dummy device 80x25//
//console [tty0] enabled, bootconsole disabled/

tty0 is a graphical console for which I don't see a backing device. Why
don't you just use ttyS0?

Also you probably want to pass -cpu e500mc to the command line to make
sure you get the correct guest CPU type.


Alex

"Disclaimer: This message is being sent from Kalki Communication Technologi
es
Pvt Ltd (KALKITECH). and may contain information which is confidential 
or 

privileged. If you are not the intended recipient, please advise th
e sender
immediately by reply e-mail and delete this message and any attac
hments 

without retaining a copy. Any unauthorized use of the content o
f this message
can expose the responsible party to civil and/or criminal p
enalties, 

and may constitute a more serious offense. Further the compa
ny does not accept
liability for any errors, omissions, viruses or compute
r problems 

experienced as a result of this transmission. If you have r
eceived this
message in error, notice is hereby given that no representati
on, contract or 

other binding obligation shall be created by this e-ma
il."