Differences

This shows you the differences between two versions of the page.

--- en:virtualization:proxmox_ve_6_2_enable_connectx3_en_in_installer [2020-12-06 23:17]
Decomo 作成
+++ en:virtualization:proxmox_ve_6_2_enable_connectx3_en_in_installer [2021-01-09 12:46] (current)
Decomo
@@ Line 1: / Line 1: @@
-FIXME **このページはまだ完全には、翻訳されません。翻訳の完了を支援して下さい。**\\ //（翻訳が完了したらこの段落を削除して下さい）//
+====== Enable ConnectX-3 EN cards on Proxmox VE 6.2 Installer ======
-====== Enable a ConnectX-3 EN card on Proxmox VE 6.2 Installer ======
 Proxmox VE 6.2 contains 'mlx4' kernel modules that are drivers for ConnectX-3 cards, so it can potentially use the card as NIC by doing nothing. However I don't know why PVE installer doesn't load a ''mlx4_en'' module while it loads ''mlx4_core'' one, then the installer doesn't recognise the ConnectX-3 as NIC.
@@ Line 18: / Line 16: @@
 Boot the installer, and choose "Install Proxmox VE (Debug Mode)" in boot menu.
-{{ :linux:proxmox_ve_6_2_debug_mode_install.png |}}
+{{ virtualization:proxmox_ve_6_2_debug_mode_install.png |}}
 A shell appears after loading kernel, then straight to exit the shell.
@@ Line 24: / Line 22: @@
 The shell appears again after loading kernel modules, and run 'modprobe mlx4_en' to load an Ethernet driver for ConnectX-3.
-{{ :linux:proxmox_ve_6_2_modprobe_mlx4_en.png |}}
+{{ virtualization:proxmox_ve_6_2_modprobe_mlx4_en.png |}}
 You get back to PVE GUI installer screen after 'exit' the shell again, then proceed to install the PVE.
@@ Line 30: / Line 28: @@
 You can see ConnectX-3 interfaces on Management Interface screen (as ens1 and ens1d1 in a below image. I'm wondering they aren't ens1d1 and ens1s2.)
-{{ :linux:proxmox_ve_6_2_mlx4_en_enabled.png |}}
+{{ virtualization:proxmox_ve_6_2_mlx4_en_enabled.png |}}
 You do nothing on Proxmox VE environment after the installation because the PVE automatically loads the 'mlx4_en' module.