You may be able to reference these posts: Create the installed image directly from the source: http://groups.google.com/group/android-porting/msg/2dedc5fe7ad58ed3?pli=1 Installation in VMWare: http://groups.google.com/group/android-porting/msg/fe85782f1bc3ad2f Installation in VirtualBox: http://groups.google.com/group/android-porting/msg/32b3709b4ae4f1d5
Hope it helps! -- Chen On Sat, Feb 21, 2009 at 6:06 PM, Avtar Singh <s.av...@gmail.com> wrote: > > Hi, > > I have built latest Android (did a repo sync today) for x86-Eee PC > target following instructions on this mailing list. The installer > image, installer.img, has been created successfully. I want to run > this image inside Virtual Box 2.1.0 (running on Windows XP). I > converted installer.img to .vdi using "vboxmanage convertdd" command. > > The kernel seems to boot okay and mounts ramdisk.img and I get to the > shell prompt. When I invoke init script to mount system and data > images, I get the following error: > > "Waiting for device: /dev/block/sdb2" > > I searched the mailing list. This is USB drive source for the > system/data images which obviously does not exist in my case. What > should I change this to so that the init script continues running? > > Thanks, > > Avtar Singh > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
