Windows 10/11

B

b14ckfoot

New Member
Feb 26, 2025
5
0
1
VM 303 qmp command 'set_password' failed - unable to connect to VM 303 qmp socket - timeout after 51 retries
TASK ERROR: Failed to run vncproxy.


I cant seem to get any windows working on my proxmox anymore. Just debian linux and other linux's. Can someone help me. ChatGPT has been assisting with this but after 6hrs i figured id ask for help here .
 
root@PromoxMain:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
qm config 303

bios: ovmf
boot: order=scsi0;ide0;ide2;net0;ide1
cores: 2
cpu: x86-64-v2-AES
ide0: local:iso/virtio-win.iso,media=cdrom,size=512
ide1: local:iso/virtio-win.iso,media=cdrom,size=512
ide2: local:iso/Windows_10_64_real.iso,media=cdrom,size=4779200K
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1740550305
name: Windows10
net0: virtio=BC:24:11:A8:01:31,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: hdd3:303/vm-303-disk-0.qcow2,iothread=1,size=50G
scsihw: virtio-scsi-single
smbios1: uuid=af43e902-aa9b-49fc-be54-a7614a9a9e9e
sockets: 1
vmgenid: 58a8c9d3-32a3-4655-920e-96076e1f63c3


I can get it to boot after shutdown -r now on my proxmox, but it wont read the drivers to read storage devices even after include virtio
 
so i got 11 working with restarts and a different ISO of Virt IO

Ill try 10 again, it just sucks that i have to restart my whole server to get it to work
 
b14ckfoot said:
I can get it to boot after shutdown -r now on my proxmox, but it wont read the drivers to read storage devices even after include virtio
Click to expand...
I know of three ways to solve this:
  • load current virtio-drivers during installation into the windows installer. this should be easiest
  • integrate the virtio-drivers into the installation iso
  • install with default scsi controller and sata disk, install virtio-drivers after system is installed. Make windows load the drivers on boot by attaching an additional disk by scsi first. Reboot vm. afterwards remove additional disk and change boot disk to virtio/scsi.
 
fba said:
I know of three ways to solve this:
  • load current virtio-drivers during installation into the windows installer. this should be easiest
  • integrate the virtio-drivers into the installation iso
  • install with default scsi controller and sata disk, install virtio-drivers after system is installed. Make windows load the drivers on boot by attaching an additional disk by scsi first. Reboot vm. afterwards remove additional disk and change boot disk to virtio/scsi.
Click to expand...
i got both of them to work! I freaking had a virtio iso with on 300b not 700mb like a the new i got! I simply overlooked that i had the wrong virt io! Thank you so much!
 
You must log in or register to reply here.
Top Bottom