Re: [Xen-ia64-devel] [IA64] Weekly benchmark results [ww26]

["KUWAMURA Shin'ya" <kuwa@xxxxxxxxxxxxxx>]

Hi Isaku,

On <20070702082404.GB32695%yamahata@xxxxxxxxxxxxx>
 Isaku Yamahata wrote:
> 
> On Fri, Jun 29, 2007 at 03:26:18PM +0900, KUWAMURA Shin'ya wrote:
> 
> > As for this changeset, booting domU using tap:aio succeeded, but
> > failed after the second. DomU's output:
> >   Xen p2m: to [0x0000000020000000, 0x0000000024000000) (65536 KBytes)
> >   XENBUS: Timeout connecting to device: device/vbd/769 (state 3)
> >   XENBUS: Device with no driver: device/console/0
> >   VFS: Cannot open root device "hda1" or unknown-block(0,0)
> >   Please append a correct "root=" boot option
> >   Kernel panic - not syncing: VFS: Unable to mount root fs on 
> > unknown-block(0,0)
> 
> blktap works for me. Could you check the followings?
> - Does dom0 support blktap and aio?
>   If you use kernel module, make sure that the module is inserted.
> - Is blktapctrl daemon running right after xend starting?
>   You can check it by ps command and the system log.
> - Is tapdisk daemon running after domU starting? Or does it complain?
>   You can check it by ps command and the system log.

Thank you for your advise. Now, this problem was solved!

The cause was because xenstore database was broken.
/var/lib/xenstored renamed as xenstored.bak and blktap works fine.

At first, I found that tapdisk daemon was not running at the second
boot.  The tapdisk has no output.

Next, I noticed that xenstore-ls hung up. Thus, I cleared xenstore
database.

Best Regards,
-- 
  KUWAMURA Shin'ya

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel