You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

pve-faq.adoc 5.9KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  1. Frequently Asked Questions
  2. ==========================
  3. ifndef::manvolnum[]
  4. :pve-toplevel:
  5. endif::manvolnum[]
  6. ifdef::wiki[]
  7. :title: FAQ
  8. endif::wiki[]
  9. NOTE: New FAQs are appended to the bottom of this section.
  10. /////////////////////////////////////////////////////////////////
  11. ADD NEW FAQS TO THE BOTTOM OF THIS SECTION TO MAINTAIN NUMBERING
  12. /////////////////////////////////////////////////////////////////
  13. [qanda]
  14. What distribution is {pve} based on?::
  15. {pve} is based on http://www.debian.org[Debian GNU/Linux]
  16. What license does the {pve} project use?::
  17. {pve} code is licensed under the GNU Affero General Public License,
  18. version 3.
  19. Will {pve} run on a 32bit processor?::
  20. {pve} works only on 64-bit CPUs (AMD or Intel). There is no plan
  21. for 32-bit for the platform.
  22. +
  23. NOTE: VMs and Containers can be both 32-bit and/or 64-bit.
  24. Does my CPU support virtualization?::
  25. To check if your CPU is virtualization compatible, check for the `vmx`
  26. or `svm` tag in this command output:
  27. +
  28. ----
  29. egrep '(vmx|svm)' /proc/cpuinfo
  30. ----
  31. Supported Intel CPUs::
  32. 64-bit processors with
  33. http://en.wikipedia.org/wiki/Virtualization_Technology#Intel_virtualization_.28VT-x.29[Intel
  34. Virtualization Technology (Intel VT-x)] support. (http://ark.intel.com/search/advanced/?s=t&VTX=true&InstructionSet=64-bit[List of processors with Intel VT and 64-bit])
  35. Supported AMD CPUs::
  36. 64-bit processors with
  37. http://en.wikipedia.org/wiki/Virtualization_Technology#AMD_virtualization_.28AMD-V.29[AMD
  38. Virtualization Technology (AMD-V)] support.
  39. What is a container, CT, VE, Virtual Private Server, VPS?::
  40. Operating-system-level virtualization is a server-virtualization
  41. method where the kernel of an operating system allows for multiple
  42. isolated user-space instances, instead of just one. We call such
  43. instances containers. As containers use the host's kernel they are
  44. limited to Linux guests.
  45. What is a QEMU/KVM guest (or VM)?::
  46. A QEMU/KVM guest (or VM) is a guest system running virtualized under
  47. {pve} using QEMU and the Linux KVM kernel module.
  48. What is QEMU?::
  49. QEMU is a generic and open source machine emulator and
  50. virtualizer. QEMU uses the Linux KVM kernel module to achieve near
  51. native performance by executing the guest code directly on the host
  52. CPU.
  53. It is not limited to Linux guests but allows arbitrary operating systems
  54. to run.
  55. [[faq-support-table]]
  56. How long will my {pve} version be supported?::
  57. {pve} versions are supported at least as long as the corresponding
  58. Debian Version is
  59. https://wiki.debian.org/DebianOldStable[oldstable]. {pve} uses a
  60. rolling release model and using the latest stable version is always
  61. recommended.
  62. +
  63. [width="100%",cols="5*d",options="header"]
  64. |===========================================================
  65. | {pve} Version | Debian Version | First Release | Debian EOL | Proxmox EOL
  66. | {pve} 6.x | Debian 10 (Buster)| 2019-07 | tba | tba
  67. | {pve} 5.x | Debian 9 (Stretch)| 2017-07 | 2020-07 | 2020-07
  68. | {pve} 4.x | Debian 8 (Jessie) | 2015-10 | 2018-06 | 2018-06
  69. | {pve} 3.x | Debian 7 (Wheezy) | 2013-05 | 2016-04 | 2017-02
  70. | {pve} 2.x | Debian 6 (Squeeze)| 2012-04 | 2014-05 | 2014-05
  71. | {pve} 1.x | Debian 5 (Lenny) | 2008-10 | 2012-03 | 2013-01
  72. |===========================================================
  73. [[faq-upgrade]]
  74. How can I upgrade {pve} to the next release?::
  75. Minor version upgrades, for example upgrading from {pve} in version 5.1
  76. to 5.2, can be done just like any normal update, either through the Web
  77. GUI __Node -> Updates__ panel or through the CLI with:
  78. +
  79. ----
  80. apt update
  81. apt full-upgrade
  82. ----
  83. +
  84. NOTE: Always ensure you correctly setup the
  85. xref:sysadmin_package_repositories[package repositories] and only
  86. continue with the actual upgrade if `apt update` did not hit any error.
  87. +
  88. Major version upgrades, for example going from {pve} 4.4 to 5.0, are
  89. also supported. They must be carefully planned and tested and should
  90. *never* be started without having a current backup ready.
  91. Although the specific upgrade steps depend on your respective setup, we
  92. provide general instructions and advice of how a upgrade should be
  93. performed:
  94. +
  95. * https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0[Upgrade from {pve} 5.x to 6.0]
  96. * https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0[Upgrade from {pve} 4.x to 5.0]
  97. * https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0[Upgrade from {pve} 3.x to 4.0]
  98. LXC vs LXD vs Proxmox Containers vs Docker::
  99. LXC is a userspace interface for the Linux kernel containment
  100. features. Through a powerful API and simple tools, it lets Linux users
  101. easily create and manage system containers. LXC, as well as the former
  102. OpenVZ, aims at *system virtualization*, i.e. allows you to run a
  103. complete OS inside a container, where you log in as ssh, add users,
  104. run apache, etc...
  105. +
  106. LXD is building on top of LXC to provide a new, better user
  107. experience. Under the hood, LXD uses LXC through `liblxc` and its Go
  108. binding to create and manage the containers. It's basically an
  109. alternative to LXC's tools and distribution template system with the
  110. added features that come from being controllable over the network.
  111. +
  112. Proxmox Containers also aims at *system virtualization*, and thus uses
  113. LXC as the basis of its own container offer. The Proxmox Container
  114. Toolkit is called `pct`, and is tightly coupled with {pve}. That means
  115. that it is aware of the cluster setup, and it can use the same network
  116. and storage resources as fully virtualized VMs. You can even use the
  117. {pve} firewall, create and restore backups, or manage containers using
  118. the HA framework. Everything can be controlled over the network using
  119. the {pve} API.
  120. +
  121. Docker aims at running a *single* application running in a contained
  122. environment. Hence you're managing a docker instance from the host with the
  123. docker toolkit. It is not recommended to run docker directly on your
  124. {pve} host.
  125. +
  126. NOTE: You can however perfectly install and use docker inside a Proxmox Qemu
  127. VM, and thus getting the benefit of software containerization with the very
  128. strong isolation that VMs provide.