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

[Tino Vazquez]

Hi Maxence,

Sorry for the long delay in answering. Looking to the VM template and
the deployment file, it looks like that is what is intended in the
OpenNebula side. It instructs the hypervisor to set the disks in the
desired places (xvda for the base image, xvdb for the context CDROM,
and sde for the datablock).

In the end, this is passed through to the XEN hypervisor, which may
tinker with this values as it sees fit (unfortunately), or even the
guest OS may have udev rules that dictate other preferences. I suggest
cleaning this rules to see if after reboot the disks end up in their
proper places.

Regards,

-Tino

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



On Thu, Aug 25, 2011 at 4:13 PM, Maxence Dunnewind
<maxence.dunnewind at inria.fr> wrote:
> Hi,
>
>> Could you please send us the resulting deployment file? You may find
>> it in $ONE_LOCATION/var/<vid>.
> deployment file contains :
>
> ======
>
> name = 'one-1858'
> #O CPU_CREDITS = 256
> memory  = '256'
> kernel = '/usr/lib/xen-default/boot/hvmloader'
> disk = [
>    'tap:aio:/srv/cloud/one/var/1858/images/disk.0,xvda,w',
>    'tap:aio:/srv/cloud/one/var/1858/images/disk.1,sde,w',
>    'tap:aio:/srv/cloud/one/var/1858/images/disk.2,xvdb,r',
> ]
> vif = [
>    ' mac=02:00:83:fe:cc:97,ip=131.254.204.151,bridge=eth0',
> ]
> builder='hvm'
> device_model='/usr/lib/xen-default/bin/qemu-dm'
>
> =====
>
> Regards,
>
> 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
>