startup

I'm trying to figure out how to have a cluster wide startup order. Initially I thought, the "Start and Shutdown Order" mentioned in "11.3.6. Automatic Start and Shutdown of Containers" of the PVE Admin guide was the way to go, but it turned out that this "Startup Order" is only taken into...

Hi, :) my plan is to wake up my Server remotly with a different device. Immediately WOL came to my mind. The BIOS is set up correctly and the WOL Feature is enabled. Also i checked the interface with ethtool <interface_name> and the wake on is set on g as you can see below...

Hallo zusammen, TL;DR Uns macht momentan das aktivierte Journaling-Feature bei LX-Containern zu schaffen. Einerseits ist dies für den rbd-mirror Sync in einen Pool vom Master zu Slave cluster obligatorisch, andererseits hindert es Container im Master an einem (Neu)start...

I've got a small Proxmox 5.1 server running 8 LXC containers (Debian). Randomly, when the server reboots (usually after a power outage), 1 of the 8 containers (always the same) doesn't start. I can start it manually without any problem. Only difference between this container and the 7 others ...

Hello, Pardon me, as I am sure this is common knowledge for many PVE users. For me, it took many frustrating hours to find the fix, so I will document it here as I have not seen this particular problem/solution laid out explicitly elsewhere. This video from the PVE team documents the fix but...

I have a new LXC (104) which I created yesterday in a 3 node cluster and it was running perfectly for about 18 hours. This morning I migrated the running container to another node and it stopped working, but proxmox still says it's running. I have tried restarting it, restarted the node...

When upgrading to this version the proxmox web environment was deprecated, affected the automatic start options; giving me an error "unable to parse value of 'startup' - Can not call method" retturn "on unblessed reference at /usr/share/perl5/PVE/JSONSchema.pm line 490" As it says in this line...

After getting the node up and running again (https://forum.proxmox.com/threads/it-seemed-failed-disks-prevent-proxmox-from-booting-but-it-was-actually-noapic-that-was-needed.43720/) I now have a problem that has been reported a few time elsewhere, but not in the systemd based version of Proxmox...

So i tried to make my first LXC container, got the ubuntu 16.04 image from Proxmox. When i try to start it it give me this: Job for pve-container@101.service failed because the control process exited with error code. See "systemctl status pve-container@101.service" and "journalctl -xe" for...

Hello, I've a got a Linux VM running as follows: balloon: 0 boot: cdn bootdisk: ide1 cores: 2 ide1: local:106/vm-106-disk-1.qcow2 ide2: local:iso/Hiren's.BootCD.15.2.iso,media=cdrom,size=609268K memory: 128 name: asystem net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0 numa: 0 ostype: l26 scsi0...

Problem When starting a VM the host occasionally crashes. /var/log/syslog and /var/log/daemon do not seem to show suspicious activities. We have tried reinstalling the host once—which yielded no improvement. The next thing we will try is checking for hardware problems. Has anybody else...

Hi All, I feel like I'm missing something blatantly obvious, but I can't seem to find it. I would like to automate the process of creating a Centos LXC, boostrapping it, then running the provisioning. The hang up is the Centos 7 LXC doesn't have openssh-server installed by default. Which I...

Hi. Is there a solution to use variables in container configuration. I need to start some premount scripts and some post stop scripts. As far as I've understand, up to now the variables in container configs are not implemented. My task is simple: 1- to create some directories and files before...

Hi All, Been enjoying using Proxmox for the last couple of months with no real complaints, really appreciate the work that has gone into overhauling the web interface, slick. Over the past couple of days I have had quite a bit of interaction with my server and have noticed the below error...