How to keep the system open when a VM crash?

[teokoul]

Hello I would like to ask a question.

I am beginner on Proxmox and I have make a small home lab with 3 VMs.

In one VM I work on CAD projects and CAD Model Rendering.

I am trying to test my VM for the rendering.

When I am trying to make more detailed CAD Model Rendering the PROXMOX server crashes.
The tower do not shutdown, but I am not able to connect on VMs or the GUI or SSH.

I do not mind if the VM with CAD Model Rendering crash. But I do not want the whole server crash.
There is any way to prevent this?

Thank you for your time!

 

[oguz]

hi,

please post more details about your VM and your setup:

qm config VMID
pveversion -v

also it would be interesting to see syslog or journal from such a crash

 

[teokoul]

hi,

please post more details about your VM and your setup:

qm config VMID
pveversion -v

also it would be interesting to see syslog or journal from such a crash

Hello oguz thank you for the reply!

Yes please!

The qm config VMID :

bios: ovmf
boot: order=ide0;ide2
cores: 4
efidisk0: local-lvm:vm-100-disk-1,size=4M
hostpci0: 09:00,pcie=1
ide0: local-lvm:vm-100-disk-0,size=150G
ide2: local:iso/virtio-win-0.1.190.iso,media=cdrom,size=489986K
machine: q35
memory: 25000
name: WindowsGPU
net0: virtio=45:3E:HK:9Y:G8:32,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=1626a95e-08d1-4e39-a71b-685101e4fd98
sockets: 4
vmgenid: 9e737340-79bf-4273-a44d-1788345e1322

The pveversion -v :

proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

I have no idea how to get a syslog or journal about the crash.
The connection just lost and then I need to shutdown the server and open again to connect.

Thank you for your time!

 

[oguz]

The connection just lost and then I need to shutdown the server and open again to connect.

i see you're doing GPU passthrough, and when you do heavy load on it it just crashed the whole machine. do you remember around what time that happened?

I have no idea how to get a syslog or journal about the crash.

there is a file /var/log/syslog and its friends, syslog.1, syslog.2.gz and so on -- those are your system logs

it would help to look at it to see what exactly happened at the time of crash. you can run ls -al /var/log/syslog* to see the files and their modification dates. please find the log for the day when the crash happened and attach it here.

and also some information about your hardware specs would be interesting

 

[teokoul]

i see you're doing GPU passthrough, and when you do heavy load on it it just crashed the whole machine. do you remember around what time that happened?


there is a file /var/log/syslog and its friends, syslog.1, syslog.2.gz and so on -- those are your system logs

it would help to look at it to see what exactly happened at the time of crash. you can run ls -al /var/log/syslog* to see the files and their modification dates. please find the log for the day when the crash happened and attach it here.

and also some information about your hardware specs would be interesting

On the time!

Because I am working on a project it just crash again.
Show give me a minute to find those log files

I believe this is the first time that I am happy for a PC crash

 

[teokoul]

i see you're doing GPU passthrough, and when you do heavy load on it it just crashed the whole machine. do you remember around what time that happened?


there is a file /var/log/syslog and its friends, syslog.1, syslog.2.gz and so on -- those are your system logs

it would help to look at it to see what exactly happened at the time of crash. you can run ls -al /var/log/syslog* to see the files and their modification dates. please find the log for the day when the crash happened and attach it here.

and also some information about your hardware specs would be interesting

My hardaware is:

MOTHERBOARD : GA-AB350M-Gaming 3
CPU: AMD Ryzen 7 1800x
RAM : 64GB
GPU: GTX 1050 Ti

My syslog file the exactly time the whole machine crash is below ( this is not the whole crash please tell me if you need the rest):

