Problem with qm guest exec on windows

[kiteskate]

Hi,

I'm having trouble with qm guest exec answering randomly, i did not found any pattern.
It is not responding each time when qemu-agent is launch as a service, but everything is working fine and i got answer each time when launch as adminstrator in console

Tested on the last proxmox release 6.3 freshly updated and 6.2 before that

Do someone have any clue

TIA

root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exited" : 1,
   "signal" : -1073741502
}
root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exited" : 1,
   "signal" : -1073741502
}
root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exited" : 1,
   "signal" : -1073741502
}
root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exited" : 1,
   "signal" : -1073741502
}
root@proxmox2:~# qm guest exec 104 ipconfig
^[[A{
   "exitcode" : 0,
   "exited" : 1,
   "out-data" : "\r\nConfiguration IP de Windows\r\n\r\n\r\nCarte Ethernet Ethernet :\r\n\r\n   Suffixe DNS propre ▒ la connexion. . . : lan\r\n   Adresse IPv6 de liaison locale. . . . .: fe80::9946:77d8:afb6:564f%2\r\n   Adresse IPv4. . . . . . . . . . . . . .: 192.168.100.241\r\n   Masque de sous-r▒seau. . . .▒. . . . . : 255.255.255.0\r\n   Passerelle par d▒faut. . . .▒. . . . . : 192.168.100.1\r\n\r\nCarte Tunnel Teredo Tunneling Pseudo-Interface :\r\n\r\n   Suffixe DNS propre ▒ la connexion. . . : \r\n   Adresse IPv6. . . . . . . . . . .▒. . .: 2001:0:2851:782c:2cfb:38c4:3f57:9b0e\r\n   Adresse IPv6 de liaison locale. . . . .: fe80::2cfb:38c4:3f57:9b0e%3\r\n   Passerelle par d▒faut. . . .▒. . . . . : ::\r\n"
}
root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exited" : 1,
   "signal" : -1073741502
}
root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exited" : 1,
   "signal" : -1073741502
}
root@proxmox2:~# qm guest exec 104 ipconfig
{
   "exitcode" : 0,
   "exited" : 1,
   "out-data" : "\r\nConfiguration IP de Windows\r\n\r\n\r\nCarte Ethernet Ethernet :\r\n\r\n   Suffixe DNS propre ▒ la connexion. . . : lan\r\n   Adresse IPv6 de liaison locale. . . . .: fe80::9946:77d8:afb6:564f%2\r\n   Adresse IPv4. . . . . . . . . . . . . .: 192.168.100.241\r\n   Masque de sous-r▒seau. . . .▒. . . . . : 255.255.255.0\r\n   Passerelle par d▒faut. . . .▒. . . . . : 192.168.100.1\r\n\r\nCarte Tunnel Teredo Tunneling Pseudo-Interface :\r\n\r\n   Suffixe DNS propre ▒ la connexion. . . : \r\n   Adresse IPv6. . . . . . . . . . .▒. . .: 2001:0:2851:782c:2cfb:38c4:3f57:9b0e\r\n   Adresse IPv6 de liaison locale. . . . .: fe80::2cfb:38c4:3f57:9b0e%3\r\n   Passerelle par d▒faut. . . .▒. . . . . : ::\r\n"
}

 

[Moayad]

Hi,

It's happening on all VMs guest or only 104 VM?

 

[kiteskate]

Hi,
no, on one other vm too, installed with the same iso file.
I'ill test another version of Win10 to check, thx for the idea

 

[kiteskate]

Hi,
no, on one other vm too, installed with the same iso file.
I'ill test another version of Win10 to check, thx for the idea

Looks like it's the windows version that is not working properly, no problem on a fresh 1909

thx for the help