Feature #348
User configurable image protocol for xen
| Status: | Closed | Start date: | 09/13/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Drivers - Auth | |||
| Target version: | Release 2.0.1 | |||
| Resolution: | fixed | Pull request: |
Description
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.
Associated revisions
feature #348: Xen DISKs can now use a custom driver (tap:aio:, file:, ...)
feature #348: Xen DISKs can now use a custom driver (tap:aio:, file:, ...)
(cherry picked from commit e3d82b69e9eeb4d152e085a22b2fb9f789430af6)
History
#1
Updated by Frank Stutz almost 11 years ago
I second this. Right now I have a patch file for XenDriver.cc which automatically changes tap:aio to file for my case.
#2
Updated by Daniel Molina over 10 years ago
- Target version deleted (
Release 2.0)
#3
Updated by Javi Fontan over 10 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).
#4
Updated by Ruben S. Montero over 10 years ago
- Target version set to Release 2.0.1
#5
Updated by Ruben S. Montero over 10 years ago
- Status changed from New to Closed
- Resolution set to fixed
This is now implemented in the one-2.0 branch.