Revision 18c3417b

b/doc/install.rst
721 721
Your instance types, networking environment, hypervisor type and version
722 722
may all affect what kind of parameters should be used on your cluster.
723 723

  
724
For example kvm instances are by default configured to use a host
725
kernel, and to be reached via serial console, which works nice for Linux
726
paravirtualized instances. If you want fully virtualized instances you
727
may want to handle their kernel inside the instance, and to use VNC.
724
.. admonition:: KVM
725

  
726
  Instances are by default configured to use a host kernel, and to be
727
  reached via serial console, which works nice for Linux paravirtualized
728
  instances. If you want fully virtualized instances you may want to
729
  handle their kernel inside the instance, and to use VNC.
730

  
731
  Some versions of KVM have a bug that will make an instance hang when
732
  configured to use the serial console (which is the default) unless a
733
  connection is made to it within about 2 seconds of the instance's
734
  startup. For such case it's recommended to disable the
735
  ``serial_console`` option.
736

  
728 737

  
729 738
Joining the nodes to the cluster
730 739
++++++++++++++++++++++++++++++++
b/man/gnt-instance.rst
492 492
    Valid for the KVM hypervisor.
493 493

  
494 494
    This boolean option specifies whether to emulate a serial console
495
    for the instance.
495
    for the instance. Note that some versions of KVM have a bug that
496
    will make an instance hang when configured to use the serial console
497
    unless a connection is made to it within about 2 seconds of the
498
    instance's startup. For such case it's recommended to disable this
499
    option, which is enabled by default.
496 500

  
497 501
serial\_speed
498 502
    Valid for the KVM hypervisor.

Also available in: Unified diff