Bug #4146

Attached cdrom to existing VM can crash oned and the context image isn't moved as the latest device

Added by Tim Verhoeven almost 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:11/10/2015
Priority:HighDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 4.14.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14

Description

There was an issue reported that when using contextualization and CDROM images, the context iso always take precedence on the attached CDROM image and this prevents booting from it. A workaround what to set the target device for the CDROM to "hda". But this is supposed to be fixed in current version.

Now when trying a similar scenario but with an already existing VM by using the Attach feature, things do not work as expected.

When using a CDROM that has no target device set and attach this to a VM with a context iso then the CDROM will become hdb, not hda as expected.

Secondly, when attaching a CDROM that has the target device set to "hda" to a VM with a context issue the oned completely crashes and is restarted.

Both are undesired behaviours and should be fixed. I've tested this with ONE 4.14 on CentOS 7.

Associated revisions

Revision f6ec52dd
Added by Ruben S. Montero almost 5 years ago

bug #4146: Fix bug when the target is already in use

Revision c35c18a7
Added by Ruben S. Montero almost 5 years ago

bug #4146: Fix bug when the target is already in use

(cherry picked from commit f6ec52dddc5ab205dc94f0a6e5fd04a834f9b2a3)

History

#1 Updated by Ruben S. Montero almost 5 years ago

  • Target version set to Release 4.14.2

#2 Updated by Ruben S. Montero almost 5 years ago

  • Assignee set to Ruben S. Montero

#3 Updated by Ruben S. Montero almost 5 years ago

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

Hi Tim.

The issue about oned crashing is now fixed and in master and one-4.14 branches. You can safely apply the patch to your installation.

About the CDROM and context CD:
  • The CDROM always precede the context CD at instantiation, i.e. if both are part of the VM template. If there is no other CD, context will take hda.
  • Booting from CD should not be an issue in this case.
  • This cannot be change if you are attaching a CD to an existing VM with hda already taken by the context. Note that this would imply detaching the context iso, attaching the new one and re-attaching the context behind.

I'm closing this issue as fixed, if you have any other comment or issue please feel free to reply.

#4 Updated by Rolandas Naujikas almost 5 years ago

Probably you forgot apply to one-4.14 :-)

#5 Updated by Ruben S. Montero almost 5 years ago

Ups forgot to git push... thanks :)

Also available in: Atom PDF