Search results

Wow, that way AMD's core graphics can't be used for passthrough

It is exactly what I have done,But I can't start him

I tried typing dmesg | grep nomode, but according to the information returned to me, I did not type correctly root@pve:~# dmesg | grep nomode root@pve:~#

Sorry, I did, but it still doesn't work swtpm_setup: Not overwriting existing state file. TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name win10 -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev...

can, the display is waiting for nuclear display, did I not cancel the occupancy of nuclear display? root@pve:~# tail -n 200 /var/log/syslog Jan 27 18:50:00 pve kernel: [ 514.580205] vfio-pci 0000:06:00.0: vfio_ecap_init: hiding ecap 0xffff@0xffc Jan 27 18:50:00 pve kernel: [ 514.580205]...

I don't know the reason, I can't start the virtual machine if I select the AMD core display, but I can start it without selecting the core display. Could it be a compatibility reason?

Yes, without pass-through AMD core display can start normally

Yes, but you can't call AMD's core graphics

bios: ovmf boot: order=sata0;ide2;net0;sata1 cores: 6 cpu: host efidisk0: local-lvm:vm-100-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M ide2: local:iso/Windows10.iso,media=cdrom machine: pc-q35-6.1 memory: 4096 meta: creation-qemu=6.1.0,ctime=1643026447 name: win10 net0...

Hello, I am using this for the first time, can you help me how to debug it? I mounted the AMD core display virtual machine and can't start it, but canceling the AMD core display virtual machine can start, why is that?

OK 400 Parameter verification failed. vmid: type check ('integer') failed - got 'VMID' qm config <vmid> [OPTIONS] root@pve:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve) pve-manager: 7.1-7 (running version: 7.1-7/df5740ad) pve-kernel-helper: 7.1-6 pve-kernel-5.13: 7.1-5...

Can anyone help me, I am using AMD5600g core display pass-through, and the installation of win10 does not start and keeps reporting an error, what is the reason? swtpm_setup: Not overwriting existing state file. TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name win10 -no-shutdown...