Bug 822987 - Booting Virtual Machines from custom initrd/kernel images.
Summary: Booting Virtual Machines from custom initrd/kernel images.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Cheryn Tan
QA Contact: ecs-bugs
URL:
Whiteboard:
: 856734 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-18 17:28 UTC by Stephen Gordon
Modified: 2015-09-22 13:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 17:22:10 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 6 Cheryn Tan 2012-09-25 06:19:51 UTC
Changed table entry to read:

Linux Boot Options

The following options boot a Linux kernel directly instead of through the BIOS bootloader.

  *  kernel path - A fully-qualified path to a kernel image to boot the virtual machine. The kernel image must be stored on either the ISO domain (path name in the format of iso://path-to-image) or on the host's local storage domain (path name in the format of /data/images).

  *  initrd path - A fully-qualified path to a ramdisk image to be used with the previously specified kernel. The ramdisk image must be stored on the ISO domain (path name in the format of iso://path-to-image) or on the host's local storage domain (path name in the format of /data/images).

  *  kernel params - Kernel command line parameter strings to be used with the defined kernel on boot. 

In both Table 8.8. Virtual Machine: Boot Options Settings and Table 8.10. Virtual Machine: Run Once Settings

Does this fulfill the bug requirement? Does it need any more information?

Comment 7 Cheryn Tan 2012-09-25 06:20:25 UTC
*** Bug 856734 has been marked as a duplicate of this bug. ***

Comment 8 Stephen Gordon 2012-09-25 13:10:15 UTC
I think that looks much better, thanks!


Note You need to log in before you can comment on or make changes to this bug.