Bug #2077

Context ISO do not always appear as /dev/cdrom (or sr0)

Added by Bastien Cadiot about 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:05/22/2013
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:worksforme Pull request:
Affected Versions:OpenNebula 4.0



Since Virtio become default disk driver, I experienced an issue with the contextualization disk.
Now the target dev for the ISO Cdrom in deployement file is the same than the default driver in /etc/oned.conf (vdb etc...)

This cause the guest to not see correctly the cdrom device. For example as /dev/vdb instead of /dev/sr0 (tested in centos 6.4)
In context variables of each template we can set the target device for context cdrom, but there is no option to set this parameter for the whole installation.

Because context script depends on the name of the device is this possible to force context ISO to use by default IDE driver ? Or at least to add a parameter in oned.conf to set this for all template ?


#1 Updated by Jaime Melis about 8 years ago

  • Status changed from Pending to Closed
  • Resolution set to worksforme

The solution for this issue would be to manually set the TARGET in the CONTEXT section:

Also available in: Atom PDF