HOW TO CREATE AN ANDROID VIRTUAL MACHINE w/ SDCARD ON VMWARE
teacher1st
Android image: android-x86.6.r2
Vmware Workstation: 7.1.2 build-301548
Dell Studio 1737 laptop; Vista Home Premium SP2
1- Download from: http://www.androidx86.org/downloads.html
select: android-x86-1.6-r2.iso
2- Create a VMware machine.
Set memory to 512 MB [ 384MB or 256 MB may work]
re:http://vmetc.com/2010/12/27/install-androidx86-in-a-vmware-
workstation-vm/
Browse to the android-x86-1.6-r2.iso file.
VMware will detect a BSD image.
Set up networking. I used NAT. [Bridged should work as well].
Create a disk:
"Create /.Modify Partition" => OK => ...\cfdisk(util-linux-
2.14.1) new => tab to [NEW] => [Primary] => take all
defaults
Check to see if correct:
Name: sda1; Flags: Boot; Partition Type: Primary; FS Type:
Linux
Tab to [Write] => Sure => Quit
note: I selected ext2 as I plan to place this eventually on
my eee Netbook with a solid state disk. There is less writing to the
disk with ext2. Ext3 would be better for a hard drive
installation.
Install GRUB when prompted.
3- Start the new Android machine within Vmware Workstation.
4- Stop the Android machine and "X" the Android machine tab in VMware
Workstation .
Go to the .vmx file associated with the Android virtual machine.
Find the line:
ethernet0.virtualDev = "e1000"
change the virtual network card from e1000 to vlance so that
the line reads:
ethernet0.virtualDev = "vlance"
re: http://blogs.vmware.com/networking/2009/06/what-vnic-choosing-an-adapter-for-your-vm.html
5- Start Android on VMware
left click on Android screen => Settings button => Ethernet
Configuration => check Ethernet => Ethernet Configuration -
Configure Ethernet Devices =>
"eth0" should appear on the drop down and the Dhcp radio
button should be selected.
If the drop down is blank then something is wrong with the
ethernet0.virtualDev setting in the .vmx file.
6- Restart the Android virtual machine in VMware.
B- HOW TO INSTALL AN SDCARD INTO ANDROID VMWARE VIRTUAL MACHINE
1- Create a second disk drive on Vmware:
Edit Virtual Machine Settings => Add... button => highlight Hard Disk
=> Next =>
Create a new Virtual Disk => IDE radio button => Next => set Maximum
Disk Size
[I set it to 2 GB] => Store virtual disk as a single file radio
button => take default to
where the virtual disk will be stored => Finish
2- Start the Android Virtual Machine in VMware. Android will confirm
the added drive with a message. The message displays for a VERY short
time at startup.
3- Create a partition on the added drive:
Alt-F3 while cursor is on the Android screen to enter console mode.
# busybox df // better formatting with busybox
prefix
note that /dev/sda is the data drive
# fdisk /dev/block/sdb // will create a partition table and
partition on the sdcard drive
m // for menu to see the available
commands
n // new partition will be created
p // the new partition will be a primary partition
1 // number one says to create the first
partition
w // write the partition table. The first
partition lives
# fdisk /dev/block/sdb // check that all is correct
p // check the partition table
q // quit
4- Place an ext2 file system onto the sdcard partition
# mkfs.ext2 -L SDCARD /dev/block/sdb1 // create a file
system and a volume label
# mount -rw -t ext2 /dev/block/sdb1 /sdcard // directory /
sdcard already exists on image
5- Edit the GRUB file so that SDCARD will mount at boot time
# mkdir /data/
fs // fs is a
temporary directory
#
mount //
note file type of sda1
# mount -t ext2 /dev/block/sda1 /data/fs // the file
type should match above
#
mount //
see if it worked
# cd /data/fs/grub // we will need to mount SDCARD at boot
# vi
menu.lst // lst
as in list – an L not a one
cursor to the end of the line starting with “ Kernel /android-
lib.nw/kernel... the second line.
Esc =>
a // for
append
add “ SDCARD=SDB1” // without
quotes and with a leading space // to the end of
the line
Esc =>
q // quit
vi
# cat menu.1st //
verify the change
6- Check that Android knows about SDCARD
# reboot
left click on Android screen => Settings => SD card and phone storage
=. note total space.
Issa
well it's not easy !!
but thanks for this
> as in list � an L not a one
>
> cursor to the end of the line starting with � Kernel /android-
> lib.nw/kernel... the second line.
>
> Esc =>
> a // for
> append
>
> add � SDCARD=SDB1� // without
Taichichuan
Thanks for the post. BTW, is there a way to power off the VM from
within Android? Or, do you just power off the VM?
TIA
Yebyen (Kingdon)
http://martyfunkhouser.csh.rit.edu/~yebyen/
It must have been around 12/26... this is my first update since the new SDCARD installer, and I did not use the installer at all, just overwriting files by copying components of the image from out/target/product and overwriting on my system partition. I think from reading these instructions that all I need to do is change my SDCARD=/dev/sda2 to SDCARD=SDA2 and it might be restored.
Going to give that a shot, and if it works I'll flash again with the latest from a couple days ago, and put up another build. I am excited to try the GLES2 support, not sure if my hardware must provide special support to get it to work, but any EeePC target users can tell me if the BOARD_USES_I915C=true flag trick is all I need to get the support?
Any other new build flags that are worthy of a highlight? I will update my page of instructions as soon as it looks like I've fixed my SDCARD issues, I would like to provide support for multiple targets, but right now I only have this archos32 user machine (arm) and my converted Android-x86 netbook on eeepc/eng/release target, that worked pretty well except for the camera, last time I checked.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
Kingdon
The understanding I have is that you can actually install onto a single partition, and something like a sparse file or garbage-collected database of another kind can be set to run the SDCARD, and that it will grow (and shrink?) dynamically as the space is needed for sdcard storage.
I have experimented with the duplicity backup tool, and it describes my situation, sure I can take backups, but any cache data that is not in APK format will surely be lost when I restore and don't find the time for all of the little databases. I have found map applications that cache map data halfway between the behavior of GoogleMaps and MapDroyd (but not yet anything that will cache bus routes!), if I were a collector, this might be a hinderance if I have to suffer it again in the future.
It might be neat to have a more object-oriented cache browser, is all I'm saying... but the one application I don't want to lose track of as I factory-reset my AndroidX86 box, Yaxim! This jabber tool is clean, and enough to get you on facebook, but it does not jibe well with the large-screen form factor of my 10.1" or 9.1" Android-x86 machine... it will probably be great on the ARM target.
So, when I write again, I'll be using the 0106 image with preliminary support for GLES2.0 according to the list notes I've read! For the record, 1226 graphics already look faster than I remember, there are no slowdowns in transitions and everything is 100% rendered with fades and shades. The shutdown dialog in particular does not cause a slowdown anymore. This seems to be a slight improvement over previous images. :-)
Kingdon
Kingdon (yebyen)
But, the SD installer did the trick, I have an SD card and Android-x86 system all in one partition now! Thanks :)
Does anyone have more detailed notes on what's going on with GLES2? I thought I read that it has preliminary support now, what does preliminary mean? Any blog posts or code to point at?
Kingdon
Chih-Wei Huang
> Does anyone have more detailed notes on what's going on with GLES2? I thought I read that it has preliminary support now, what does preliminary mean? Any blog posts or code to point at?
Preliminary support? No, I didn't say that.
ES2 is enabled in the current mesa library,
but it doesn't work.
If you'd like to help or debug, go ahead.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Issa
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
--
Cordialement
Yassin Chouchane