Sometime you run into problem and your LXC container do not start. Proxmox VE graphical UI is very good, but it does not provide enough information about what is wrong.
To get the most detailed information, you should try to start the LXC container from command using verbose logging. Here is the command you should use:
(replace [ID] with your actual LXC container ID)
lxc-start -n [ID] -F -l DEBUG -o /tmp/lxc-[ID].log
Then, to view the log use this command:
cat /tmp/lxc-[ID].log
Wednesday, May 15, 2019
Upgrading Proxmox VE
To upgrade your Proxmox virtual environment to the next version do the following steps.
Step 1 - Get latest APT updates
apt-get update
Step 2 - Perform distribution upgrade
apt-get dist-upgrade
You may be asked if you would like to use existing or newer configuration file. I usually answer N (no) to keep using the current version which is usually safer.
Step 1 - Get latest APT updates
apt-get update
Step 2 - Perform distribution upgrade
apt-get dist-upgrade
You may be asked if you would like to use existing or newer configuration file. I usually answer N (no) to keep using the current version which is usually safer.
Can not start LXC container with error: unsupported Ubuntu version '18.04'
I restored an LXC container I have backed up from a newer Proxmox VE to an older node. To my surprise... it would not start. This is the error message I got when I debugged the LXC start-up process.
lxc pre-start with output: unsupported Ubuntu version '18.04'
When I press start button, it quickly fails and displays:
I thought it may be caused by file system (the LXC image) corruption. So I tried to mount and unmount it first using
pct mount 165
pct unmount 165
both worked perfectly so that was not the issue.
Then I made sure the file system is clean by running fsck against it, using this fsck command
pct fsck 165
That also ran perfectly clean!
After being puzzled, I researched and found people with similar issue, it turned out that Proxmox LXC start up script checks for version of Ubuntu and did not have the latest version 18.04 LTS Bionic Beaver. So I updated this file:
nano /usr/share/perl5/PVE/LXC/Setup/Ubuntu.pm
look for this section:
my $known_versions = {
'17.10' => 1, # artful
'17.04' => 1, # zesty
'16.10' => 1, # yakkety
'16.04' => 1, # xenial
'15.10' => 1, # wily
'15.04' => 1, # vivid
'14.04' => 1, # trusty LTS
'12.04' => 1, # precise LTS
};
and replace it with this:
my $known_versions = {
'22.04' => 1,
'20.04' => 1,
'18.04' => 1, # Bionic Beaver LTS
'17.10' => 1, # artful
'17.04' => 1, # zesty
'16.10' => 1, # yakkety
'16.04' => 1, # xenial
'15.10' => 1, # wily
'15.04' => 1, # vivid
'14.04' => 1, # trusty LTS
'12.04' => 1, # precise LTS
};
This SOLVED my issue and I was able to start the LXC container.
If you don't feel comfortable editing /usr/share/perl5/PVE/LXC/Setup/
You can also simply upgrade your Proxmox VE node to get the latest update from Proxmox.
lxc pre-start with output: unsupported Ubuntu version '18.04'
When I press start button, it quickly fails and displays:
I thought it may be caused by file system (the LXC image) corruption. So I tried to mount and unmount it first using
pct mount 165
pct unmount 165
both worked perfectly so that was not the issue.
Then I made sure the file system is clean by running fsck against it, using this fsck command
pct fsck 165
That also ran perfectly clean!
After being puzzled, I researched and found people with similar issue, it turned out that Proxmox LXC start up script checks for version of Ubuntu and did not have the latest version 18.04 LTS Bionic Beaver. So I updated this file:
nano /usr/share/perl5/PVE/LXC/Setup/Ubuntu.pm
look for this section:
my $known_versions = {
'17.10' => 1, # artful
'17.04' => 1, # zesty
'16.10' => 1, # yakkety
'16.04' => 1, # xenial
'15.10' => 1, # wily
'15.04' => 1, # vivid
'14.04' => 1, # trusty LTS
'12.04' => 1, # precise LTS
};
and replace it with this:
my $known_versions = {
'22.04' => 1,
'20.04' => 1,
'18.04' => 1, # Bionic Beaver LTS
'17.10' => 1, # artful
'17.04' => 1, # zesty
'16.10' => 1, # yakkety
'16.04' => 1, # xenial
'15.10' => 1, # wily
'15.04' => 1, # vivid
'14.04' => 1, # trusty LTS
'12.04' => 1, # precise LTS
};
This SOLVED my issue and I was able to start the LXC container.
If you don't feel comfortable editing /usr/share/perl5/PVE/LXC/Setup/
You can also simply upgrade your Proxmox VE node to get the latest update from Proxmox.
Proxmox LXC Backup issue: INFO: mode failure - some volumes do not support snapshots
I am getting this notice when performing LXC container backup on Proxmox 5.x
INFO: mode failure - some volumes do not support snapshots
At first I thought there was something wrong with the container, I checked for strange things that I may have done such as mounting external NFS share, etc... but I did not find anything strange.
Then I realize this disk partition or space that the container is on is not an LVM type of partition.
Because of this I can NOT do a 'SNAPSHOT' backup. Suspend somehow does not work either.
But backup did work after full shutdown. Or you can just start the backup right away with SHUTDOWN mode.
Hope this help someone with same issue.
INFO: mode failure - some volumes do not support snapshots
At first I thought there was something wrong with the container, I checked for strange things that I may have done such as mounting external NFS share, etc... but I did not find anything strange.
Then I realize this disk partition or space that the container is on is not an LVM type of partition.
Because of this I can NOT do a 'SNAPSHOT' backup. Suspend somehow does not work either.
But backup did work after full shutdown. Or you can just start the backup right away with SHUTDOWN mode.
Hope this help someone with same issue.
Sunday, May 12, 2019
What is new in Proxmox VE 5.4? is it worth upgrading?
New Wizard for Installing Ceph (even easier)
Ceph has been integrated into the Proxmox VE since 2014 as its primary distributed storage technology. The configuration of Ceph has been available in Proxmox VE GUI for a while, but some configuration are still required to be done from command line interface. Proxmox VE 5.4 eliminates all command line requirements and make Ceph fully configurable from Proxmox VE web based GUI. For those of you who are not familiar with Ceph, it is very robust and stable distributed storage architecture which allows you to add cheap and scable storage using cheap disk from multiple nodes within your Proxmox cluster.Better HA (High Availability) features
Proxmox VE 5.4 improved on HA policy data center-wide, changing the way how guests are treated upon a node shutdown or reboot. This brings greater flexibility and choice to the user.These new HA policy choices are:
- Freeze: always freeze services—independently of the shutdown type (reboot, poweroff).
- Fail-over: never freeze services—this means a service will get recovered to another node if possible and if the current node doesn’t come back up in the grace period of one minute.
- Default: this is the current behavior—freeze on reboot but do not freeze on poweroff.
Qemu/KVM guests can now Suspend to disk/hibernation
You can now hibernate Qemu guests independent of the guest OS and have them resumed properly on the next restart. Hibernating your virtual machine saves the RAM contents and the internal state to disk. This allows users to restore the running state of their qemu-guests between upgrades to and reboots of the PVE-node.Support for U2F (Universal 2nd Factor) Authentication (optional)
Proxmox VE 5.4 now supports the U2F (Universal 2nd Factor) protocol which can be used in the web-based user interface as an additional method of two-step verification for users. The U2F is an open authentication standard and simplifies the two-factor authentication. Since it is required in certain domains and environments this is an important improvement to security practices.Move options and features in QEMU Guest creation wizard
As often requested by the Proxmox community some options like for example:- Machine-type (q35, pc-i440fx)
- Firmware (Seabios, UEFI)
- SCSI controller can now be selected directly in the VM creation wizard
What is new in Proxmox 5.3 - CEPHFS is finally integrated in GUI
CephFS finally easy to use in Proxmox VE 5.3
Ceph has been integrated in Proxmox VE for a few years already. However it was difficult to use because it was only available as a block device (not as a mountable file system).Now Proxmox has finally integrated mountable Ceph file system directly to the Proxmox VE web gui. Proxmox release statements claims administrators can now create CephFS just within a few clicks.
Being able to create and mount (use) CephFS is a true game changer. I will test to make sure it is able to be used for backup, to be mounted inside lxc containers.
I have been using other file system such as NFS via OMV (media vault) for a while. I am not happy with its performance. I hope CephFS will be much faster.
Stay tuned for my next blog for my review of how CephFS for my real scenario review.
What is new in Proxmox VE (virtual environment) 5.2 - Should I upgrade?
Cloud-Init - automatic virtual machine provisioning
Cloud-Init will help you do initial setups on your virtual machines after its first boot. Cloud-Init is a multi-distribution automation software. It is similar to Puppet, Ansible, Chef, etc...SMB/CIFS Storage Plug-in
SMB/CIFS (aka Samba) is a network shared storage usually used by Windows platform. SMB/CIFS is typically faster than NFS. It is also simpler / easier to learn due to its simpler username / password.This is a huge feature and one that I have been waiting to arrive. As of currently I only use NFS for sharing network shared mounted storage inside LXC containers.
Let’s Encrypt Certificate Management via GUI
Let's encrypt has changed the SSL industry. Let's encrypt basically offers 100% free perpetual SSL. I am using Let's Encrypt for almost all my websites. Having Let's encrypt integration in Proxmox will be useful in cases where I can not install certbot or acme due to age of server issue, etc...Proxmox VE 5.2 also adds many new improvement features for better usability, scalability, and security
+ Creation of clusters via the web gui. Now you can create and join nodes to a Proxmox cluster extremely simple and effective.
+ LXC management improvement: Creating templates or moving disks from one storage to another now also work for LXC.
+ If the QEMU guest agent is installed, the IP address of a virtual machine is displayed on the GUI
+ Administrators can create and edit new roles via the GUI.
+ Setting I/O limits for restore operations is now possible (globally or more fine-grained per storage) to avoid I/O load getting too high while restoring a backup.
Subscribe to:
Posts (Atom)