User configurable image protocol for xen
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Drivers - Auth|
|Target version:||Release 2.0.1|
Xen images can be specified using "file:" or "tap:aio:" flavors. Even if "tap:aio" is seems to be the right way to go with recent versions of Xen there are some distributions that do not support it.
"tap:aio:" or "file:" protocols should be user configurable. Right now this is hardcoded in the core.
feature #348: Xen DISKs can now use a custom driver (tap:aio:, file:, ...)
(cherry picked from commit e3d82b69e9eeb4d152e085a22b2fb9f789430af6)
#3 Updated by Javi Fontan over 9 years ago
Xen 4 does not like tap:aio. Mail from Åukasz OleÅ›:
I'm using Xen 4.0 and pvops kernel 2.6.32 (http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary) In this kernel blktap is in version 2 and version 1 is not availabe. Correct driver entry for blktap2 is tap2:aio, but opennebula generates config with tap:aio. Probably it should be option in VM template to define driver(tap, tap2, file).