Jun  2 15:15:00 pve systemd[1]: Starting Proxmox VE replication runner...
Jun  2 15:15:01 pve systemd[1]: pvesr.service: Succeeded.
Jun  2 15:15:01 pve systemd[1]: Started Proxmox VE replication runner.
Jun  2 15:19:20 pve systemd-modules-load[499]: Inserted module 'vfio'
Jun  2 15:19:20 pve kernel: [    0.000000] Linux version 5.4.73-1-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.73-1 (Mon, 16 Nov 2020 10:52:16 +0100) ()
Jun  2 15:19:20 pve kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.73-1-pve root=/dev/mapper/pve-root ro quiet amd_iommu=on textonly video=astdrmfb video=efifb:off
Jun  2 15:19:20 pve kernel: [    0.000000] KERNEL supported cpus:
Jun  2 15:19:20 pve kernel: [    0.000000]   Intel GenuineIntel
Jun  2 15:19:20 pve kernel: [    0.000000]   AMD AuthenticAMD
Jun  2 15:19:20 pve kernel: [    0.000000]   Hygon HygonGenuine
Jun  2 15:19:20 pve kernel: [    0.000000]   Centaur CentaurHauls
Jun  2 15:19:20 pve blkmapd[521]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jun  2 15:19:20 pve kernel: [    0.000000]   zhaoxin   Shanghai 
Jun  2 15:19:20 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun  2 15:19:20 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun  2 15:19:20 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun  2 15:19:20 pve kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun  2 15:19:20 pve kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jun  2 15:19:20 pve systemd-modules-load[499]: Inserted module 'vfio_pci'
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-provided physical RAM map:
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000004cfffff] usable
Jun  2 15:19:20 pve dmeventd[524]: dmeventd ready for processing.
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000004d00000-0x0000000004ffffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000005000000-0x00000000d4cd6fff] usable
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000d4cd7000-0x00000000d4d58fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000d4d59000-0x00000000dbe42fff] usable
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000dbe43000-0x00000000dbfd5fff] reserved
Jun  2 15:19:20 pve systemd-modules-load[499]: Inserted module 'iscsi_tcp'
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000dbfd6000-0x00000000dc0ccfff] usable
Jun  2 15:19:20 pve systemd[1]: Starting Flush Journal to Persistent Storage...
Jun  2 15:19:20 pve lvm[524]: Monitoring thin pool pve-data-tpool.
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000dc0cd000-0x00000000dc4abfff] ACPI NVS
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000dc4ac000-0x00000000dcfa7fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000dcfa8000-0x00000000dcffefff] type 20
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000dcfff000-0x00000000deffffff] usable
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fdf00000-0x00000000fdffffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun  2 15:19:20 pve systemd-modules-load[499]: Inserted module 'ib_iser'
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun  2 15:19:20 pve systemd-modules-load[499]: Inserted module 'vhost_net'
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun  2 15:19:20 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000101f37ffff] usable
Jun  2 15:19:20 pve kernel: [    0.000000] NX (Execute Disable) protection: active
Jun  2 15:19:20 pve lvm[510]:   9 logical volume(s) in volume group "pve" monitored
Jun  2 15:19:20 pve kernel: [    0.000000] efi: EFI v2.50 by American Megatrends
Jun  2 15:19:20 pve kernel: [    0.000000] efi:  ACPI 2.0=0xdc0cd000  ACPI=0xdc0cd000  SMBIOS=0xf05e0  SMBIOS 3.0=0xf0600  ESRT=0xdab3ca58
Jun  2 15:19:20 pve kernel: [    0.000000] secureboot: Secure boot could not be determined (mode 0)
Jun  2 15:19:20 pve kernel: [    0.000000] SMBIOS 3.0.0 present.
Jun  2 15:19:20 pve kernel: [    0.000000] DMI: Gigabyte Technology Co., Ltd. Default string/AB350-Gaming 3-CF, BIOS F5 02/24/2017
Jun  2 15:19:20 pve lvm[510]:   4 logical volume(s) in volume group "Drive1" monitored
Jun  2 15:19:20 pve kernel: [    0.000000] tsc: Fast TSC calibration failed
Jun  2 15:19:20 pve kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun  2 15:19:20 pve kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jun  2 15:19:20 pve kernel: [    0.000000] last_pfn = 0x101f380 max_arch_pfn = 0x400000000
Jun  2 15:19:20 pve kernel: [    0.000000] MTRR default type: uncachable
Jun  2 15:19:20 pve systemd[1]: Started Flush Journal to Persistent Storage.
Jun  2 15:19:20 pve kernel: [    0.000000] MTRR fixed ranges enabled:
Jun  2 15:19:20 pve kernel: [    0.000000]   00000-9FFFF write-back
Jun  2 15:19:20 pve kernel: [    0.000000]   A0000-BFFFF write-through
Jun  2 15:19:20 pve kernel: [    0.000000]   C0000-FFFFF write-protect
Jun  2 15:19:20 pve kernel: [    0.000000] MTRR variable ranges enabled:
Jun  2 15:19:20 pve kernel: [    0.000000]   0 base 000000000000 mask FFFF80000000 write-back
Jun  2 15:19:20 pve systemd[1]: Started udev Coldplug all Devices.
Jun  2 15:19:20 pve kernel: [    0.000000]   1 base 000080000000 mask FFFFC0000000 write-back
Jun  2 15:19:20 pve kernel: [    0.000000]   2 base 0000C0000000 mask FFFFE0000000 write-back
Jun  2 15:19:20 pve systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Jun  2 15:19:20 pve kernel: [    0.000000]   3 base 0000DF000000 mask FFFFFF000000 uncachable
Jun  2 15:19:20 pve kernel: [    0.000000]   4 disabled
Jun  2 15:19:20 pve kernel: [    0.000000]   5 disabled
Jun  2 15:19:20 pve kernel: [    0.000000]   6 disabled
Jun  2 15:19:20 pve kernel: [    0.000000]   7 disabled
Jun  2 15:19:20 pve kernel: [    0.000000] TOM2: 0000001020000000 aka 66048M
Jun  2 15:19:20 pve kernel: [    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT 
Jun  2 15:19:20 pve systemd[1]: Starting udev Wait for Complete Device Initialization...
Jun  2 15:19:20 pve kernel: [    0.000000] total RAM covered: 3568M
Jun  2 15:19:20 pve kernel: [    0.000000] Found optimal setting for mtrr clean up
Jun  2 15:19:20 pve kernel: [    0.000000]  gran_size: 64K     chunk_size: 1G     num_reg: 3      lose cover RAM: 0G
Jun  2 15:19:20 pve kernel: [    0.000000] e820: update [mem 0xdf000000-0xffffffff] usable ==> reserved
Jun  2 15:19:20 pve kernel: [    0.000000] last_pfn = 0xdf000 max_arch_pfn = 0x400000000
Jun  2 15:19:20 pve systemd-udevd[583]: Using default interface naming scheme 'v240'.
Jun  2 15:19:20 pve kernel: [    0.000000] esrt: Reserving ESRT space from 0x00000000dab3ca58 to 0x00000000dab3ca90.
Jun  2 15:19:20 pve kernel: [    0.000000] e820: update [mem 0xdab3c000-0xdab3cfff] usable ==> reserved
Jun  2 15:19:20 pve kernel: [    0.000000] check: Scanning 1 areas for low memory corruption
Jun  2 15:19:20 pve kernel: [    0.000000] Using GB pages for direct mapping
Jun  2 15:19:20 pve kernel: [    0.000000] secureboot: Secure boot could not be determined (mode 0)
Jun  2 15:19:20 pve kernel: [    0.000000] RAMDISK: [mem 0x32e8f000-0x3573efff]
Jun  2 15:19:20 pve systemd-udevd[583]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: Early table checksum verification disabled
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: RSDP 0x00000000DC0CD000 000024 (v02 ALASKA)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: XSDT 0x00000000DC0CD098 0000B4 (v01 ALASKA A M I    01072009 AMI  00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: FACP 0x00000000DC0D2AC8 000114 (v06 ALASKA A M I    01072009 AMI  00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20190816/tbfadt-624)
Jun  2 15:19:20 pve systemd-udevd[556]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: DSDT 0x00000000DC0CD1E8 0058DD (v02 ALASKA A M I    01072009 INTL 20120913)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: FACS 0x00000000DC4A9C80 000040
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: APIC 0x00000000DC0D2BE0 0000DE (v03 ALASKA A M I    01072009 AMI  00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: FPDT 0x00000000DC0D2CC0 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SSDT 0x00000000DC0D2D08 008C4C (v02                 00000002 MSFT 04000000)
Jun  2 15:19:20 pve systemd[1]: Found device Samsung SSD 960 EVO 250GB 2.
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: FIDT 0x00000000DC0DB958 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SSDT 0x00000000DC0DB9F8 0020E4 (v01 AMD    AmdTable 00000001 AMD  00000001)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SRAT 0x00000000DC0DDAE0 000130 (v03 AMD    AmdTable 00000001 AMD  00000001)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: CRAT 0x00000000DC0DDC10 000F50 (v01 AMD    AmdTable 00000001 AMD  00000001)
Jun  2 15:19:20 pve systemd[1]: Found device /dev/pve/swap.
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: CDIT 0x00000000DC0DEB60 000029 (v01 AMD    AmdTable 00000001 AMD  00000001)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SSDT 0x00000000DC0DEB90 0017A1 (v01 AMD    AOD      00000001 INTL 20120913)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: MCFG 0x00000000DC0E0338 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: HPET 0x00000000DC0E0378 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SSDT 0x00000000DC0E03B0 000024 (v01 AMDFCH FCHZP    00001000 INTL 20120913)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: UEFI 0x00000000DC0E03D8 000042 (v01                 00000000      00000000)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: BGRT 0x00000000DC0E0420 000038 (v01 ALASKA ALASKAA  01072009 AMI  00010013)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: IVRS 0x00000000DC0E0458 0000D0 (v02                 00000001 AMD  00000000)
Jun  2 15:19:20 pve systemd[1]: Activating swap /dev/pve/swap...
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SSDT 0x00000000DC0E0528 0000F8 (v01 AMDFCH FCHPT    00001000 INTL 20120913)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: SSDT 0x00000000DC0E0620 001664 (v01 AMD    CPMCMN   00000001 INTL 20120913)
Jun  2 15:19:20 pve kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jun  2 15:19:20 pve kernel: [    0.000000] system APIC only can use physical flat
Jun  2 15:19:20 pve kernel: [    0.000000] Setting APIC routing to physical flat.
Jun  2 15:19:20 pve systemd[1]: Reached target Sound Card.
Jun  2 15:19:20 pve systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jun  2 15:19:20 pve systemd[1]: Created slice system-lvm2\x2dpvscan.slice.
Jun  2 15:19:20 pve systemd[1]: Starting LVM event activation on device 8:1...
Jun  2 15:19:20 pve systemd[1]: Starting LVM event activation on device 259:3...
Jun  2 15:19:20 pve lvm[694]:   7 logical volume(s) in volume group "pve" now active
Jun  2 15:19:20 pve lvm[694]:   4 logical volume(s) in volume group "Drive1" now active
Jun  2 15:19:20 pve lvm[693]:   7 logical volume(s) in volume group "pve" now active
Jun  2 15:19:20 pve lvm[693]:   4 logical volume(s) in volume group "Drive1" now active

 

[oguz]

( this is not the whole crash please tell me if you need the rest):

so the crash happened between 15:15 and 15:19 -- but there aren't any entries in that timeframe, that could indicate a power failure or a similar issue. you could check your power supply unit

 

[teokoul]

so the crash happened between 15:15 and 15:19 -- but there aren't any entries in that timeframe, that could indicate a power failure or a similar issue. you could check your power supply unit

No there is no power failure...

I don't think that is a power supply unit problem...Because the machine do not get off power just I lost the connection to my VM, Proxmox GUI and SSH.
The tower still running after that.

It needed to restart it manually.

Also it crash only when I am trying to do detailed Rendering.

What about this ??
Jun 2 15:19:20 pve kernel: [ 0.000000] gran_size: 64K chunk_size: 1G num_reg: 3 lose cover RAM: 0G

In this line Proxmox GUI has some RED signs.