Re: the /dev/xvda can not be mounted and read/write when using xl create domU

[Wei Huang <w1.huang@samsung.com>]

>
> Thanks very much for your advices.
> I want to know  how the "54525952" offset can be computed?
> Mr Huang, could you give me some advice?
>
This number comes from the offset of Linaro rootfs image file x 512. 
Here is the output from fdisk. You then calculate 106496 * 512.

Disk rootfs.img: 536 MB, 536870912 bytes
255 heads, 63 sectors/track, 65 cylinders, total 1048576 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

                Device Boot      Start         End      Blocks   Id  System
vexpress-a9-nano.img1   *          63      106494       53216    c  W95 
FAT32 ()
vexpress-a9-nano.img2          106496     1048575      471040   83  Linux

Given that you can mount /dev/loop2 in Dom0, I think you don't need this 
offset. Another advice/question I have is if you have ext4-fs support 
compiled in your DomU kernel?


>> Or use root=/dev/xvda2 on the guest command line/cfg, which would be
>> more usual I think.
>>
>> (I'm not convinced this is the error though, since it seems xvda just
>> isn't working).
>>
>> duqi could you post the output of "xenstore-ls -fp" while the guest is
>> running but not able to access its disk.
>>
>