Hi Maxence, Not sure why that is the case. To use /dev/xvd* devices in Xen, domU's need to load the xen paravirtualization kernel modules.
Maybe loading these drivers as explained in [1] helps? Regards, -Tino [1] http://xen.1045712.n5.nabble.com/how-to-create-dev-xvda-td2594051.html -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor www.OpenNebula.org | @tinova79 On Wed, Aug 31, 2011 at 1:40 PM, Maxence Dunnewind <maxence.dunnew...@inria.fr> wrote: > Hi tino, > >> 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). > what I don't understand is why I would need to set datablock in sd namespace, > whereas base image and context are in xvd ? >> >> 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. > I'll try and come back to you with some results. > > 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@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org