Kimsufi server creates Windows 11 chick using Proxmox7

Proxmox has supported tpm2.0 since version 7.x, so now we can easily create Windows 11 chicks on proxmox. First prepare the win11 iso and virtio driver iso.

win11iso download: https://www.microsoft.com/zh-cn/software-download/windows11

You can copy the address to the pve panel to download:

Virtio driver iso download, download the latest version: https://github.com/virtio-win/virtio-win-pkg-scripts

You can also download it in the pve panel:

Create a virtual machine, select the win11iso you just downloaded, and be sure to select the correct operating system category and version:

The next step is to system configuration. If the version selected in the previous step is 11/2022, then the default configuration here is the best. You only need to select the storage pool of efi and tpm. It is also recommended to enable the qemu agent option. , the function of qemu agent will be introduced in detail later:

The bus/device here on the hard disk is configured as virtioblock, and the cache is configured as write-back, which can maximize the hard disk performance of the virtual machine:

It is recommended to select host for the cpu category and enable numa. You can configure other configurations according to your own needs:

The memory settings are not explained in detail here without taking screenshots. It is recommended to use 4g or above.

It is recommended to choose virtio paravirtualization for the network model, which can maximize the network performance of the virtual machine:

Since I have ipv4 and ipv6 dual stack, one network card only handles one protocol. The previous vmbr0 only handles ipv6, so after the machine is created, I will continue to add a vmbr1 network card to support ipv4:

For the configuration of the network, please refer to my article:

kimsufi: Use proxmox to open IPv4nat+IPv6 chick, ks-le can open dozens of VPS

Next, you need to add a cd/dvd drive to mount the virtio driver downloaded before. Since when we created the virtual machine before, the hard disk and network card were set to the virtio model, so virtio must be used here. driver, otherwise the system will not recognize the hard disk and network during installation:

After everything is set up, start the virtual machine, open the vnc console and press Enter when you see the proxmox logo to enter the windows installation interface:

If nothing else, the Windows installer will prompt that it cannot find any hard disk during the hard disk partitioning step. At this time, click to load the driver:

Browse the virtio-win drive and find the directory amd64/w10 inside:

To install the hard drive:

At this point you can see that the hard disk is recognized, but don’t rush to partition, click to load the driver:

Browse the virtio-win driver as before and find the netkvm/w10/amd64 directory:

Install network card driver:

Then you will return to the hard disk partition. At this time, the virtio hard disk driver and network card driver have been installed. Continue to the next step to complete the installation.

For win11 network configuration, open Settings-Network and Internet-Ethernet:

There will be two networks inside, the first network actually corresponds to vmbr0, and the second network actually corresponds to vmbr1:

The first network is used to support ipv6. Since I forgot to configure dns when configuring radvd before, although radvd automatically assigned an ipv6 address, it did not configure dns. Just add a dns address manually: < /p>

The second network is used to support ipv4. You can configure everything manually here:

If you find it troublesome, you can also install a DHCP service on the hen. I won’t introduce it here. I’ve written about it before. .

During the system installation, only the hard disk and network card drivers were installed. Now install all the remaining uninstalled drivers.

Open the virtio-win driver and double-click virtio-win-gt-x64 to start the installation:

When you created the virtual machine before, you checked the qemu agent. In order for this function to work properly, you need to double-click virtio-win-guest-tools to install the qemu agent:

Verify whether the qemu agent is normal. You can see the network information of the virtual machine in the pve panel:

The main functions of qemu agent:

https://pve.proxmox.com/wiki/Qemu-guest-agent

Finally, I want to complain about win11. I feel that this system is not suitable for upgrading now. I just installed it on a virtual machine and tried it, and then I encountered a huge funny bug. The network configuration interface just now automatically inexplicably Switching the network configuration file type, that is, from public to private, and from private to public, I feel like switching back and forth like this. It is a trivial matter to switch back and forth like this, but if I switch to the private network, the remote desktop will be disconnected, resulting in only You can go in from vnc and turn off this interface. .

Maybe this description is not clear. Let’s use a gif to appreciate it. My mouse and keyboard are not moving at all:

Recommended site searches: domain name registration website, telecom hosting, free cloud server, Alibaba Cloud domain name registration, US server rental, domain name registration number query, the cheapest dual-line space, independent IP virtual host, PHP website space overseas server ,