yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

Public bug reported:

Boot from ISO is slightly different by default in Xen vs KVM

In Xen ISO is attached as a separate drive and set to boot (i.e. root hard drive still exists)
In KVM the ISO image replaces the root drive

In discussions on irc we decided that we should allow both based on
image metadata. Example: metadata like 'separate_attach', if set to True
will attach the disk separately and still allow a root drive.

We will need some sort of flag to set maximum size of separate attached
drive.  If the metadata is not set, the ISO will replace the root drive.

** Affects: nova
     Importance: High
     Assignee: Nova Feature Parity Team (nova-feature-parity)
         Status: Triaged

** Changed in: nova
    Milestone: None => essex-4

** Changed in: nova
     Assignee: (unassigned) => Nova Feature Parity Team (nova-feature-parity)

** Changed in: nova
   Importance: Undecided => High

** Changed in: nova
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Nova
Feature Parity Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/914484

Title:
  Boot from ISO is different in XS/KVM

Status in OpenStack Compute (Nova):
  Triaged

Bug description:
  Boot from ISO is slightly different by default in Xen vs KVM

  In Xen ISO is attached as a separate drive and set to boot (i.e. root hard drive still exists)
  In KVM the ISO image replaces the root drive

  In discussions on irc we decided that we should allow both based on
  image metadata. Example: metadata like 'separate_attach', if set to
  True will attach the disk separately and still allow a root drive.

  We will need some sort of flag to set maximum size of separate
  attached drive.  If the metadata is not set, the ISO will replace the
  root drive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/914484/+subscriptions