Hi,
In another thread I’ve asked for some help about why Proxmox does not fully shutdown and test stuck for minutes with a black screen and blinking cursor. I’ve noticed this strange behavior:
I expected Proxmox VE shutdown procedure to execute shutdown on every VM and CT but maybe instead it executes a less clean stop command and this could be the reason why it takes ages.. stopping CT101 is very slow. Is there a way to understand where it gets stuck? In which script can I look at what action PVE executes on shutdown?
Follows the config of the CT101
In another thread I’ve asked for some help about why Proxmox does not fully shutdown and test stuck for minutes with a black screen and blinking cursor. I’ve noticed this strange behavior:
Code:
root@pve:~# time pct shutdown 101
real 0m2.862s
user 0m0.461s
sys 0m0.034s
root@pve:~# pct start 101
root@pve:~# pct status 101
status: running
root@pve:~# time pct stop 101
real 6m6.311s
user 0m0.500s
sys 0m0.075sI expected Proxmox VE shutdown procedure to execute shutdown on every VM and CT but maybe instead it executes a less clean stop command and this could be the reason why it takes ages.. stopping CT101 is very slow. Is there a way to understand where it gets stuck? In which script can I look at what action PVE executes on shutdown?
Follows the config of the CT101
Code:
root@pve:~# cat /etc/pve/lxc/101.conf
#**Proxmox Backup Server**
arch: amd64
cores: 6
features: nesting=1
hostname: ProxmoxBackupServer
memory: 4096
mp1: /mnt/pve/sata_disk/pbs_backups,mp=/pbs_backups
net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.0.0.254,hwaddr=CA:CE:16:FC:86:01,ip=10.0.0.5/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-101-disk-0,size=32G
searchdomain: mynetwork
startup: order=1
swap: 512
