1 check firewall service status
systemctl status firewalld

2 check firewall status
firewall-cmd --state

3 open,restart,close firewalld service

# start
service firewalld start
# restart
service firewalld restart
# close
service firewalld stop

4 check firewall rules
firewall-cmd --list-all

5 edit rules

# check open port
firewall-cmd --query-port=8080/tcp
# open 80 port
firewall-cmd --permanent --add-port=80/tcp
# remove port
firewall-cmd --permanent --remove-port=8080/tcp
#restart firewall (need restart firewall after config change)
firewall-cmd --reload 

First step, after entering Win10 system, we click on the “Start” menu in the lower left corner of Win10 system computer desktop, select the “Run” option, enter the regedit character command in the open operation dialog box, and press the Enter key.

Second, in the open registry editor interface, click the “Edit” and “Find” options, and enter the “F5FB2C77-0E2F-4A16-A381-3E560C68BC83” option in the search target in the pop-up search dialog box.

Step 3, click Search: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\DelegateFolders\{F5FB2C77-0E2F-4A16-A381-3E560C68BC83} option, right-click the rename option “{F5FB2C77-0E2F-4A16-A381-3E560C68BC83}” to “-{F5FB2C77-0E2F-4A16-A381-3E560C68BC83}”

For some users VM’s audio slows down/starts stuttering/becomes demonic after a while when it is pumped through HDMI on the video card. This usually also slows down graphics. A possible solution consists of enabling MSI (Message Signaled-Based Interrupts) instead of the default (Line-Based Interrupts).

In order to check whether MSI is supported or enabled, run the following command as root:
lspci -vs $device | grep 'MSI:'
where $device is the card’s address (e.g. 01:00.0).
The output should be similar to:
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
A – after Enable means MSI is supported, but not used by the VM, while a + says that the VM is using it.

Checking for PCI devices working in MSI-mode.
Go to Device Manager. Click in menu “View -> Resources by type”. Expand “Interrupt request (IRQ)” node of the tree. Scroll down to “(PCI) 0x… (…) device name” device nodes. Devices with positive number for IRQ (like “(PCI) 0x00000011 (17) …”) are in Line-based interrupts-mode. Devices with negative number for IRQ (like “(PCI) 0xFFFFFFFA (-6) …”) are in Message Signaled-based Interrupts-mode.

Trying to switch device to MSI-mode.
You must locate device`s registry key. Invoke device properties dialog. Switch to “Details” tab. Select “Device Instance Path” in “Property” combo-box. Write down “Value” (for example “PCI\VEN_1002&DEV_4397&SUBSYS_1609103C&REV_00\3&11583659&0&B0”). This is relative registry path under the key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\”.

Go to that device`s registry key (“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1002&DEV_4397&SUBSYS_1609103C&REV_00\3&11583659&0&B0”) and locate down the subkey “Device Parameters\Interrupt Management”. For devices working in MSI-mode there will be subkey “Device Parameters\Interrupt Management\MessageSignaledInterruptProperties” and in that subkey there will be DWORD value “MSISupported” equals to “0x00000001”. To switch device from legacy- to MSI-mode just add these subkey and value.

Before adding these key and value (or changing “MSISupported” to “0x00000001” in case subkey and value already exist) you have to perform safety steps like doing backup (creating system restore point at least).

Do tweak one device -> reboot and check (1) if it is displayed in Device Manager as correctly working device; (2) if its IRQ became negative -> if no (1) and no (2) then either remove subkey “MessageSignaledInterruptProperties” (if you added it) or change “MSISupported” to “0x00000000” and reboot.

Theoretically if device driver (and platform = chipset) unable to perform in MSI-mode it should ignore mentioned subkey and value.

When start windows.It get a blue screen crash like follow. And you can’t fix it by windows fix software.

Recovery
 Your PC/Device needs to be repaired
 The Boot Configuration Data file doesn't contain valid information for an operating system.
 File: \BCD
 Error code: 0x0000098
 You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.

Access the Command Prompt like you did before and try the following:

• Type Bootrec /RebuildBcd, and then press ENTER.

If the Bootrec.exe tool runs successfully, it presents you with an installation path of a Windows directory.
To add the entry to the BCD store, type Yes. A confirmation message appears that indicates the entry was added successfully.

