<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
No :(<br>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?<br>well I still get the same problem:<br><br>./lguest 64 ../../vmlinux --block=initrd-1.1-i386.img root=/dev/vda<br><br>[ 0.000000] VFS: Cannot open root device "vda" or unknown-block(0,0)<br>[ 0.000000] Please append a correct "root=" boot option; here are the available partitions:<br>[ 0.000000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)<br>[ 0.000000] Pid: 1, comm: swapper Not tainted 2.6.32.15+drm33.5 #21<br>[ 0.000000] Call Trace:<br>[ 0.000000] [<c0568e67>] ? printk+0x1d/0x26<br>[ 0.000000] [<c0568d9f>] panic+0x48/0xf3<br>[ 0.000000] [<c075fdab>] mount_block_root+0x264/0x2e7<br>[ 0.000000] [<c020f0ec>] ? sys_mknod+0x2c/0x30<br>[ 0.000000] [<c075fe87>] mount_root+0x59/0x5f<br>[ 0.000000] [<c075ffdb>] prepare_namespace+0x14e/0x192<br>[ 0.000000] [<c0201ca5>] ? sys_access+0x25/0x30<br>[ 0.000000] [<c075f3a8>] kernel_init+0x181/0x19b<br>[ 0.000000] [<c075f227>] ? kernel_init+0x0/0x19b<br>[ 0.000000] [<c0104bc7>] kernel_thread_helper+0x7/0x10<br>lguest: CRASH: VFS: Unable to mount root fs on unknown-block(0,0)<br><br><br>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".<br>This function calls "lookup_bdev()" that returns a "struct block_device" with device number 0 (is this what should happen?)<br>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). <br>"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.<br><br>Someone has ANY idea?<br><br>Thanks a lot<br><br>Eugene<br><br>Date: Sun, 14 Nov 2010 21:55:59 +0530<br>From: mailme.gaurav@gmail.com<br>To: weigelt@metux.de; lguest@lists.ozlabs.org<br>Subject: Re: [Lguest] /dev/vda<br><br>well yes you can call it that. It is possible to mount the initramdisk (initramfs in ubuntu).<br><br>Did you succeed in booting the guest?<br><br>Regards,<br><br>Gaurav Kukreja.<br><br><div class="ecxgmail_quote">On Sun, Nov 14, 2010 at 9:07 PM, Enrico Weigelt <span dir="ltr"><<a href="mailto:weigelt@metux.de">weigelt@metux.de</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="padding-left: 1ex;"><div class="ecxim">* Gaurav Kukreja <<a href="mailto:mailme.gaurav@gmail.com">mailme.gaurav@gmail.com</a>> wrote:<br>
<br>
> I guess the /dev/vda is basically in the initramdisk. I am only guessing and<br>
> stating in case you can make better sense out of my guess. The initramdisk<br>
> is a pseudo filesystem that remains in the RAM, which is why "RAMDISK".<br>
<br>
</div>Not an pseudo-blockdevice ?<br>
<br>
<br>
<br>
cu<br>
--<br>
----------------------------------------------------------------------<br>
Enrico Weigelt, metux IT service -- <a href="http://www.metux.de/" target="_blank">http://www.metux.de/</a><br>
<br>
phone: +49 36207 519931 email: <a href="mailto:weigelt@metux.de">weigelt@metux.de</a><br>
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666<br>
----------------------------------------------------------------------<br>
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme<br>
----------------------------------------------------------------------<br>
<div><div></div><div class="h5">_______________________________________________<br>
Lguest mailing list<br>
<a href="mailto:Lguest@lists.ozlabs.org">Lguest@lists.ozlabs.org</a><br>
<a href="https://lists.ozlabs.org/listinfo/lguest" target="_blank">https://lists.ozlabs.org/listinfo/lguest</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Gaurav Kukreja<br><br>+91 997 030 1257<br><br>
<br>_______________________________________________
Lguest mailing list
Lguest@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/lguest </body>
</html>