[SOLVED] VM won't auto-start Proxmox 5.0-2

F

Fruitvlieg

New Member
Apr 18, 2017
8
2
1
45
I installed a fresh installation of the newest Promox (beta) and installed a VM with Server 2008 R2.
I tried to configure the VM options to auto start: yes but the VM doesn't auto-start after a reboot of the proxmox server. Also setting the boot order and delay did not help.

How can i solve this issue?

I'm running:
proxmox-ve: 5.0-2 (running kernel: 4.10.1-2-pve)
pve-manager: 5.0-5 (running version: 5.0-5/c155b5bc)
pve-kernel-4.10.1-2-pve: 4.10.1-2

Results of task viewer:
Task viewer: Start all VMs and Containers
Output
Status
Stop
Can't call method "has_lock" on an undefined value at /usr/share/perl5/PVE/API2/Nodes.pm line 1300.
Use of uninitialized value in string eq at /usr/share/perl5/PVE/API2/Nodes.pm line 1382.
Use of uninitialized value in string eq at /usr/share/perl5/PVE/API2/Nodes.pm line 1386.
Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/PVE/API2/Nodes.pm line 1392.
unknown VM type ''
TASK OK
 
upgrade to latest 5.x beta packages, should be fixed already.
 
Here is the output:

proxmox-ve: 5.0-2 (running kernel: 4.10.1-2-pve)
pve-manager: 5.0-5 (running version: 5.0-5/c155b5bc)
pve-kernel-4.10.1-2-pve: 4.10.1-2
libpve-http-server-perl: 2.0-1
lvm2: 2.02.168-pve1
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-3
qemu-server: 5.0-1
pve-firmware: 2.0-1
libpve-common-perl: 5.0-3
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-1
libpve-storage-perl: 5.0-2
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.7.1-500
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-3
qemu-server: 5.0-1
pve-firmware: 2.0-1
libpve-common-perl: 5.0-3
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-1
libpve-storage-perl: 5.0-2
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.7.1-500
pve-container: 2.0-4
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.7-500
lxcfs: 2.0.6-pve500
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
 
Fruitvlieg said:
Here is the output:

proxmox-ve: 5.0-2 (running kernel: 4.10.1-2-pve)
pve-manager: 5.0-5 (running version: 5.0-5/c155b5bc)
pve-kernel-4.10.1-2-pve: 4.10.1-2
libpve-http-server-perl: 2.0-1
lvm2: 2.02.168-pve1
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-3
qemu-server: 5.0-1
pve-firmware: 2.0-1
libpve-common-perl: 5.0-3
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-1
libpve-storage-perl: 5.0-2
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.7.1-500
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-3
qemu-server: 5.0-1
pve-firmware: 2.0-1
libpve-common-perl: 5.0-3
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-1
libpve-storage-perl: 5.0-2
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.7.1-500
pve-container: 2.0-4
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.7-500
lxcfs: 2.0.6-pve500
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
Click to expand...

those are not the current packages, please check your repository configuration and "apt-get update; apt-get dist-upgrade" to the current beta packages.
 
Running apt-get dist-upgrade did had some updates, this are my sources:

File: /etc/apt/sources.list
deb http://ftp.nl.debian.org/debian stretch main contrib
# security updates
deb http://security.debian.org stretch/updates main contrib
# promox updates
deb http://download.proxmox.com/debian stretch pve-no-subscription

Current pveversion -v:
proxmox-ve: 5.0-2 (running kernel: 4.10.1-2-pve)
pve-manager: 5.0-5 (running version: 5.0-5/c155b5bc)
pve-kernel-4.10.1-2-pve: 4.10.1-2
libpve-http-server-perl: 2.0-1
lvm2: 2.02.168-pve1
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-3
qemu-server: 5.0-1
pve-firmware: 2.0-1
libpve-common-perl: 5.0-3
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-1
libpve-storage-perl: 5.0-2
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.7.1-500
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-3
qemu-server: 5.0-1
pve-firmware: 2.0-1
libpve-common-perl: 5.0-3
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-1
libpve-storage-perl: 5.0-2
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.7.1-500
pve-container: 2.0-4
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.7-500
lxcfs: 2.0.6-pve500
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

Is this correct now?
 
You must log in or register to reply here.
Top Bottom