I also encounter problem when I create android guest VM. The problem looks like the filesystem cannot be found.
I tried several ways but the error remains.
First of all, I follow this guide http://odroid.com/dokuwiki/doku.php?id=en:xu4_xen
and successfully put ubuntu 14.04 as domU OS. Therefore, in theory, It means xen hypervisor is working normally.
Then I just directly try to put system.img, userdata.img as well as ramdisk.img into my odroid XU4 and use this .cfg.
memory = 512
maxmem = 512
name = "dom_android"
vcpus = 2
cpus = ['2']
vif = ['bridge=xenbr0']
disk = [ 'phy:/root/android/system.img,xvda,w','phy:/root/android/userdata.img,xvdb,w','phy:/root/android/ramdisk.img,xvdc,w' ]
extra = 'console=hvc0 xencons=tty root=/dev/xvda rw'
Of course, I meet problem. And the error likes the following:
0.540539] ALSA device list:
[ 0.540558] No soundcards found.
[ 0.541949] EXT3-fs (xvda): error: couldn't mount because of unsupported optional features (40)
[ 0.542777] EXT2-fs (xvda): error: couldn't mount because of unsupported optional features (40)
[ 0.543786] EXT4-fs (xvda): bad geometry: block count 458752 exceeds size of device (26352 blocks)
[ 0.547359] EXT3-fs (xvda): error: couldn't mount because of unsupported optional features (40)
[ 0.547955] EXT2-fs (xvda): error: couldn't mount because of unsupported optional features (40)
[ 0.548901] EXT4-fs (xvda): bad geometry: block count 458752 exceeds size of device (26352 blocks)
[ 0.552021] List of all partitions:
[ 0.552085] 0100 8192 ram0 (driver?)
[ 0.552131] 0101 8192 ram1 (driver?)
[ 0.552176] 0102 8192 ram2 (driver?)
[ 0.552248] 0103 8192 ram3 (driver?)
[ 0.552292] 0104 8192 ram4 (driver?)
[ 0.552362] 0105 8192 ram5 (driver?)
[ 0.552406] 0106 8192 ram6 (driver?)
[ 0.552470] 0107 8192 ram7 (driver?)
[ 0.552516] 0108 8192 ram8 (driver?)
[ 0.552583] 0109 8192 ram9 (driver?)
[ 0.552628] 010a 8192 ram10 (driver?)
[ 0.552672] 010b 8192 ram11 (driver?)
[ 0.552717] 010c 8192 ram12 (driver?)
[ 0.552760] 010d 8192 ram13 (driver?)
[ 0.552803] 010e 8192 ram14 (driver?)
[ 0.552847] 010f 8192 ram15 (driver?)
[ 0.552901] ca00 105408 xvda driver: vbd
[ 0.552945] ca10 563200 xvdb driver: vbd
[ 0.552990] ca20 1720 xvdc driver: vbd
[ 0.553029] No filesystem could mount root, tried: ext3 ext2 ext4 cramfs vfat msdos romfs
In total, I think filesystem is not good assigned correctly. Okay, here, I want to mention i also did this $ vi ./etc/fstab
/dev/xvda / ext4 errors=remount-ro 0 1
I think I put this content into fstab.ranchu as well as fstab.odroidxu.
Another try is like this: since userdata.img and system.img are both mounted by ramdisk.img during the runtime. And the system folder and data folder in the same directory with these image files are both sharing the same content with system.img and userdata.img. Therefore, I extract ramdisk.img and put content in system and data folder into the corresponding folders under ramdisk and then recreate ramdisk.img again. Lastly, I use this image file.
The way how to extract and modify and recreate ramdisk.img can be found with the following links:
1. https://hvera.wordpress.com/2010/10/19/ ... mdisk-img/
2. http://benno.id.au/blog/2007/11/18/andr ... rk-startup
With this try I aslo did not get the expect result and the error is also like the filesystem cannot be found.
At last, I consider with the android as dom0 OS with this link viewtopic.php?f=60&t=4475&start=140
I found putting these three img files into big one is not a good idea. But I do not know how to handle the problem.
Can anyone tell me how to solve this filesystem mount problem?