[SOLVED] AMD Ryzen and Proxmox VE 7.1

D

DXS

New Member
Nov 2, 2021
13
1
3
44
I installed Proxmox VE 7.1 on the following hardware and are receiving stop errors when trying to boot from Windows ISO's. The vm are created successfully on the storage and the ISO files were tested and working. SVM has been enabled in the motherboard too.

MSI X470 Gaming Plus MAX MB
AMD RYZEN 9 3900 CPU (OEM)
KLEVV BOLT XR 64GB 3600MHz RAM
KLEVV CRAS C720 256GB M.2 PCIe 3x4 NVMe Internal Solid State Drive (SSD)

Anyone know if there are issues with Proxmox VE 7.1 and the hardware mentioned above.
 
Last edited:
What are the exact errors you're getting?
We do use CPUs from the same generation here without issues.

Please also provide the VM config and the Windows version.
 
  • Like
Reactions: Sourcenux
mira said:
What are the exact errors you're getting?
We do use CPUs from the same generation here without issues.

Please also provide the VM config and the Windows version.
Click to expand...
I just get a quick flashing black screen mentioning something about Machine UUID and it resets

balloon: 0
boot: order=ide2;ide0;net0
cores: 2
cpu: host
ide0: local-lvm:vm-100-disk-0,size=64G,ssd=1
ide2: local:iso/Windows10Pro24112021US.iso,media=cdrom
machine: pc-q35-6.1
memory: 4096
meta: creation-qemu=6.1.0,ctime=1638358884
name: DXS-SA-ISM-11
net0: e1000=DE:D1:AD:ED:44:07,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
smbios1: uuid=d0814552-2b43-4c7f-8ee7-9f7234448c36
sockets: 2
vmgenid: b18f98d8-b35c-46ba-9df7-e7cf660061fe

Microsoft Windows 10
 
Can you try it with machine type i440fx?
 
Anything in the journal during that time?

BIOS up-to-date? AMD microcode package installed [0]?
Have you checked the ISO, maybe it is corrupted?


[0] https://wiki.debian.org/Microcode
 
journalctl, or if you want the last few entries: journalctl -e.
If you want everything since the last boot: journalctl -b
 
mira said:
journalctl, or if you want the last few entries: journalctl -e.
If you want everything since the last boot: journalctl -b
Click to expand...

