qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] QEMU 1.2.0 -hda option not working


From: Fam Zheng
Subject: Re: [Qemu-devel] QEMU 1.2.0 -hda option not working
Date: Fri, 9 Nov 2012 16:19:01 +0800

I'm wondering if the interface might be IDE in this case?

---
Best regards!
Fam Zheng


On Fri, Nov 9, 2012 at 4:09 PM, Vipin Gahlaut <address@hidden> wrote:
> Hi Fam,
>
> My understanding is that I need to include SCSI driver support in kernel
> that I already did. Do I need to include something else as well?
>
> Best Regards
> Vipin
>
>
> On Fri, Nov 9, 2012 at 1:35 PM, Fam Zheng <address@hidden> wrote:
>>
>> Is the device driver compiled in the kernel?
>>
>> ---
>> Best regards!
>> Fam Zheng
>>
>>
>> On Fri, Nov 9, 2012 at 3:59 PM, Vipin Gahlaut <address@hidden> wrote:
>> > Hi Dunrong,
>> >
>> > I tried your suggestion but it is not working. Please find more details
>> > below.
>> >
>> > 1. I have created image using qemu-img command (qemu-img create
>> > -disk.img
>> > 1G), loop mounted it and installed root file system on this image.
>> >
>> > 2. I am using linux kernel 3.5.5 and made sure that SCSI support is
>> > included
>> > in the kernel. Using QEMU 1.2.0
>> >
>> > 3. Running QEMU as below
>> >
>> > /usr/local/bin/qemu-system-arm -M versatilepb -kernel
>> > /home/vgahlaut/labs/linux-3.5.5/arch/arm/boot/zImage -nographic -hda
>> > /home/vgahlaut/labs/disk.img -append "root=/dev/sda mem=128M
>> > console=ttyAMA0,115200"
>> >
>> > 4.Getting Error (VFS: Cannot open root device "sda" or
>> > unknown-block(0,0):
>> > error -6). Please see complete logs below
>> > ========
>> > Uncompressing Linux... done, booting the kernel.
>> > Booting Linux on physical CPU 0
>> > Linux version 3.5.5 (address@hidden) (gcc version 4.3.2 (crosstool-NG
>> > 1.16.0) ) #21 Fri Nov 9 10:42:54 IST 2012
>> > CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
>> > CPU: VIVT data cache, VIVT instruction cache
>> > Machine: ARM-Versatile PB
>> > Memory policy: ECC disabled, Data cache writeback
>> > sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
>> > Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
>> > 32512
>> > Kernel command line: root=/dev/sda mem=128M console=ttyAMA0,115200
>> > 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: 128MB = 128MB total
>> > Memory: 126048k/126048k available, 5024k reserved, 0K highmem
>> > Virtual kernel memory layout:
>> >     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
>> >     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
>> >     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
>> >     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
>> >       .text : 0xc0008000 - 0xc0360810   (3427 kB)
>> >       .init : 0xc0361000 - 0xc0381cbc   ( 132 kB)
>> >       .data : 0xc0382000 - 0xc03a9100   ( 157 kB)
>> >        .bss : 0xc03a9124 - 0xc03c3c9c   ( 107 kB)
>> > NR_IRQS:192
>> > VIC @f1140000: id 0x00041190, vendor 0x41
>> > FPGA IRQ chip 0 "SIC" @ f1003000, 21 irqs
>> > Console: colour dummy device 80x30
>> > Calibrating delay loop... 425.16 BogoMIPS (lpj=2125824)
>> > pid_max: default: 32768 minimum: 301
>> > Mount-cache hash table entries: 512
>> > CPU: Testing write buffer coherency: ok
>> > Setting up static identity map for 0x2c2aa0 - 0x2c2af8
>> > devtmpfs: initialized
>> > NET: Registered protocol family 16
>> > Serial: AMBA PL011 UART driver
>> > dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a PL011 rev1
>> > console [ttyAMA0] enabled
>> > dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a PL011 rev1
>> > dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a PL011 rev1
>> > fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 38) is a PL011 rev1
>> > bio: create slab <bio-0> at 0
>> > SCSI subsystem initialized
>> > Advanced Linux Sound Architecture Driver Version 1.0.25.
>> > Switching to clocksource timer3
>> > NET: Registered protocol family 2
>> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>> > TCP established hash table entries: 4096 (order: 3, 32768 bytes)
>> > TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
>> > TCP: Hash tables configured (established 4096 bind 4096)
>> > TCP: reno registered
>> > UDP hash table entries: 256 (order: 0, 4096 bytes)
>> > UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
>> > NET: Registered protocol family 1
>> > RPC: Registered named UNIX socket transport module.
>> > RPC: Registered udp transport module.
>> > RPC: Registered tcp transport module.
>> > RPC: Registered tcp NFSv4.1 backchannel transport module.
>> > NetWinder Floating Point Emulator V0.97 (double precision)
>> > Installing knfsd (copyright (C) 1996 address@hidden).
>> > jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
>> > ROMFS MTD (C) 2007 Red Hat, Inc.
>> > msgmni has been set to 246
>> > Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
>> > io scheduler noop registered
>> > io scheduler deadline registered
>> > io scheduler cfq registered (default)
>> > clcd-pl11x dev:20: >PL110 rev0 at 0x10120000
>> > clcd-pl11x dev:20: >Versatile hardware, VGA display
>> > Console: switching to colour frame buffer device 80x60
>> > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> > brd: module loaded
>> > physmap platform flash device: 04000000 at 34000000
>> > physmap-flash.0: Found 1 x32 devices at 0x0 in 32-bit bank. Manufacturer
>> > ID
>> > 0x000000 Chip ID 0x000000
>> > Intel/Sharp Extended Query Table at 0x0031
>> > Using buffer write method
>> > smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <address@hidden>
>> > eth0: SMC91C11xFD (rev 1) at c8886000 IRQ 25 [nowait]
>> > eth0: Ethernet addr: 52:54:00:12:34:56
>> > mousedev: PS/2 mouse device common for all mice
>> > i2c /dev entries driver
>> > mmci-pl18x fpga:05: >mmc0: PL181 manf 41 rev0 at 0x10005000 irq 22,33
>> > (pio)
>> > mmci-pl18x fpga:0b: >mmc1: PL181 manf 41 rev0 at 0x1000b000 irq 23,34
>> > (pio)
>> > input: AT Raw Set 2 keyboard as /devices/fpga:06/serio0/input/input0
>> > aaci-pl041 fpga:04: >ARM AC'97 Interface PL041 rev0 at 0x10004000, irq
>> > 24
>> > aaci-pl041 fpga:04: >FIFO 512 entries
>> > TCP: cubic registered
>> > NET: Registered protocol family 17
>> > VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
>> > ALSA device list:
>> >   #0: ARM AC'97 Interface PL041 rev0 at 0x10004000, irq 24
>> > input: ImExPS/2 Generic Explorer Mouse as
>> > /devices/fpga:07/serio1/input/input1
>> > 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:
>> > 1f00           65536 mtdblock0  (driver?)
>> > Kernel panic - not syncing: VFS: Unable to mount root fs on
>> > unknown-block(0,0)
>> > [<c00199f0>] (unwind_backtrace+0x0/0xf4) from [<c02c0a8c>]
>> > (panic+0x6c/0x1cc)
>> > [<c02c0a8c>] (panic+0x6c/0x1cc) from [<c0361f8c>]
>> > (mount_block_root+0x178/0x238)
>> > [<c0361f8c>] (mount_block_root+0x178/0x238) from [<c03620cc>]
>> > (mount_root+0x80/0x100)
>> > [<c03620cc>] (mount_root+0x80/0x100) from [<c0362264>]
>> > (prepare_namespace+0x118/0x1ec)
>> > [<c0362264>] (prepare_namespace+0x118/0x1ec) from [<c03614cc>]
>> > (kernel_init+0x144/0x1d4)
>> > [<c03614cc>] (kernel_init+0x144/0x1d4) from [<c0015348>]
>> > (kernel_thread_exit+0x0/0x8)
>> >
>> > Best Regards
>> > Vipin
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Nov 9, 2012 at 7:39 AM, Dunrong Huang <address@hidden>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> 2012/11/8 Vipin Gahlaut <address@hidden>
>> >>>
>> >>> Hi Experts,
>> >>>
>> >>> I am using qemu 1.2.0  and using arm versatilepb model. I am
>> >>> spevifying
>> >>> -hda hdd.img but linux is not able to recognize hard disk. I do not
>> >>> see it
>> >>> in device nodes. NONE of below exist in device nodes
>> >>
>> >>
>> >> try following command:
>> >> qemu-system-arm ... your-qemu-option ... -append "root=/dev/sda
>> >> mem=256"
>> >>>
>> >>>
>> >>> /dev/sda
>> >>> /dev/sda1
>> >>> /dev/hda
>> >>> /dev/hda1
>> >>>
>> >>> Can anyone please help?
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Best Regards,
>> >>
>> >> Dunrong Huang
>> >
>> >
>
>



reply via email to

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