System Halt

[petercheunghk]

Hi , i am a junior t using PVE , Today i am changing my physical OS(PFsense) to a Virtual OS based on PVE, but after a few minutes the system halted, need to force reboot of the device.
After reboot the device i view the syslog

Apr 19 16:48:57 pve pvestatd[982]: starting server
Apr 19 16:48:57 pve pve-firewall[983]: starting server
Apr 19 16:48:57 pve systemd[1]: Started pve-firewall.service - Proxmox VE firewall.
Apr 19 16:48:57 pve systemd[1]: Started pvestatd.service - PVE Status Daemon.
Apr 19 16:48:57 pve kernel: bpfilter: Loaded bpfilter_umh pid 987
Apr 19 16:48:57 pve unknow: Started bpfilter
Apr 19 16:48:57 pve kernel: igc 0000:03:00.0 enp3s0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Apr 19 16:48:57 pve kernel: vmbr2: port 1(enp3s0) entered blocking state
Apr 19 16:48:57 pve kernel: vmbr2: port 1(enp3s0) entered forwarding state
Apr 19 16:48:57 pve pvedaemon[1010]: starting server
Apr 19 16:48:57 pve pvedaemon[1010]: starting 3 worker(s)
Apr 19 16:48:57 pve pvedaemon[1010]: worker 1011 started
Apr 19 16:48:57 pve pvedaemon[1010]: worker 1012 started
Apr 19 16:48:57 pve pvedaemon[1010]: worker 1013 started
Apr 19 16:48:57 pve systemd[1]: Started pvedaemon.service - PVE API Daemon.
Apr 19 16:48:57 pve systemd[1]: Starting pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon...
Apr 19 16:48:57 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Apr 19 16:48:58 pve pve-ha-crm[1018]: starting server
Apr 19 16:48:58 pve pve-ha-crm[1018]: status change startup => wait_for_quorum
Apr 19 16:48:58 pve systemd[1]: Started pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon.
Apr 19 16:48:58 pve kernel: igc 0000:07:00.0 enp7s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 19 16:48:58 pve kernel: vmbr5: port 1(enp7s0) entered blocking state
Apr 19 16:48:58 pve kernel: vmbr5: port 1(enp7s0) entered forwarding state
Apr 19 16:48:58 pve pveproxy[1019]: starting server
Apr 19 16:48:58 pve pveproxy[1019]: starting 3 worker(s)
Apr 19 16:48:58 pve pveproxy[1019]: worker 1020 started
Apr 19 16:48:58 pve pveproxy[1019]: worker 1021 started
Apr 19 16:48:58 pve pveproxy[1019]: worker 1022 started
Apr 19 16:48:58 pve systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Apr 19 16:48:58 pve systemd[1]: Starting pve-ha-lrm.service - PVE Local HA Resource Manager Daemon...
Apr 19 16:48:58 pve systemd[1]: Starting spiceproxy.service - PVE SPICE Proxy Server...
Apr 19 16:48:58 pve kernel: igc 0000:01:00.0 enp1s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
Apr 19 16:48:58 pve kernel: vmbr0: port 1(enp1s0) entered blocking state
Apr 19 16:48:58 pve kernel: vmbr0: port 1(enp1s0) entered forwarding state
Apr 19 16:48:59 pve spiceproxy[1025]: starting server
Apr 19 16:48:59 pve spiceproxy[1025]: starting 1 worker(s)
Apr 19 16:48:59 pve spiceproxy[1025]: worker 1026 started
Apr 19 16:48:59 pve systemd[1]: Started spiceproxy.service - PVE SPICE Proxy Server.
Apr 19 16:48:59 pve pve-ha-lrm[1027]: starting server
Apr 19 16:48:59 pve pve-ha-lrm[1027]: status change startup => wait_for_agent_lock
Apr 19 16:48:59 pve systemd[1]: Started pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
Apr 19 16:48:59 pve systemd[1]: Starting pve-guests.service - PVE guests...
Apr 19 16:49:00 pve pve-guests[1030]: <root@pam> starting task UPID:pve:00000407:00000466:66222FFC:startall::root@pam:
Apr 19 16:49:00 pve pvesh[1030]: Starting VM 100
Apr 19 16:49:00 pve pve-guests[1031]: <root@pam> starting task UPID:pve:00000408:00000467:66222FFC:qmstart:100:root@pam:
Apr 19 16:49:00 pve pve-guests[1032]: start VM 100: UPID:pve:00000408:00000467:66222FFC:qmstart:100:root@pam:
Apr 19 16:49:00 pve kernel: kvm[1033]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Apr 19 16:49:00 pve systemd[1]: Created slice qemu.slice - Slice /qemu.
Apr 19 16:49:00 pve systemd[1]: Started 100.scope.
Apr 19 16:49:01 pve kernel: tap100i0: entered promiscuous mode
Apr 19 16:49:01 pve kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Apr 19 16:49:01 pve kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Apr 19 16:49:01 pve kernel: fwpr100p0: entered allmulticast mode
Apr 19 16:49:01 pve kernel: fwpr100p0: entered promiscuous mode
Apr 19 16:49:01 pve kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Apr 19 16:49:01 pve kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Apr 19 16:49:01 pve kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Apr 19 16:49:01 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Apr 19 16:49:01 pve kernel: fwln100i0: entered allmulticast mode
Apr 19 16:49:01 pve kernel: fwln100i0: entered promiscuous mode
Apr 19 16:49:01 pve kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Apr 19 16:49:01 pve kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Apr 19 16:49:01 pve kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Apr 19 16:49:01 pve kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Apr 19 16:49:01 pve kernel: tap100i0: entered allmulticast mode
Apr 19 16:49:01 pve kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Apr 19 16:49:01 pve kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Apr 19 16:49:01 pve kernel: tap100i1: entered promiscuous mode
Apr 19 16:49:01 pve kernel: vmbr1: port 2(tap100i1) entered blocking state
Apr 19 16:49:01 pve kernel: vmbr1: port 2(tap100i1) entered disabled state
Apr 19 16:49:01 pve kernel: tap100i1: entered allmulticast mode
Apr 19 16:49:01 pve kernel: vmbr1: port 2(tap100i1) entered blocking state
Apr 19 16:49:01 pve kernel: vmbr1: port 2(tap100i1) entered forwarding state
Apr 19 16:49:02 pve kernel: tap100i2: entered promiscuous mode
Apr 19 16:49:02 pve kernel: vmbr2: port 2(tap100i2) entered blocking state
Apr 19 16:49:02 pve kernel: vmbr2: port 2(tap100i2) entered disabled state
Apr 19 16:49:02 pve kernel: tap100i2: entered allmulticast mode
Apr 19 16:49:02 pve kernel: vmbr2: port 2(tap100i2) entered blocking state
Apr 19 16:49:02 pve kernel: vmbr2: port 2(tap100i2) entered forwarding state
Apr 19 16:49:02 pve kernel: tap100i3: entered promiscuous mode
Apr 19 16:49:02 pve kernel: vmbr3: port 2(tap100i3) entered blocking state
Apr 19 16:49:02 pve kernel: vmbr3: port 2(tap100i3) entered disabled state
Apr 19 16:49:02 pve kernel: tap100i3: entered allmulticast mode
Apr 19 16:49:02 pve kernel: vmbr3: port 2(tap100i3) entered blocking state
Apr 19 16:49:02 pve kernel: vmbr3: port 2(tap100i3) entered forwarding state
Apr 19 16:49:03 pve kernel: tap100i4: entered promiscuous mode
Apr 19 16:49:03 pve kernel: vmbr4: port 2(tap100i4) entered blocking state
Apr 19 16:49:03 pve kernel: vmbr4: port 2(tap100i4) entered disabled state
Apr 19 16:49:03 pve kernel: tap100i4: entered allmulticast mode
Apr 19 16:49:03 pve kernel: vmbr4: port 2(tap100i4) entered blocking state
Apr 19 16:49:03 pve kernel: vmbr4: port 2(tap100i4) entered forwarding state
Apr 19 16:49:03 pve kernel: tap100i5: entered promiscuous mode
Apr 19 16:49:03 pve kernel: vmbr5: port 2(tap100i5) entered blocking state
Apr 19 16:49:03 pve kernel: vmbr5: port 2(tap100i5) entered disabled state
Apr 19 16:49:03 pve kernel: tap100i5: entered allmulticast mode
Apr 19 16:49:03 pve kernel: vmbr5: port 2(tap100i5) entered blocking state
Apr 19 16:49:03 pve kernel: vmbr5: port 2(tap100i5) entered forwarding state
Apr 19 16:49:04 pve kernel: platform INT3515:04: deferred probe pending
Apr 19 16:49:07 pve pve-guests[1030]: <root@pam> end task UPID:pve:00000407:00000466:66222FFC:startall::root@pam: OK
Apr 19 16:49:07 pve systemd[1]: Finished pve-guests.service - PVE guests.
Apr 19 16:49:07 pve systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Apr 19 16:49:07 pve pveproxy[1020]: detected empty handle
Apr 19 16:49:08 pve pvescheduler[1246]: starting server

May i know , how to solve the problem , thank