Bug #165

Use cdrom type for context block devices

Added by Ruben S. Montero over 11 years ago. Updated over 11 years ago.

Status:ClosedStart date:10/27/2009
Priority:NormalDue date:
Assignee:Jaime Melis% Done:


Category:Core & System
Target version:-
Resolution:fixed Pull request:
Affected Versions:


A bug reported in the mailing list by Shi Jin:

However, it does not work at all

under Windows.
On the other hand, I found that if we make it a cdrom device instead
of a disk, it works on both systems. The XML would be
<disk type='file' device='cdrom'>
<source file='/srv/cloud/ImgRep/WinXP/vmcontext.iso'/>
<target dev='hdb' bus='ide'/>
I see two ways to accomplish this
1. change the context behavior to cdrom device completely. This should
work fine.
2. give the user the freedom to choose either a cdrom or disk device.
This will be completely compatible with previous setup.

It may be better to always use cdrom type for the iso images.

Associated revisions

Revision eb931346
Added by Jaime Melis over 11 years ago

the context isos are now generated as cdroms in libvirt (#165)

git-svn-id: http://svn.opennebula.org/one/trunk@899 3034c82b-c49b-4eb3-8279-a7acafdc01c0


#1 Updated by Jaime Melis over 11 years ago

  • Assignee changed from Ruben S. Montero to Jaime Melis
  • % Done changed from 0 to 50

The device generated by a context iso is now changed to cdrom, in the case of libvirt. We have tested it and it works. Please note that this has an impact in contextualization, for instance, in ubuntu the target device must be hd* instead of sd*. This has to be detailed in the documentation.

#2 Updated by Jaime Melis over 11 years ago

  • Status changed from New to Closed
  • % Done changed from 50 to 100
  • Resolution set to fixed

This issue has been documented.

Also available in: Atom PDF