Reset button does not reset VM.

[MarkLFT]

I have noticed that the Reset button on a VM/GUest does not work as expected. On a physical device, a reset does not care about the OS state, it simply resets the computer so it can boot again. On the VMs if the Ubuntu has crashed, or Windows is part way through an install, the reset button does not do anything.

Several times in the last few days whilst experimenting with hosts, guests have gotten into a state where I cannot complete an install or shutdown and have been forced to reset the host to allow me to restart the VM's.
This seems wrong to me, as reset should effectively power cycle a guest, irrespective of the VM/OS state.

 

[leesteken]

Indeed that does seem wrong, as it appears to work as you expect for me. What is the output of pveversion -v and can you share the configuration file of one of those VMs (from the /etc/pve/qemu-server/ directory)?

 

[MarkLFT]

proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-helper: 7.2-2
pve-kernel-5.15: 7.2-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-1
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

Windows Guest config

agent: 1
boot: order=virtio0;net0;ide0;ide2
cores: 2
machine: pc-i440fx-6.2
memory: 2048
meta: creation-qemu=6.2.0,ctime=1661756820
name: rmcore
net0: virtio=8A:4F:F7:CC:35:0E,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=1e201483-565e-4787-a2dd-ee6849d324bc
sockets: 1
virtio0: local-lvm:vm-100-disk-0,size=32G
vmgenid: 28471ad0-8ad3-4c2a-ad5c-3d2c0a31b141

 

[Dunuin]

Also make sure no "shutdown" task is still running. In such a case the VM would be locked and the "reset" task will only work after no other task for that running anymore.

 

[_gabriel]

me too, discovered shutdown tasks log prevent stop, few months after using proxmox

 

[MarkLFT]

Yes, there was a previous shutdown in process.

I still maintain, if I push reset, it should respond to it immediately. Not have to search for previous commands and stop them first.

I noticed there is another thread about this. I found it this morning. Seems others are of the same opinion that reset should just do it.

 

[gregwoodslancs]

This is crazy. Do I need to reboot the entire proxmox host server, just so that I can reset a single malfunctioning VM ??
Is there some sort of bug ticket for this?
Reset should always be the equivalent of reseting the power. If there are bad side effects to this, it is my responsibility to sort them out. It is a sometimes necessary last resort, but it HAS to work!!

 

[Dunuin]

Do I need to reboot the entire proxmox host server, just so that I can reset a single malfunctioning VM ??

No, you just stop the running shutdown task. Then the reset task will work as expected.

 

[Neobin]

For reference:
https://bugzilla.proxmox.com/show_bug.cgi?id=4474