Dec 01 15:14:53 dxs-sa-pmx-01 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Dec 01 15:14:53 dxs-sa-pmx-01 kernel: device fwpr100p0 left promiscuous mode
Dec 01 15:14:53 dxs-sa-pmx-01 kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Dec 01 15:14:53 dxs-sa-pmx-01 qmeventd[823]: read: Connection reset by peer
Dec 01 15:14:53 dxs-sa-pmx-01 systemd[1]: 100.scope: Succeeded.
Dec 01 15:14:53 dxs-sa-pmx-01 systemd[1]: 100.scope: Consumed 59.111s CPU time.
Dec 01 15:14:53 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> end task UPID:dxs-sa-pmx-01:000718D4:008E91D9:61A7750D:vncproxy:100:root@pam: OK
Dec 01 15:14:53 dxs-sa-pmx-01 pveproxy[465215]: worker exit
Dec 01 15:14:53 dxs-sa-pmx-01 pvedaemon[465464]: starting vnc proxy UPID:dxs-sa-pmx-01:00071A38:008EAAEF:61A7754D:vncproxy:100:root@pam:
Dec 01 15:14:53 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> starting task UPID:dxs-sa-pmx-01:00071A38:008EAAEF:61A7754D:vncproxy:100:root@pam:
Dec 01 15:14:53 dxs-sa-pmx-01 qmeventd[465463]: Starting cleanup for 100
Dec 01 15:14:53 dxs-sa-pmx-01 qmeventd[465463]: trying to acquire lock...
Dec 01 15:14:54 dxs-sa-pmx-01 qm[465466]: VM 100 qmp command failed - VM 100 not running
Dec 01 15:14:54 dxs-sa-pmx-01 pvedaemon[465464]: Failed to run vncproxy.
Dec 01 15:14:54 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> end task UPID:dxs-sa-pmx-01:00071A38:008EAAEF:61A7754D:vncproxy:100:root@pam: Failed to run vncpro>
Dec 01 15:14:54 dxs-sa-pmx-01 qmeventd[465463]: OK
Dec 01 15:14:54 dxs-sa-pmx-01 qmeventd[465463]: Finished cleanup for 100
Dec 01 15:14:54 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> end task UPID:dxs-sa-pmx-01:00071A21:008EAABB:61A7754C:qmstop:100:root@pam: OK
Dec 01 15:17:01 dxs-sa-pmx-01 CRON[466086]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 01 15:17:01 dxs-sa-pmx-01 CRON[466087]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 01 15:17:01 dxs-sa-pmx-01 CRON[466086]: pam_unix(cron:session): session closed for user root
Dec 01 15:19:16 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> successful auth for user 'root@pam'
Dec 01 15:19:36 dxs-sa-pmx-01 pvedaemon[433276]: <root@pam> successful auth for user 'root@pam'
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[433276]: worker exit
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[1237]: worker 433276 finished
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[1237]: starting 1 worker(s)
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[1237]: worker 467208 started
Dec 01 15:21:56 dxs-sa-pmx-01 pvedaemon[467585]: starting termproxy UPID:dxs-sa-pmx-01:00072281:008F5008:61A776F4:vncshell::root@pam:
Dec 01 15:21:56 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> starting task UPID:dxs-sa-pmx-01:00072281:008F5008:61A776F4:vncshell::root@pam:
Dec 01 15:21:56 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> successful auth for user 'root@pam'
Dec 01 15:21:56 dxs-sa-pmx-01 login[467590]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Dec 01 15:21:56 dxs-sa-pmx-01 systemd-logind[826]: New session 53 of user root.
Dec 01 15:21:56 dxs-sa-pmx-01 systemd[1]: Started Session 53 of user root.
Dec 01 15:21:56 dxs-sa-pmx-01 login[467595]: ROOT LOGIN on '/dev/pts/0'
Dec 01 15:24:57 dxs-sa-pmx-01 pveproxy[1246]: worker 465217 finished
Dec 01 15:24:57 dxs-sa-pmx-01 pveproxy[1246]: starting 1 worker(s)
Dec 01 15:24:57 dxs-sa-pmx-01 pveproxy[1246]: worker 468864 started
Dec 01 15:25:00 dxs-sa-pmx-01 pveproxy[468862]: got inotify poll request in wrong process - disabling inotify
Dec 01 15:25:36 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> successful auth for user 'root@pam'

Is there a Proxmox process on installing amd64-microcode?
 
