Newly created Windows VM fails to start right off the bat

FuriousRage

Renowned Member
Oct 17, 2014
120
4
83
Hi, i just created a windows server VM, and it just wont boot, and the logs doesnt help (me)

Code:
eb 05 13:19:59 pve pvedaemon[3998902]: VM 102 qmp command failed - VM 102 not running
Feb 05 13:19:59 pve pvedaemon[1674556]: stopping swtpm instance (pid 1674564) due to QEMU startup error
Feb 05 13:19:59 pve systemd[1]: 102.scope: Succeeded.
Feb 05 13:19:59 pve systemd[1]: 102.scope: Consumed 1.909s CPU time.
Feb 05 13:19:59 pve pvedaemon[1674551]: start failed: QEMU exited with code 1
Feb 05 13:19:59 pve pvedaemon[3992498]: <root@pam> end task UPID:pve:00198D37:1CDFAA5B:61FE6B6C:qmstart:102:root@pam: start failed: QEMU exited with code 1
Feb 05 13:20:00 pve pvedaemon[3996432]: <root@pam> starting task UPID:pve:00198D89:1CDFABED:61FE6B70:vncproxy:102:root@pam:
Feb 05 13:20:00 pve pvedaemon[1674633]: starting vnc proxy UPID:pve:00198D89:1CDFABED:61FE6B70:vncproxy:102:root@pam:
Feb 05 13:20:02 pve qm[1674635]: VM 102 qmp command failed - VM 102 not running
Feb 05 13:20:02 pve pvedaemon[1674633]: Failed to run vncproxy.
Feb 05 13:20:02 pve pvedaemon[3996432]: <root@pam> end task UPID:pve:00198D89:1CDFABED:61FE6B70:vncproxy:102:root@pam: Failed to run vncproxy.
Feb 05 13:20:24 pve pvedaemon[3992498]: <root@pam> starting task UPID:pve:00198DD5:1CDFB508:61FE6B88:qmstart:102:root@pam:
 
hi,

can you post the VM configuration qm config 102 and your pveversion -v output?
 
You can have more than one.

If you want to investigate this, you should provide the VM config from the not working VM and now also from the working one, as oguz said.
In a windows vm? Saw a text somewhere when i read, that it only supports 1 disk.
 
The problem was that i had added 2 disks, which isnt supported apparantly.
could you please run the commands on your PVE host and post the outputs here for us to take a look?