Re: Unable to start Precise domU PV on xen-unstable with xl

[Stefan Bader <stefan.bader@canonical.com>]

On 14.02.2012 10:19, Fantu wrote:
> There are already some on attachment of first post...
> 
> ...
> (initramfs) cat /proc/partitions 
> major minor  #blocks  name
> 
>  202        1   10240000 xvda1
>  202        2    1024000 xvda2
>  (initramfs) blkid 
> /dev/xvda2: UUID="3a4d1b29-15b2-47b1-b97f-8c258a8b10d8" TYPE="swap"

Right, saw that. This is what the kernel has. So internally xvda1 is there and
has a size. The uuid link is created (or should be) when the device becomes
ready. Interestingly I can see a capacity change message for xvda2 but not for
xvda1. Not sure why.
But then there is also the fact that when you do a blkid manually, you also do
not get any info there. Not sure there would be any errors anywhere about that
or you just get no data at all.
Of course this could be related to something xl in 4.0 does differently. Problem
is I have 4.1.2 and I cannot see the same issues.

-Stefan
> 
> And about /dev/disk-by-uuid/:
> (initramfs) ls -al /dev/disk/by-uuid/
> lrwxrwxrwx    1        11 3a4d1b29-15b2-47b1-b97f-8c258a8b10d8 ->
> ../../xvda2
> drwxr-xr-x    4        80 ..
> drwxr-xr-x    2        60 .
> 
> If can help also udev info:
> (initramfs) udevadm info --query=all --path /block/xvda1
> P: /devices/vbd-51713/block/xvda1
> N: xvda1
> S: disk/by-path/xen-vbd-51713
> E: DEVLINKS=/dev/disk/by-path/xen-vbd-51713
> E: DEVNAME=/dev/xvda1
> E: DEVPATH=/devices/vbd-51713/block/xvda1
> E: DEVTYPE=disk
> E: ID_PART_TABLE_TYPE=dos
> E: ID_PATH=xen-vbd-51713
> E: ID_PATH_TAG=xen-vbd-51713
> E: MAJOR=202
> E: MINOR=1
> E: SUBSYSTEM=block
> E: UDEV_LOG=3
> E: USEC_INITIALIZED=282841
> (initramfs) udevadm info --query=all --path /block/xvda2
> P: /devices/vbd-51714/block/xvda2
> N: xvda2
> S: disk/by-path/xen-vbd-51714
> S: disk/by-uuid/3a4d1b29-15b2-47b1-b97f-8c258a8b10d8
> E: DEVLINKS=/dev/disk/by-path/xen-vbd-51714
> /dev/disk/by-uuid/3a4d1b29-15b2-47b1-b97f-8c258a8b10d8
> E: DEVNAME=/dev/xvda2
> E: DEVPATH=/devices/vbd-51714/block/xvda2
> E: DEVTYPE=disk
> E: ID_FS_TYPE=swap
> E: ID_FS_USAGE=other
> E: ID_FS_UUID=3a4d1b29-15b2-47b1-b97f-8c258a8b10d8
> E: ID_FS_UUID_ENC=3a4d1b29-15b2-47b1-b97f-8c258a8b10d8
> E: ID_FS_VERSION=2
> E: ID_PATH=xen-vbd-51714
> E: ID_PATH_TAG=xen-vbd-51714
> E: MAJOR=202
> E: MINOR=2
> E: SUBSYSTEM=block
> E: UDEV_LOG=3
> E: USEC_INITIALIZED=283285
> 
> Only xvda2 (swap) seem to be full and correct, xvda1 not.
> On production system the same domU work, differences in which there is very
> likely the cause of the problem are then:
> Xen 4.0 with xm on production system and xen-unstable with xl on test system
> But I have no certainty that it is a problem of xen and/or xl.
> 
> Thanks for any reply and sorry for bad english.
> 
> --
> View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-start-Precise-domU-PV-on-xen-unstable-with-xl-tp5479428p5481930.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel