paul.piscuc at sinergetic.ro
Fri Oct 29 14:59:09 PDT 2010
Thanks, the solution resolved the problem.
On Sat, Oct 30, 2010 at 12:24 AM, Javier Fontan <jfontan at gmail.com> wrote:
> Please, try this change
> Will be in the next patch release if it works as expected.
> On Fri, Oct 29, 2010 at 4:01 PM, Paul Piscuc <paul.piscuc at sinergetic.ro>
> > Hi,
> > We are having a small issue regarding opennebula + xen + lvm. The problem
> > 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
> > 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.
> > I modify the context line to:
> > 'file:/var/lib/one//6/images/disk.2,hda1,r',
> > everything works fine.
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users