Difference between revisions of "Hotplug (qemu disk,nic,cpu,memory)"

From Proxmox VE
Jump to navigation Jump to search
m
(26 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
Proxmox support hotplugging of qemu devices
+
Proxmox support hotplugging of Qemu devices:
  
−
- disks (hotplug/unplug)
+
- Disks (hotplug/unplug)
  
−
- nics (hotplug/unplug)
+
- NICs (hotplug/unplug)
  
−
- cpu (core hotplug only)
+
- CPU (hotplug/unplug)
  
−
- memory (hotplug only - not yet released)
+
- Memory (hotplug/unplug)
  
−
=== Linux Guests notes ===
+
== Linux Guests Notes ==
  
−
you need to have 2 modules loaded in your linux guest
+
==== Kernel Modules Needed ====
 +
You need to have 2 modules loaded in your Linux guest:
  
 
<pre>
 
<pre>
Line 18: Line 19:
 
</pre>
 
</pre>
  
−
for cpu && memory hotplug,
+
==== CPU and Memory Hotplug ====
  
−
you need a recent kernel > 3.10
+
You need a recent kernel (> 3.10) and a udev rules file, to auto-enable CPU or memory hotplugging.
−
 
 
−
and a udev rules, to auto enable cpus or memory hotplugged
 
−
 
 
−
you can add a file:
 
  
 +
You can add the file:
  
 
/lib/udev/rules.d/80-hotplug-cpu-mem.rules
 
/lib/udev/rules.d/80-hotplug-cpu-mem.rules
 
<pre>
 
<pre>
−
    SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", \
+
SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", ATTR{online}="1"
−
    ATTR{online}="1"
+
SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", ATTR{state}="online"
−
   
 
−
    SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", \
 
−
    ATTR{state}="online"
 
 
</pre>
 
</pre>
  
−
   
+
For Linux kernel >= 4.7, you don't need the udev rule for memory hotplug; you only need to add this kernel parameter at boot:
−
=== Windows Guests notes ===
+
 
 +
  memhp_default_state=online
 +
 
 +
== Windows Guests Notes ==
 +
 
 +
- Disk and NIC hotplug work out of the box for all Windows versions >2003
  
−
- Disk and nic hotplug is working out of the box for all windows versions >2003
+
- CPU and memory hotplug work on > 2008 enterprise/datacenter, 2012 > standard
−
- cpu && memory hotplug is working on > 2008 enterprise/datacenter, 2012 > standard
 
  
−
=== Disk && Nic hotplug/unplug ===
+
== Disk and NIC Hotplug/unplug ==
  
−
edit your vm configuration file
+
Edit your VM configuration file:
  
 
<pre>
 
<pre>
 
/etc/pve/qemuserver/<VMID>.conf
 
/etc/pve/qemuserver/<VMID>.conf
 
</pre>
 
</pre>
−
and add
+
and add:
 
<pre>
 
<pre>
−
hotplug: 1
+
hotplug: network,disk,....
 
</pre>
 
</pre>
  
−
Then add/remove your disk or nics as usual.
+
Note: Since Proxmox 3.3, the hotplug option is available in the GUI.
 +
 
 +
Then add/remove your disks or NICs as usual.
  
−
For disk unplug, verify that your disk is not mounted in your linux guest or disabled in windows disk management.
+
For disk unplug, verify that your disk is not mounted in your Linux guest or enabled in Windows Disk Management.
  
 +
== CPU Hotplug ==
 +
 +
# In the VM Options, edit the "Hotplug" Value and activate "CPU Hotplug".
 +
# In the Hardware Section of your VM, specify the maximum number of Sockets/Cores.
 +
# You can now use the "CPU Options" dialog to change the number of vCPUs, while the machine is running.
 +
 +
maxcpus = sockets * cores.
 +
 +
Note : Windows CPU hotplug has been working since qemu 2.6 and CPU hot unplug has been working since qemu 2.7.
 +
 +
== Memory Hotplug ==
 +
 +
Memory hotplug is available in proxmox 3.4.
 +
 +
You need to enable NUMA and hotplug to get it working:
  
−
=== CPU hotplug ===
 
 
<pre>
 
<pre>
−
/etc/pve/qemuserver/<VMID>.conf
+
numa: 1
−
</pre>
+
hotplug: memory,...
−
and add
 
−
<pre>
 
−
cores: 1
 
−
maxcpus: 16
 
 
</pre>
 
</pre>
  
−
You will start your vm with 1 cpu|cores, and you can hotplug later up to 16 cores.
+
Then you can use the memory GUI options as usual.
−
Note that you can hotplug sockets with multiple cores, so don't defined socket option
+
 
 +
== Memory Hot Unplug ==
 +
 
 +
- Memory unplug currently does not work on Windows (<=win10 currently)
 +
 
 +
- Memory unplug can be unstable on Linux (<= kernel 4.10 currently)
 +
 
 +
For Linux memory unplug, you need to have movable zone enabled, in the kernel config (not enabled by default on Debian/Ubuntu):
  
−
=== memory hotplug ===
+
CONFIG_MOVABLE_NODE=YES
  
−
Need to be done
+
and the "movable_node" boot kernel parameter enabled.
  
 +
Here are some future kernel patches to improve unplug : http://www.spinics.net/lists/linux-mm/msg125359.html
  
 
[[Category:HOWTO]] [[Category:Installation]]
 
[[Category:HOWTO]] [[Category:Installation]]

Revision as of 08:44, 17 September 2020

Proxmox support hotplugging of Qemu devices:

- Disks (hotplug/unplug)

- NICs (hotplug/unplug)

- CPU (hotplug/unplug)

- Memory (hotplug/unplug)

Linux Guests Notes

Kernel Modules Needed

You need to have 2 modules loaded in your Linux guest: 

#modprobe acpiphp
#modprobe pci_hotplug

CPU and Memory Hotplug

You need a recent kernel (> 3.10) and a udev rules file, to auto-enable CPU or memory hotplugging.

You can add the file:

/lib/udev/rules.d/80-hotplug-cpu-mem.rules 

SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", ATTR{online}="1"
SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", ATTR{state}="online"

For Linux kernel >= 4.7, you don't need the udev rule for memory hotplug; you only need to add this kernel parameter at boot: 

memhp_default_state=online

Windows Guests Notes

- Disk and NIC hotplug work out of the box for all Windows versions >2003

- CPU and memory hotplug work on > 2008 enterprise/datacenter, 2012 > standard

Disk and NIC Hotplug/unplug

Edit your VM configuration file: 

/etc/pve/qemuserver/<VMID>.conf

and add: 

hotplug: network,disk,....

Note: Since Proxmox 3.3, the hotplug option is available in the GUI.

Then add/remove your disks or NICs as usual.

For disk unplug, verify that your disk is not mounted in your Linux guest or enabled in Windows Disk Management.

CPU Hotplug

  1. In the VM Options, edit the "Hotplug" Value and activate "CPU Hotplug".
  2. In the Hardware Section of your VM, specify the maximum number of Sockets/Cores.
  3. You can now use the "CPU Options" dialog to change the number of vCPUs, while the machine is running.

maxcpus = sockets * cores. 

Note : Windows CPU hotplug has been working since qemu 2.6 and CPU hot unplug has been working since qemu 2.7.

Memory Hotplug

Memory hotplug is available in proxmox 3.4.

You need to enable NUMA and hotplug to get it working: 

numa: 1
hotplug: memory,...

Then you can use the memory GUI options as usual.

Memory Hot Unplug

- Memory unplug currently does not work on Windows (<=win10 currently)

- Memory unplug can be unstable on Linux (<= kernel 4.10 currently)

For Linux memory unplug, you need to have movable zone enabled, in the kernel config (not enabled by default on Debian/Ubuntu): 

CONFIG_MOVABLE_NODE=YES

and the "movable_node" boot kernel parameter enabled.

Here are some future kernel patches to improve unplug : http://www.spinics.net/lists/linux-mm/msg125359.html

Retrieved from "https://pve.proxmox.com/mediawiki/index.php?title=Hotplug_(qemu_disk,nic,cpu,memory)&oldid=10835"