[one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode

[Tino Vazquez]

Dear Maxence,

Could you please send us the resulting deployment file? You may find
it in $ONE_LOCATION/var/<vid>.

Regards,

-Tino

--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79



On Thu, Aug 18, 2011 at 8:52 AM, Maxence Dunnewind
<maxence.dunnewind at inria.fr> wrote:
> Hi,
>
> I'm trying to use DATABLOCK on our installation and have some issues.
> First, a little bit of context :
>
> * Workers :
>  - Xen 3.2, caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
>  - Debian Lenny, kernel 2.6.26-2, xen version, x86_64
> * ONE :
>  - ONE 2.0.1
>  - Centos 5.5, kernel 2.6.18-194
>
> I use Xen in HVM mode, so my instances' template looks like :
> ----
> CPU    = 1
> MEMORY = 256
> OS     = [ kernel = "/usr/lib/xen-default/boot/hvmloader" ]
> RAW =[type ="xen",data="builder='hvm'"]
> RAW =[type="xen",data="device_model='/usr/lib/xen-default/bin/qemu-dm'"]
> ----
>
> Now the strange things : If I create a system image with DEV_PREFIX=sd, it own't
> boot. If I create it with DEV_PREFIX=xvd, it will boot correctly but will be
> seen as /dev/sda (and context will be /dev/sdb).
>
> With datablocks, it much more "funny", the only combination which seems to work is :
>  - DEV_PREFIX=xvd for the system image
>  - DEV_PREFIX=sd for the datablock image
>
> With this combination, resulting "onevm show" looks like :
>
> [snip]
> CPU=1
> DISK=[
>    CLONE=YES,
>    DISK_ID=0,
>    IMAGE=BonFIRE Debian Squeeze v2,
>    IMAGE_ID=165,
>    READONLY=NO,
>    SAVE=NO,
>    SOURCE=/srv/cloud/one/var/images/58cad9fd025f8135a4ef176a0f7721826a0aea8e,
>    TARGET=xvda,
>    TYPE=DISK ]
> DISK=[
>    CLONE=YES,
>    DISK_ID=1,
>    IMAGE=bd18,
>    IMAGE_ID=283,
>    READONLY=NO,
>    SAVE=NO,
>    SOURCE=/srv/cloud/one/var/images/ec02c9e15e297d51c94ef9640909bee7345eb529,
>    TARGET=sde,
>    TYPE=DISK ]
>
> [snip]
>
> So the system disk has xvda as target, but will finally appear as /dev/sda.
> Context will appear as /dev/sdb, and the datablock which has target=sdE will
> appear as /dev/sdc ...
>
> any other combination does not work for me (if TARGET=sda for system disk,
> instance does not boot, if TARGET=xvdX for datablock, the instance boots but the
> corresponding device never appears).
>
>
> Any hints ?
>
> Maxence
> --
> Maxence Dunnewind
> System Engineer on Bonfire
> Research Center INRIA Rennes - Bretagne Atlantique, France
> Team Myriads, Office E219, tel +33 2 99 84 25 76
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>