Please, try this change http://lists.opennebula.org/pipermail/users-opennebula.org/2010-October/003134.html. Will be in the next patch release if it works as expected.
On Fri, Oct 29, 2010 at 4:01 PM, Paul Piscuc <[email protected]> wrote: > Hi, > We are having a small issue regarding opennebula + xen + lvm. The problem is > that when one generates the deployment file appends to the context disk > 'tap:aio', instead of 'file'. When deploying the VM, everything works, > except for the fact that the VM doesn't recognize the context iso. When we > modify that line to read 'file:' instead of 'tap:aio', the context is > mounted succesfully. > Here is our context: > CONTEXT = [ > TYPE = "BLOCK", > hostname = $NAME, > ip_public = "10.11.12.6", > ip_netmask = "255.255.255.0", > ip_gw = "10.11.12.1", > files="/vms_configuration/init.sh", > target="hda1", > netloc="/etc/network/interfaces", > hostloc="/etc/hostname" > ] > The generated deployment file has the following: > disk = [ > 'phy:/var/lib/one//6/images/disk.0,sda1,w', > 'phy:/var/lib/one//6/images/disk.1,sda2,w', > 'tap:aio:/var/lib/one//6/images/disk.2,hda1,r', > ] > Xen succesfully mounts the tap:aio, but it is not recognized by the VM. When > I modify the context line to: > 'file:/var/lib/one//6/images/disk.2,hda1,r', > everything works fine. > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Javier Fontan, Grid & Virtualization Technology Engineer/Researcher DSA Research Group: http://dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
