Revision fc3914e6
b/doc/admin.rst | ||
---|---|---|
371 | 371 |
be seamless for the instance. For more than one disk, just pass another |
372 | 372 |
disk parameter (e.g. ``--disk 1:adopt=...``). |
373 | 373 |
|
374 |
Instance kernel selection |
|
375 |
+++++++++++++++++++++++++ |
|
376 |
|
|
377 |
The kernel that instances uses to bootup can come either from the node, |
|
378 |
or from instances themselves, depending on the setup. |
|
379 |
|
|
380 |
Xen-PVM |
|
381 |
~~~~~~~ |
|
382 |
|
|
383 |
With Xen PVM, there are three options. |
|
384 |
|
|
385 |
First, you can use a kernel from the node, by setting the hypervisor |
|
386 |
parameters as such: |
|
387 |
|
|
388 |
- ``kernel_path`` to a valid file on the node (and appropriately |
|
389 |
``initrd_path``) |
|
390 |
- ``kernel_args`` optionally set to a valid Linux setting (e.g. ``ro``) |
|
391 |
- ``root_path`` to a valid setting (e.g. ``/dev/xvda1``) |
|
392 |
- ``bootloader_path`` and ``bootloader_args`` to empty |
|
393 |
|
|
394 |
Alternatively, you can delete the kernel management to instances, and |
|
395 |
use either ``pvgrub`` or the deprecated ``pygrub``. For this, you must |
|
396 |
install the kernels and initrds in the instance, and create a valid grub |
|
397 |
v1 configuration file. |
|
398 |
|
|
399 |
For ``pvgrub`` (new in version 2.4.2), you need to set: |
|
400 |
|
|
401 |
- ``kernel_path`` to point to the ``pvgrub`` loader present on the node |
|
402 |
(e.g. ``/usr/lib/xen/boot/pv-grub-x86_32.gz``) |
|
403 |
- ``kernel_args`` to the path to the grub config file, relative to the |
|
404 |
instance (e.g. ``(hd0,0)/grub/menu.lst``) |
|
405 |
- ``root_path`` **must** be empty |
|
406 |
- ``bootloader_path`` and ``bootloader_args`` to empty |
|
407 |
|
|
408 |
While ``pygrub`` is deprecated, here is how you can configure it: |
|
409 |
|
|
410 |
- ``bootloader_path`` to the pygrub binary (e.g. ``/usr/bin/pygrub``) |
|
411 |
- the other settings are not important |
|
412 |
|
|
413 |
More information can be found in the Xen wiki pages for `pvgrub |
|
414 |
<http://wiki.xensource.com/xenwiki/PvGrub>`_ and `pygrub |
|
415 |
<http://wiki.xensource.com/xenwiki/PyGrub>`_. |
|
416 |
|
|
417 |
KVM |
|
418 |
~~~ |
|
419 |
|
|
420 |
For KVM also the kernel can be loaded either way. |
|
421 |
|
|
422 |
For loading the kernels from the node, you need to set: |
|
423 |
|
|
424 |
- ``kernel_path`` to a valid value |
|
425 |
- ``initrd_path`` optionally set if you use an initrd |
|
426 |
- ``kernel_args`` optionally set to a valid value (e.g. ``ro``) |
|
427 |
|
|
428 |
If you want instead to have the instance boot from its disk (and execute |
|
429 |
its bootloader), simply set the ``kernel_path`` parameter to an empty |
|
430 |
string, and all the others will be ignored. |
|
431 |
|
|
374 | 432 |
Instance HA features |
375 | 433 |
-------------------- |
376 | 434 |
|
Also available in: Unified diff