Proxmox 3.0 behaviour on host shutdown

T

TomTomGo

Renowned Member
Mar 30, 2012
48
3
73
France
Hi,

Since we have migrate from 2.3 to 3.0 (on multiple hosts), when we run a "shutdown" on the host, all VM'S (KVM) are instantanely stopped instead of doing a clean shutdown (via ACPI / qm shutdown).
Is it the expected behaviour ? Is it possible to change this or to cutomize the shutdown process in order to shutdown VM properly ?

pveversion :

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

Best regards,

Thomas
 
check the task logs, you should see "Stopping VM 116 (timeout = 180 seconds)" - clean shutdown should happen as long as your VM´s allows anonymous acpi shutdown commands.

after 180 seconds, the VMs are stopped and the host powers off.
 
tom said:
check the task logs, you should see "Stopping VM 116 (timeout = 180 seconds)" - clean shutdown should happen as long as your VM´s allows anonymous acpi shutdown commands.

after 180 seconds, the VMs are stopped and the host powers off.
Click to expand...

Hello Tom,

Thanks for the quick reply. I agree with you and this is the problem, when i initiate a reboot from gui (or from ssh), got only these entries in tasks logs after reboot :

tasklogs.png

VM configuration : Start at boot = yes , order=any

Regards,

Thomas
 
works here. if I reboot via gui, I see two tasks (I have one VM 116 running):

  • Stop all VMs and Containers
  • VM 116 - Shutdown
 
tom said:
works here. if I reboot via gui, I see two tasks (I have one VM 116 running):

  • Stop all VMs and Containers
  • VM 116 - Shutdown
Click to expand...

Okay thank you for the test.
It should be an upgrade issue ?
I do the upgrade from 2.3 with the pve-upgrade-2.3-to-3.0 script dowloaded from the wiki, upgrade was succesfull.
If i do a "qm shutdown 102", the VM shutdown occurs normally ... It looks like the host shutdown sequence "skip" the step named "Stop all VMs and Containers".

Regards,

Thomas
 
Okay, i've done more tests :

pvesh --nooutput create /nodes/localhost/stopall : the vm shutdown correctly with an ACPI shutdown sequence
So i add a sleep 30 at the end of file /etc/init.d/pve-manager (just before the "exit 0") and reboot the host.
I've got few lines saying "ipcc_send_rec_failed : connection refused" and the VM is stopped after the end of the sleep.

Still investigate, if you have some ideas you're welcome ...

Regards,

Thomas
 
Found the problem : RTFM !!!
I forget the last step in the migration guide :
apt-get purge fuse-utils
insserv

Works right now !!!

Sorry for inconvenience and thanks for your help.

Regards,

Thomas
 
You must log in or register to reply here.
Top Bottom