Thanks! I'll try to upgrade to 6.2 kernel, this is the only difference
Le vendredi 02 juin 2023 à 18:09 +0200, Aaron Lauterer a écrit : > > > On 6/2/23 16:15, DERUMIER, Alexandre wrote: > > Thanks Aeron. > > > > I'll try to reproduce on my side on epyc milan. > > AMD EPYC 7543 32-Core Processor microcode patch_level=0x0a0011ce > > (I just tried again with q35, but I'm still not able de reproduce) > > > > > > can you share your full vmid.conf ? (numa ? vga ?..). > > > On the Epyc Systems: > > args: -cpu > Nehalem,enforce,+aes,-svm,- > vmx,+kvm_pv_eoi,+kvm_pv_unhalt,vendor="GenuineIntel" > bios: ovmf > boot: order=scsi0;ide2;net0 > cores: 2 > cpu: host,flags=+aes > efidisk0: local-storage:vm-104-disk-0,efitype=4m,size=1M > ide2: iso-images:iso/debian-11.7.0-amd64- > netinst.iso,media=cdrom,size=389M > machine: q35 > memory: 2048 > meta: creation-qemu=7.2.0,ctime=1685631249 > name: tmp-debtest > net0: virtio=26:A2:08:6B:00:8F,bridge=vmbr0,firewall=1 > numa: 0 > ostype: l26 > scsi0: local-storage:vm-104-disk-1,discard=on,iothread=1,size=8G > scsihw: virtio-scsi-single > smbios1: uuid=ef95de37-c93f-4987-820d-4f969913b03d > sockets: 1 > vmgenid: cb42b08c-9448-4821-b1e6-d018150de807 > > > On the Ryzen system: > > args: -cpu > kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+sep,+lahf_lm,+popcnt,+sse4. > 1,+sse4.2,+ssse3 > bios: ovmf > boot: order=scsi0;ide2;net0 > cores: 4 > cpu: kvm64 > efidisk0: local-zfs:vm-115-disk-1,efitype=4m,size=1M > ide2: iso:iso/debian-11.6.0-amd64-netinst.iso,media=cdrom,size=388M > machine: q35 > memory: 2048 > meta: creation-qemu=7.2.0,ctime=1685537448 > name: debtest > net0: virtio=AA:AA:7A:3A:F5:94,bridge=vmbr0,firewall=1 > numa: 0 > ostype: l26 > scsi0: local-zfs:vm-115-disk-0,iothread=1,size=32G > scsihw: virtio-scsi-single > smbios1: uuid=05785fd0-69b7-4df7-a96e-962e030cdbca > sockets: 1 > vmgenid: 869bd693-3560-4cd1-a5be-f61ec158acef > > > The CPU args are different, depending on what I tested last tested. > > > > do you use debian graphical install or console install ? > > the cli installer > > > > > host kernel version ? (I'm still testing on 5.15 / qemu 7.4) > > On the Epyc Systems: > $ pveversion -v > proxmox-ve: 7.4-1 (running kernel: 6.2.6-1-pve) > pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a) > pve-kernel-6.2: 7.3-8 > pve-kernel-5.15: 7.3-3 > pve-kernel-6.2.6-1-pve: 6.2.6-1 > pve-kernel-5.15.102-1-pve: 5.15.102-1 > pve-kernel-5.15.5-1-pve: 5.15.5-1 > (…) > qemu-server: 7.4-3 > > On the Ryzen System: > $ pveversion -v > proxmox-ve: 7.4-1 (running kernel: 6.2.11-2-pve) > pve-manager: 7.4-4 (running version: 7.4-4/4a8501a8) > pve-kernel-6.2: 7.4-3 > pve-kernel-5.15: 7.4-3 > pve-kernel-6.2.11-2-pve: 6.2.11-2 > pve-kernel-6.2.11-1-pve: 6.2.11-1 > pve-kernel-5.15.107-2-pve: 5.15.107-2 > (…) > qemu-server: 7.4-3 > > > > > my last patch version use qemu64 as base without specifify the > > vendor, > > so I think it should ok, but I would like to find what happend > > exactly > > :) > > > > > > > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