If the Bootrec.exe tool cannot locate any missing Windows installations, you must remove the BCD store, and then you must re-create it.
To do this, type the following commands in bold in the order which they are presented:

• Bcdedit /export C:\BCD_Backup
• ren c:\boot\bcd bcd.old
• Bootrec /rebuildbcd

We use chmod command to change permissions of folders and files.

root@pve:~# chmod --help
 Usage: chmod [OPTION]… MODE[,MODE]… FILE…
   or:  chmod [OPTION]… OCTAL-MODE FILE…
   or:  chmod [OPTION]… --reference=RFILE FILE…
 Change the mode of each FILE to MODE.
 With --reference, change the mode of each FILE to that of RFILE.
 -c, --changes          like verbose but report only when a change is made
   -f, --silent, --quiet  suppress most error messages
   -v, --verbose          output a diagnostic for every file processed
       --no-preserve-root  do not treat '/' specially (the default)
       --preserve-root    fail to operate recursively on '/'
       --reference=RFILE  use RFILE's mode instead of MODE values
   -R, --recursive        change files and directories recursively
       --help     display this help and exit
       --version  output version information and exit

For example:

chmod -R 777 /home/rockfuns

Local source configuration method

Go into /etc/yum.reps.d/ directory and create a file ending with .repo.The content like follow.

[base]
name=cdrom          #cdrom is notes.it can write casually.
baseurl=file:///mnt/    #local cdrom's path. path of the yum source.
enabled=1
gpgcheck=0        #Check the legitimacy of the yum source.when the value is 1,need follow line.
#gpgkey=URL #check url

use command yum clean all and yum repolist to make metadata.after these you can use local yum.

External network configuration method

