Ok, ho provato a lanciare con le impostazioni indicate, riporto per completezza le opzioni con cui viene richiamato l'eseguibile "qemu":
Codice: Seleziona tutto
pgrep -a kvm|grep --color cpu
32226 /usr/bin/qemu-kvm -name guest=win-10-pro-disk,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-win-10-pro-disk/master-key.aes -machine pc-q35-4.1,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Penryn,vme=on,vmx=on,pdcm=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc_adjust=on,pdpe1gb=on -drive file=/usr/share/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/qemu/nvram/win-10-pro-disk_VARS.fd,if=pflash,format=raw,unit=1 -m 1900 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid 6c8e1e82-a089-4e56-ac24-6dd2baa716fa -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=23,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot menu=off,strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-pci-bridge,id=pci.2,bus=pci.1,addr=0x0 -device pcie-root-port,port=0x11,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x4 -device pcie-root-port,port=0x15,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x5 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x1d.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x1d -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x1d.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x1d.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -drive file=/var/lib/libvirt/images/win-10-pro-disk-1.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.5,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/var/lib/libvirt/images/win-10-pro-disk.qcow2,format=qcow2,if=none,id=drive-virtio-disk1 -device virtio-blk-pci,scsi=off,bus=pci.7,addr=0x0,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=2 -drive file=/home/joe/temp/partizionamento-virtuale/Win10_Pro_20H2_v2_Italian_x64.iso,format=raw,if=none,id=drive-sata0-0-1,media=cdrom,readonly=on -device
ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 -drive file=/home/joe/Downloads/virtio-win-0.1.185.iso,format=raw,if=none,id=drive-sata0-0-2,media=cdrom,readonly=on -device ide-cd,bus=ide.2,drive=drive-sata0-0-2,id=sata0-0-2 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:22:30:70,bus=pci.6,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=32,max_outputs=1,bus=pcie.0,addr=0x1 -device intel-hda,id=sound0,bus=pci.2,addr=0x2 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -sandbox off -messaggio timestamp=on
Anche nella tendina di modelli cpu, appare "Penryn".
Però in realtà il processore dell'host sarebbe della serie "Wolfdale"... (Core 2 Duo E8200 2.66 GHz)
Stando così le cose, siamo sicuri che sia la configurazione migliore possibile per massimizzare le prestazioni?
(fermo restando le limitazioni hardware che quelle sono e quelle restano...).