[Lguest] /dev/vda

[Eugene Kov]

No :(
Did exactly what you said, same error. I don't understand why it is needed to make a new pseudo block when initrd-1.1-i386.img is already exists?
well I still get the same problem:

./lguest 64 ../../vmlinux --block=initrd-1.1-i386.img root=/dev/vda

[    0.000000] VFS: Cannot open root device "vda" or unknown-block(0,0)
[    0.000000] Please append a correct "root=" boot option; here are the available partitions:
[    0.000000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.000000] Pid: 1, comm: swapper Not tainted 2.6.32.15+drm33.5 #21
[    0.000000] Call Trace:
[    0.000000]  [<c0568e67>] ? printk+0x1d/0x26
[    0.000000]  [<c0568d9f>] panic+0x48/0xf3
[    0.000000]  [<c075fdab>] mount_block_root+0x264/0x2e7
[    0.000000]  [<c020f0ec>] ? sys_mknod+0x2c/0x30
[    0.000000]  [<c075fe87>] mount_root+0x59/0x5f
[    0.000000]  [<c075ffdb>] prepare_namespace+0x14e/0x192
[    0.000000]  [<c0201ca5>] ? sys_access+0x25/0x30
[    0.000000]  [<c075f3a8>] kernel_init+0x181/0x19b
[    0.000000]  [<c075f227>] ? kernel_init+0x0/0x19b
[    0.000000]  [<c0104bc7>] kernel_thread_helper+0x7/0x10
lguest: CRASH: VFS: Unable to mount root fs on unknown-block(0,0)


Debugging the panic stack showed that a call to "open_bdev_exclusive()" (located in fs/block_dev.c) is made with the "path" argument ="/dev/root".
This function calls "lookup_bdev()" that returns a "struct block_device" with device number 0 (is this what should happen?)
Then it calls "__blkget_dev()" that calls "gen_getdisk()" (located in block/genhd.c).  "gen_getdisk()" calls "kobj_lookup()" (located in drivers/base/map.c). 
"kobj_lookup()" fails to find the kobject and returns NULL, and so "get_gendisk()". "__blkget_dev()" returns with -ENXIO. "open_bdev_exclusive()" returns with ERR_PTR(-ENXIO) which eventually produces the VFS panic.

Someone has ANY idea?

Thanks a lot

Eugene

Date: Sun, 14 Nov 2010 21:55:59 +0530
From: mailme.gaurav at gmail.com
To: weigelt at metux.de; lguest at lists.ozlabs.org
Subject: Re: [Lguest] /dev/vda

well yes you can call it that. It is possible to mount the initramdisk (initramfs in ubuntu).

Did you succeed in booting the guest?

Regards,

Gaurav Kukreja.

On Sun, Nov 14, 2010 at 9:07 PM, Enrico Weigelt <weigelt at metux.de> wrote:

* Gaurav Kukreja <mailme.gaurav at gmail.com> wrote:




> I guess the /dev/vda is basically in the initramdisk. I am only guessing and

> stating in case you can make better sense out of my guess. The initramdisk

> is a pseudo filesystem that remains in the RAM, which is why "RAMDISK".



Not an pseudo-blockdevice ?







cu

--

----------------------------------------------------------------------

 Enrico Weigelt, metux IT service -- http://www.metux.de/



 phone:  +49 36207 519931  email: weigelt at metux.de

 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666

----------------------------------------------------------------------

 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme

----------------------------------------------------------------------

_______________________________________________

Lguest mailing list

Lguest at lists.ozlabs.org

https://lists.ozlabs.org/listinfo/lguest



-- 
Gaurav Kukreja

+91 997 030 1257



_______________________________________________
Lguest mailing list
Lguest at lists.ozlabs.org
https://lists.ozlabs.org/listinfo/lguest 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/lguest/attachments/20101116/55051e24/attachment.html>