1 backup the yum source that the system had when you install.
mv /etc/yum.repos.d/*.repo /etc/yum/repos.d/repo_backup/

2 download new yum source.
wget http://mirrors.aliyun.com/repo/Centos-7.repo
also use command yum clean all and yum repolist to make metadata

Or you can modify the source list file under Debian linux system.
vi /etc/apt/sources.list
add yum source address into it.For example:

#source address of Aliyun
deb http://mirrors.aliyun.com/ubuntu/ trusty main restricted universe multiverse
 deb http://mirrors.aliyun.com/ubuntu/ trusty-security main restricted universe multiverse
 deb http://mirrors.aliyun.com/ubuntu/ trusty-updates main restricted universe multiverse
 deb http://mirrors.aliyun.com/ubuntu/ trusty-proposed main restricted universe multiverse
 deb http://mirrors.aliyun.com/ubuntu/ trusty-backports main restricted universe multiverse
 deb-src http://mirrors.aliyun.com/ubuntu/ trusty main restricted universe multiverse
 deb-src http://mirrors.aliyun.com/ubuntu/ trusty-security main restricted universe multiverse
 deb-src http://mirrors.aliyun.com/ubuntu/ trusty-updates main restricted universe multiverse
 deb-src http://mirrors.aliyun.com/ubuntu/ trusty-proposed main restricted universe multiverse
 deb-src http://mirrors.aliyun.com/ubuntu/ trusty-backports main restricted universe multiverse

run apt-get update.Then you can install software by new source.

Virtual graphics card performance is too weak.we need to use real graphics card to improve display performance.

Before starting passthough gpu card.Make sure something right first.

1 your passthough card is AMD card.
Because NVDIA company made a check in their video card drivers.If it found that the system is VM system.The driver will stop working.Although there is a way to bypass the drive blockade, it is troublesome.AMD gpu cards don’t have this problem.

2 Your gpu card support UEFI bios.
Although traditional seabios can also be passthough successful.But there are always strange problems.
For example.My card RX560.Running score under real system can reach 70,000 points.It can work normal under UEFI mode and reach 68,000 points.But only get 7,000 points under seabios mode.And if I run GPU-Z. The guest system windows get blue screen crash and whole system crash completely.

Now we can start passthough work.

1 enable UEFI boot in your Physical machine bios.
If your machine do not suport UEFI mode.It doesn’t matter.We can dump gpu card bios and use it as a file in proxmox.

2 modify /etc/default/grub
vi /etc/default/grub
found GRUB_CMDLINE_LINUX_DEFAULT="quiet" line.
intel cpu: modify to GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt video=efifb:off"
amd cpu: modify to GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt video=efifb:off"
Then save the file and run update-grub.

3 modify /etc/modules
vi /etc/modules
add following things.it can’t change the order

 vfio
 vfio_iommu_type1
 vfio_pci
 vfio_virqfd

Then save and run update-initramfs -u -k all.

4 add gpu card ID.
how to get gpu card id.
first run lspci. we can get a list about pci devices.

We can found that the line which start with “02:00” is my gpu card.
02:00.0 is gpu device.
02:00.1 is hdmi audio device that on gpu card.

02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] (rev cf)

02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0

Then we run lspci -n -s 02:00 to get card ID.

root@pve:~# lspci -n -s 02:00

02:00.0 0300: 1002:67ff (rev cf)

02:00.1 0403: 1002:aae0

root@pve:~#

Run commands.

echo "options vfio-pci ids=1002:67ff,1002:aae0" > /etc/modprobe.d/vfio.conf
echo "options vfio_iommu_type1 allow_unsafe_interrupts=1" > /etc/modprobe.d/vfio_iommu_type1.conf

modprobe kvm ignore_msrs=y
modprobe kvm_intel nested=y ept=y

5 modify /etc/modprobe.d/pve-blacklist.conf
add content to blacklist drivers

blacklist nvidiafb 
blacklist nouveau 
blacklist nvidia 
blacklist radeon 
blacklist amdgpu

Then run update-initramfs -u -k all
After thest.Reboot your proxmox system.

6 Configure your guest system configuration
copy your UEFI bios which dump from gpu card(Use gpu-z to dump it or it can download from other web site) to /usr/share/kvm dir with vbios.bin name.

add pci device in hardware list.




The rom-file parameter can’t set by web mode.
You can modify VM config file directly after add pci device.
All VM guest config files are in /etc/pve/nodes/pve/qemu-server/.
Modify conf file with guest system id.
Likevi /etc/pve/nodes/pve/qemu-server/105.conf

After these.Your can find your gpu-card in your guest system.Install driver and works.

Sometimes we what use harddisk in guest system passthough.So if the disk move to other machine.The data can read directly.

We can check harddisk name in shell.In linux, all hardwares are in /dev directory.
For hardisk,we can get disk id in /dev/disk/by-id .

In the picture which with red box is the harddisk id.

In proxmox,it is very easy to passthough the harddisk to guest system by using qm tools.

for example:
qm set 100 --sata0 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_drive-scsi1
In this command. 100 is the guest system id. –sata0 is the hardisk bus type that you want use in guest system.There are (–ide,–sata,–scsi,–virtio) types.The number follow the type can’t repeat.You can have only 4 ide,6 sata,14 scsi and 16 virtio equipments.




Than we can see the disk in guest hardware list now.

In the last.Remember do not passthogh the harddisk that proxmox install in.

Proxmox VE is a complete open-source platform for all-inclusive enterprise virtualization that tightly integrates KVM hypervisor and LXC containers, software-defined storage and networking functionality on a single platform, and easily manages high availability clusters and disaster recovery tools with the built-in web management interface.

We can get ISO image from https://www.proxmox.com/en/downloads.
The newest version is 5.4-1.

After download.We can burn the image into cd-r or usb.Then we can start the installation.

Set first boot option to cd-rom or usb-disk in bios.When system startup.We can see this screen.

Choose first select Install Proxmox VE.


Choose I agree.


Select which harddisk we want the proxmox install to.Then next.


Set your country/time zone and keyboard.


Set administrator password and email.


If you have multiple netowork cards.Select one that you want admin port used to.
And manual setting ip.You can’t get ip via DHCP.


Start installation after confirming that there’s no problem.


Finish installation.User another computer.Open https://192.168.1.124:8006 via browser.


Use the password that set during installation.


The no vaild subscription box can removed by modify config file.


Start the shell.enter command line.
vi /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
find the line which has content if (data.status !== 'Active') {

modify it to if (false) {


Logout the account and close the browser.Then relogin.The alert box disappeared now.

BTW.There’s some bug with default vi tools on this version.We can reinstall vim tool to solved this problem.
apt-get remove vim-common
apt-get install vim

Sometimes when we run ls to list files.There’s only black background with white words.We can’t see file/dir or executable easyly.

There’s a file named .bashrc under user folder.Such like /root/.bashrc
We can modify this file and add a command line.
alias ls='ls --color'

After reboot system.Different colors could be showed for different file types.