DXS said:
Dec 01 15:14:53 dxs-sa-pmx-01 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Dec 01 15:14:53 dxs-sa-pmx-01 kernel: device fwpr100p0 left promiscuous mode
Dec 01 15:14:53 dxs-sa-pmx-01 kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Dec 01 15:14:53 dxs-sa-pmx-01 qmeventd[823]: read: Connection reset by peer
Dec 01 15:14:53 dxs-sa-pmx-01 systemd[1]: 100.scope: Succeeded.
Dec 01 15:14:53 dxs-sa-pmx-01 systemd[1]: 100.scope: Consumed 59.111s CPU time.
Dec 01 15:14:53 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> end task UPID:dxs-sa-pmx-01:000718D4:008E91D9:61A7750D:vncproxy:100:root@pam: OK
Dec 01 15:14:53 dxs-sa-pmx-01 pveproxy[465215]: worker exit
Dec 01 15:14:53 dxs-sa-pmx-01 pvedaemon[465464]: starting vnc proxy UPID:dxs-sa-pmx-01:00071A38:008EAAEF:61A7754D:vncproxy:100:root@pam:
Dec 01 15:14:53 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> starting task UPID:dxs-sa-pmx-01:00071A38:008EAAEF:61A7754D:vncproxy:100:root@pam:
Dec 01 15:14:53 dxs-sa-pmx-01 qmeventd[465463]: Starting cleanup for 100
Dec 01 15:14:53 dxs-sa-pmx-01 qmeventd[465463]: trying to acquire lock...
Dec 01 15:14:54 dxs-sa-pmx-01 qm[465466]: VM 100 qmp command failed - VM 100 not running
Dec 01 15:14:54 dxs-sa-pmx-01 pvedaemon[465464]: Failed to run vncproxy.
Dec 01 15:14:54 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> end task UPID:dxs-sa-pmx-01:00071A38:008EAAEF:61A7754D:vncproxy:100:root@pam: Failed to run vncpro>
Dec 01 15:14:54 dxs-sa-pmx-01 qmeventd[465463]: OK
Dec 01 15:14:54 dxs-sa-pmx-01 qmeventd[465463]: Finished cleanup for 100
Dec 01 15:14:54 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> end task UPID:dxs-sa-pmx-01:00071A21:008EAABB:61A7754C:qmstop:100:root@pam: OK
Dec 01 15:17:01 dxs-sa-pmx-01 CRON[466086]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 01 15:17:01 dxs-sa-pmx-01 CRON[466087]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 01 15:17:01 dxs-sa-pmx-01 CRON[466086]: pam_unix(cron:session): session closed for user root
Dec 01 15:19:16 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> successful auth for user 'root@pam'
Dec 01 15:19:36 dxs-sa-pmx-01 pvedaemon[433276]: <root@pam> successful auth for user 'root@pam'
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[433276]: worker exit
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[1237]: worker 433276 finished
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[1237]: starting 1 worker(s)
Dec 01 15:20:49 dxs-sa-pmx-01 pvedaemon[1237]: worker 467208 started
Dec 01 15:21:56 dxs-sa-pmx-01 pvedaemon[467585]: starting termproxy UPID:dxs-sa-pmx-01:00072281:008F5008:61A776F4:vncshell::root@pam:
Dec 01 15:21:56 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> starting task UPID:dxs-sa-pmx-01:00072281:008F5008:61A776F4:vncshell::root@pam:
Dec 01 15:21:56 dxs-sa-pmx-01 pvedaemon[455554]: <root@pam> successful auth for user 'root@pam'
Dec 01 15:21:56 dxs-sa-pmx-01 login[467590]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Dec 01 15:21:56 dxs-sa-pmx-01 systemd-logind[826]: New session 53 of user root.
Dec 01 15:21:56 dxs-sa-pmx-01 systemd[1]: Started Session 53 of user root.
Dec 01 15:21:56 dxs-sa-pmx-01 login[467595]: ROOT LOGIN on '/dev/pts/0'
Dec 01 15:24:57 dxs-sa-pmx-01 pveproxy[1246]: worker 465217 finished
Dec 01 15:24:57 dxs-sa-pmx-01 pveproxy[1246]: starting 1 worker(s)
Dec 01 15:24:57 dxs-sa-pmx-01 pveproxy[1246]: worker 468864 started
Dec 01 15:25:00 dxs-sa-pmx-01 pveproxy[468862]: got inotify poll request in wrong process - disabling inotify
Dec 01 15:25:36 dxs-sa-pmx-01 pvedaemon[436310]: <root@pam> successful auth for user 'root@pam'

Is there a Proxmox process on installing amd64-microcode?
Click to expand...
Scratch the last question I got the AMD64-microcode installed, I'll let you know of the results
 
Could you provide the log from a complete start?
This one only contains the end of the VM stop.
 
Thank you for the log.
Sadly, even with the additional info containing the start, there's nothing in the log that would explain this issue.

Have you tried other ISOs as well, for example Linux ones?
 
mira said:
Thank you for the log.
Sadly, even with the additional info containing the start, there's nothing in the log that would explain this issue.

Have you tried other ISOs as well, for example Linux ones?
Click to expand...

Ubuntu 20.04 installed fine without any issues...I have tried Windows 21H2 but it's not working, seems that it might be a driver issue
 
DXS said:
Ubuntu 20.04 installed fine without any issues...I have tried Windows 21H2 but it's not working, seems that it might be a driver issue
Click to expand...
In this case I suggest trying Windows 10 LTSC 2019 but not version (Windows 10 LTSC 2021)

Listing
Start Date​
Mainstream End Date​
Extended End Date​
Windows 10 Enterprise LTSC 2019
Nov 13, 2018​
Jan 9, 2024​
Jan 9, 2029​

Listing
Start Date​
Mainstream End Date​
Windows 10 Enterprise LTSC 2021
Nov 16, 2021​
Jan 12, 2027​
 
Last edited:
0bit said:
In this case I suggest trying Windows 10 LTSC 2019 but not version (Windows 10 LTSC 2021)

Listing
Start Date​
Mainstream End Date​
Extended End Date​
Windows 10 Enterprise LTSC 2019
Nov 13, 2018​
Jan 9, 2024​
Jan 9, 2029​

Listing
Start Date​
Mainstream End Date​
Windows 10 Enterprise LTSC 2021
Nov 16, 2021​
Jan 12, 2027​
Click to expand...
That doesn't boot either, I've' tried our Windows Server 2016 Standard edition as well, still no luck
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom