You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/guide/incus/incus_install.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ If this is a new server, make sure that both ```update``` and ```curl``` are wor
16
16
- The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
17
17
- The server needs to be restarted after the environment installation process to load some default configurations
18
18
- By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
19
+
- This installer has been tested to work on either physical or non-physical machines
Copy file name to clipboardExpand all lines: docs/en/guide/lxd/lxd_install.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,11 @@ If this is a new server, make sure that both ```apt update``` and ```apt install
16
16
It's recommended to wait for at least 5 minutes after the system boots up before executing the following commands. This is to avoid the script being executed by the default system settings, which could cause issues with apt sources.
- The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
21
21
- The server needs to be restarted after the environment installation process to load some default configurations
22
22
- By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
23
+
- This installer has been tested to work on either physical or non-physical machines
- Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
20
+
- Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the public network.
21
21
22
22
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs [Jump](https://github.com/oneclickvirt/pve)
Copy file name to clipboardExpand all lines: docs/en/guide/pve/pve_install.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,8 @@ For low-configuration hosts, it is recommended to check the contents of the ```C
12
12
13
13
## Installation on non-physical machines
14
14
15
+
Proxmox installed by this method can subsequently use all scripts of this project.
16
+
15
17
### One-click PVE installation
16
18
17
19
:::tip
@@ -116,7 +118,9 @@ To this point the main body is installed.
116
118
117
119
## Installation on a physical machine
118
120
119
-
This method has not been tested and adapted on a large scale, only the author himself installed PVE8.4 on the local machine, if there are problems corresponding to the warehouse and then open issues
121
+
Proxmox installed by this method **NOT** to be used subsequently with all scripts of this project.
122
+
123
+
This method has not been tested and adapted on a large scale, only I installed PVE8.4 on the local machine, the router itself is not ```automatically obtain an IP address``` but ```fixed IP address connection``` way, if there is a problem corresponding to the warehouse open issues.
120
124
121
125
### U disk burning official ISO
122
126
@@ -183,4 +187,6 @@ During the execution of the configuration script, you will be prompted to enter
183
187
184
188
### Cautions
185
189
186
-
Physical machines can not use NAT to directly connect virtual machines to access the network after the installation of unlimited modules, so the project's subsequent tutorials do not support this method of access to the bridge, the project's subsequent tutorials only support the installation of the PVE on non-physical machines (through the automatic configuration of the host gateway of the PVE)
190
+
Physical machine after the installation of unlimited modules can not use NAT to connect directly to the virtual machine to access the network, so the subsequent tutorials of this project does not support this method of access to the bridge, the subsequent scripts of this project does not support this method of installation of Proxmox.
191
+
192
+
Currently feasible wireless module used on the PVE success stories, are required to WIFI router access to the network is ```automatically obtain an IP address (DHCP)``` (the subsequent use of openwrt or ikuai or directly nat after the network available within the virtual machine), or can be modified in the router static routing table, if the WIFI router to use a ```fixed IP address Connection to the network```, for the time being did not find success stories.
0 commit comments