Brutal stop after timeout

A

AdminCogne

New Member
May 9, 2017
8
0
1
46
Hi all,

I have set this options on a VM with Windows 2000:
upload_2017-10-13_18-5-8.png


When i press server power button, all VMs begin to shutdown but this machine still online after 10 minutes.
Proxmox reports Error: VM quit/powerdown failed - got timeout and the poweroff procedure fails.

Is there a script/command or config file to edit to force proxmox to cut off power to this VM if it still online after 600 seconds?

Thanks,
Steve.
 
Oh, windows2000, yes a long time ago... :) but should work. ACPI/energy Option are set correctly in the VM? If you logged in the VM (directly not rdp) the shutdown is working?
Please post also:
Code: 
qm config <vmid>
pveversion -v
 
There's no way to shut it down.
Everything is set correctly, I have already done everything Microsoft tells me to do and the only way is a brutal power off.
The "shutdown" command inside VM, without RDP, puts the machines to "Now is possible to power off the computer" (it is showed in Italian, maybe it's not the exact traduction).

Result of "qm config vmid" is:
upload_2017-10-14_20-57-10.png

Result of "pveversion -v" is:
upload_2017-10-14_20-57-45.png


I need an automatic, forced power off, after the shutdwon timeout.

Thanks in advance for help.
 
Ok, this looks nice. Is that the only one Win2000 or have you other win2000 that is working fine? But in the VM with shutdown it is possible?

Have you an ISO for me that i can test it for you?
 
fireon said:
Ok, this looks nice. Is that the only one Win2000 or have you other win2000 that is working fine? But in the VM with shutdown it is possible?

Have you an ISO for me that i can test it for you?
Click to expand...

Yes, I have another Win2000 VM that is working fine and it shutdown correctly.

I don't have ISO because these 2 VMs are old physical machine converted to virtual. Some years ago they were converted to hyper-v having Windows 2008 as host, after some years converted to VMware and putted inside ESXi 5.5. Now they are into Proxmox, under my manage.

Inside the Win2000 VM with the shutdown problem, is installed a license service for an old software no more supported and without installation supports.

When VM was inside VMware, it had the same shutdown problem that has now with Proxmox.
 
AdminCogne said:
I don't have ISO because these 2 VMs are old physical machine converted to virtual. Some years ago they were converted to hyper-v having Windows 2008 as host, after some years converted to VMware and putted inside ESXi 5.5. Now they are into Proxmox, under my manage.
Click to expand...
a wider away...
 
hmm... at windows CMD a shutdown is
Code: 
shutdown /s
an yes you can insert a script in GPO at shutdown and start. Maybe an script will be executet. On a working windowsinstallation this do. Test it.
 
A "shutdown /s" results in "It is now safe to turn off the computer".

Qemu-agent seems not compatible, it doesn't install.

Is it possible to start a command outside Windows/guest?
Something that kills the VM process?
 
You must log in or register to reply here.
Top Bottom