From Fedora Project Wiki
(add tons of information, also VM instructions) |
(adjust associated_release_criterion template invocation) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|Beta|direct-kernel-boot}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This is to verify that it is possible to boot [[Anaconda]] and install the system by direct kernel+initrd boot. That can be achieved either by using [http://en.wikipedia.org/wiki/Preboot_Execution_Environment PXE boot] or by booting the kernel directly in a virtual machine. | |description=This is to verify that it is possible to boot [[Anaconda]] and install the system by direct kernel+initrd boot. That can be achieved either by using [http://en.wikipedia.org/wiki/Preboot_Execution_Environment PXE boot] or by booting the kernel directly in a virtual machine. | ||
Line 4: | Line 6: | ||
<ol> | <ol> | ||
<li>You will need {{filename|vmlinuz}} and {{filename|initrd.img}} files. Those are located in the {{filename|(arch)/os/images/pxeboot}} directory of the tree for the Fedora compose you wish to test.</li> | <li>You will need {{filename|vmlinuz}} and {{filename|initrd.img}} files. Those are located in the {{filename|(arch)/os/images/pxeboot}} directory of the tree for the Fedora compose you wish to test.</li> | ||
<li>You will need a remote location containing Anaconda's {{filename|LiveOS/}} directory (containing the installer) and optionally also a package repository. Development composes are usually available at [http:// | <li>You will need a remote location containing Anaconda's {{filename|LiveOS/}} directory (containing the installer) and optionally also a package repository. Development composes are usually available at [http://dl.fedoraproject.org/pub/alt/stage/ dl.fedoraproject.org/pub/alt/stage/] (doesn't contain package repository). If you have a local mirror, you can make it accessible over any protocol supported by [[Anaconda_Boot_Options#repo|inst.repo]] boot option.</li> | ||
<li>''Option 1:'' Set up a PXE server. | <li>''Option 1:'' Set up a PXE server. | ||
<ul> | <ul> | ||
Line 19: | Line 21: | ||
<li>''Option 2:'' Boot kernel directly in a virtual machine. | <li>''Option 2:'' Boot kernel directly in a virtual machine. | ||
<ul> | <ul> | ||
<li>Prepare a virtual machine that can boot kernel+initrd pair directly, e.g. using {{package|virt-manager}} (virt-manager has a ''Direct kernel boot'' field where you can specify the kernel, initrd and any boot options). | <li>Prepare a virtual machine that can boot kernel+initrd pair directly, e.g. using {{package|virt-manager}} (virt-manager has a ''Direct kernel boot'' field where you can specify the kernel, initrd and any boot options).<br/> | ||
[[image:virt-manager-pxeboot.png|300px]]</li> | |||
</ul> | </ul> | ||
</li> | </li> | ||
Line 32: | Line 35: | ||
<li>If the remote location contains a yum repository, the said repository is used for installation. This can be checked by examining the {{filename|/tmp/packaging.log}} file. Example output: | <li>If the remote location contains a yum repository, the said repository is used for installation. This can be checked by examining the {{filename|/tmp/packaging.log}} file. Example output: | ||
{{#tag:pre| | {{#tag:pre| | ||
09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl http://download.fedoraproject.org/pub/fedora/linux/development/ | 09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl http://download.fedoraproject.org/pub/fedora/linux/development/{{FedoraVersionNumber|next}}/x86_64/os/ and mirrorlist None | ||
09:34:37,313 DEBUG packaging: disabling repo fedora | 09:34:37,313 DEBUG packaging: disabling repo fedora | ||
09:34:37,313 DEBUG packaging: disabling repo updates-testing | 09:34:37,313 DEBUG packaging: disabling repo updates-testing |
Revision as of 20:42, 30 July 2013
Description
This is to verify that it is possible to boot Anaconda and install the system by direct kernel+initrd boot. That can be achieved either by using PXE boot or by booting the kernel directly in a virtual machine.
Setup
- You will need
vmlinuz
andinitrd.img
files. Those are located in the(arch)/os/images/pxeboot
directory of the tree for the Fedora compose you wish to test. - You will need a remote location containing Anaconda's
LiveOS/
directory (containing the installer) and optionally also a package repository. Development composes are usually available at dl.fedoraproject.org/pub/alt/stage/ (doesn't contain package repository). If you have a local mirror, you can make it accessible over any protocol supported by inst.repo boot option. - Option 1: Set up a PXE server.
- This is not an easy task and requires some administrator knowledge. You can read the appropriate section in the Installation guide for Fedora 17.
- The custom pxelinux config file can look like this:
DEFAULT vesamenu.c32 LABEL Fedora 41-Alpha-RC1 x86_64 KERNEL vmlinuz INITRD initrd.img APPEND inst.repo=http://dl.fedoraproject.org/pub/alt/stage/41-Alpha-RC1/Fedora/x86_64/os/
- Option 2: Boot kernel directly in a virtual machine.
- Prepare a virtual machine that can boot kernel+initrd pair directly, e.g. using
virt-manager
(virt-manager has a Direct kernel boot field where you can specify the kernel, initrd and any boot options).
- Prepare a virtual machine that can boot kernel+initrd pair directly, e.g. using
How to test
- Boot the system via PXE, or using a virtual machine with appropriate inst.repo boot argument (it has to point to the same compose you used for retrieving
vmlinuz
andinitrd.img
). - Proceed with installation.
Expected Results
- The system boots (using PXE or direct kernel boot in a virtual machine) and it downloads anaconda installer from the specified remote location.
- The installer starts correctly.
- If the remote location contains a yum repository, the said repository is used for installation. This can be checked by examining the
/tmp/packaging.log
file. Example output:09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl http://download.fedoraproject.org/pub/fedora/linux/development/41/x86_64/os/ and mirrorlist None 09:34:37,313 DEBUG packaging: disabling repo fedora 09:34:37,313 DEBUG packaging: disabling repo updates-testing 09:34:37,314 DEBUG packaging: disabling repo updates
- The installation completes and the new system initiates boot properly