vm with Yellow exclamation mark：pve7.0-2 with 12th Intel CPU 12700

C

ccexw

New Member
Apr 3, 2023
6
0
1
12700 intel CPU
pve7.0-2
Code: 
proxmox-ve: 7.0-2 (running kernel: 5.15.102-1-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.11.22-4-pve: 5.11.22-8
ceph-fuse: 15.2.14-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

when I run a win7 virtual machine，and I running stress CPU，that was happend：

Snipaste_2023-04-03_11-02-49(1).png

cpu type : host and kvm64
 
Last edited:
ccexw said:
12700 intel CPU
pve7.0-2
Code: 
proxmox-ve: 7.0-2 (running kernel: 5.15.102-1-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.11.22-4-pve: 5.11.22-8
ceph-fuse: 15.2.14-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

when I run a win7 virtual machine，and I running stress CPU，that was happend：

View attachment 48788

cpu type : host and kvm64
Click to expand...
Hi,
before anything else please upgrade you system to the latest version of PVE and see if the issue persists. Also please post the output of your VM config which you obtain by running qm config <VMID>
 
Chris said:
Hi,
before anything else please upgrade you system to the latest version of PVE and see if the issue persists. Also please post the output of your VM config which you obtain by running qm config <VMID>
Click to expand...
thank you
here are qm config return:
Code: 
args: -vnc 0.0.0.0:5902,password=off -spice port=5904,disable-ticketing=on -device ich9-usb-ehci1,id=usb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,multifunction=on -device ich9-usb-uhci2,masterbus=usb.0,firstport=2 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4 -device nec-usb-xhci,id=usb2,bus=pci.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3
boot: order=scsi0;net0;ide2;ide0
cores: 12
ide0: local:iso/Drvceo_Win7x64.iso,media=cdrom,size=6417844K
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-i440fx-5.2
memory: 16384
name: windows7
net0: virtio=A2:85:C0:41:DC:16,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
scsi0: local-lvm:vm-100-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=b2ca589b-b58c-4567-b981-df98ea99ab3b
sockets: 1
vmgenid: 1b3c1615-8b49-459e-b1f8-2e24ced87ce9

which command let me upgrade my pve?
 
ccexw said:
thank you
here are qm config return:
Code: 
args: -vnc 0.0.0.0:5902,password=off -spice port=5904,disable-ticketing=on -device ich9-usb-ehci1,id=usb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,multifunction=on -device ich9-usb-uhci2,masterbus=usb.0,firstport=2 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4 -device nec-usb-xhci,id=usb2,bus=pci.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3
boot: order=scsi0;net0;ide2;ide0
cores: 12
ide0: local:iso/Drvceo_Win7x64.iso,media=cdrom,size=6417844K
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-i440fx-5.2
memory: 16384
name: windows7
net0: virtio=A2:85:C0:41:DC:16,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
scsi0: local-lvm:vm-100-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=b2ca589b-b58c-4567-b981-df98ea99ab3b
sockets: 1
vmgenid: 1b3c1615-8b49-459e-b1f8-2e24ced87ce9

which command let me upgrade my pve?
Click to expand...
You can upgrade your system by running apt-get upgrade && apt-get dist-upgrade or by using the WebUI by selecting the host and got to Updates. Make sure to have the correct repositories enabled, see https://pve.proxmox.com/wiki/Package_Repositories
 
Chris said:
You can upgrade your system by running apt-get upgrade && apt-get dist-upgrade or by using the WebUI by selecting the host and got to Updates. Make sure to have the correct repositories enabled, see https://pve.proxmox.com/wiki/Package_Repositories
Click to expand...
thanks
upgrade done and kernel manual update 5.19

but stress cpu failure too( vm's icon with Yellow exclamation mark)

Code: 
proxmox-ve: 7.4-1 (running kernel: 5.19.17-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.3-3
pve-kernel-5.11: 7.0-10
pve-kernel-5.19.17-2-pve: 5.19.17-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-1
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1


Code: 
args: -vnc 0.0.0.0:5902,password=off -spice port=5904,disable-ticketing=on -device ich9-usb-ehci1,id=usb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,multifunction=on -device ich9-usb-uhci2,masterbus=usb.0,firstport=2 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4 -device nec-usb-xhci,id=usb2,bus=pci.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3
boot: order=scsi0;net0;ide2;ide0
cores: 12
ide0: local:iso/Drvceo_Win7x64.iso,media=cdrom,size=6417844K
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-i440fx-5.2
memory: 16384
name: windows7
net0: virtio=A2:85:C0:41:DC:16,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
scsi0: local-lvm:vm-100-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=b2ca589b-b58c-4567-b981-df98ea99ab3b
sockets: 1
vmgenid: 1b3c1615-8b49-459e-b1f8-2e24ced87ce9

1680505997169.png
 
ccexw said:
thanks
upgrade done and kernel manual update 5.19

but stress cpu failure too( vm's icon with Yellow exclamation mark)

Code: 
proxmox-ve: 7.4-1 (running kernel: 5.19.17-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.3-3
pve-kernel-5.11: 7.0-10
pve-kernel-5.19.17-2-pve: 5.19.17-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-1
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1


Code: 
args: -vnc 0.0.0.0:5902,password=off -spice port=5904,disable-ticketing=on -device ich9-usb-ehci1,id=usb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,multifunction=on -device ich9-usb-uhci2,masterbus=usb.0,firstport=2 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4 -device nec-usb-xhci,id=usb2,bus=pci.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3
boot: order=scsi0;net0;ide2;ide0
cores: 12
ide0: local:iso/Drvceo_Win7x64.iso,media=cdrom,size=6417844K
ide2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-i440fx-5.2
memory: 16384
name: windows7
net0: virtio=A2:85:C0:41:DC:16,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
scsi0: local-lvm:vm-100-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=b2ca589b-b58c-4567-b981-df98ea99ab3b
sockets: 1
vmgenid: 1b3c1615-8b49-459e-b1f8-2e24ced87ce9

View attachment 48789
Click to expand...
Did you also reboot for the new kernel to be loaded? Also, consider using a different machine type, maybe the latest instead of 5.2
 
Chris said:
Did you also reboot for the new kernel to be loaded? Also, consider using a different machine type, maybe the latest instead of 5.2
Click to expand...
yeah,already reboot.
and use machine type i440fx 7.2/7.1/7.0/6.2/6.1/5.2
stress also failure with same error log QAQ
 
You must log in or register to reply here.
Top Bottom