Re: [one-users] Support for custom Xen drivers for disk images
On Friday 29 October 2010 21:12:11 Ruben S. Montero wrote: > Finally, the driver defaults to "tap:aio:" you can change the default for > all the images including context in > $ONE_LOCATION/etc/vmm_ssh/vmm_ssh_xen.conf I tried this one with 'tap2:aio' and it works perfect. Now you can say Xen 4.0 is supported. Thanks a lot. Regards, Łukasz Oleś ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Support for custom Xen drivers for disk images
The "driver" is a string prepended to the file path so you can use any of the prefixes in the page you have linked. On Fri, Oct 29, 2010 at 11:04 PM, Todd Deshane wrote: > On Fri, Oct 29, 2010 at 3:12 PM, Ruben S. Montero > wrote: >> Hi all, >> This refers to http://dev.opennebula.org/issues/348. >> There is a new DRIVER attribute for DISK. The DRIVER can be used to specify >> custom drivers for images. Example >> DISK = [ driver = "tap2:aio:", source="path_to_image", target="hda1"] >> So it gets transformed to: >> disk = [ >> 'tap2:aio:path_to_image,sda1,w', >> ] >> This attribute is also supported by the image repository. So you can add >> driver="file:" to an image template, or add it to an existing one using >> oneimage update. Also you can specify it in the VM template as: >> DISK = [ image="myimage", driver="file:"] >> The DRIVER is also supported by CONTEXT devices just added as: >> CONTEXT = [ driver = "file:" ,... ] >> Finally, the driver defaults to "tap:aio:" you can change the default for >> all the images including context in >> $ONE_LOCATION/etc/vmm_ssh/vmm_ssh_xen.conf >> Any feedback is more than welcome! > > Naming that xen upstream uses should be taken into consideration: > http://wiki.xensource.com/xenwiki/blktap2 > > Thanks, > Todd > > -- > Todd Deshane > http://todddeshane.net > http://runningxen.com > ___ > Users mailing list > Users@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 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Support for custom Xen drivers for disk images
On Fri, Oct 29, 2010 at 3:12 PM, Ruben S. Montero wrote: > Hi all, > This refers to http://dev.opennebula.org/issues/348. > There is a new DRIVER attribute for DISK. The DRIVER can be used to specify > custom drivers for images. Example > DISK = [ driver = "tap2:aio:", source="path_to_image", target="hda1"] > So it gets transformed to: > disk = [ > 'tap2:aio:path_to_image,sda1,w', > ] > This attribute is also supported by the image repository. So you can add > driver="file:" to an image template, or add it to an existing one using > oneimage update. Also you can specify it in the VM template as: > DISK = [ image="myimage", driver="file:"] > The DRIVER is also supported by CONTEXT devices just added as: > CONTEXT = [ driver = "file:" ,... ] > Finally, the driver defaults to "tap:aio:" you can change the default for > all the images including context in > $ONE_LOCATION/etc/vmm_ssh/vmm_ssh_xen.conf > Any feedback is more than welcome! Naming that xen upstream uses should be taken into consideration: http://wiki.xensource.com/xenwiki/blktap2 Thanks, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
