Always unable to detect OS distribution after pct restore

Norbert_42

New Member
May 11, 2016
8
1
1
63
Hello,

I'm trying migrate from OpenVZ to Proxmox. I have 6 VM 32 or 64 bits. The migration of VM with
OSTEMPLATE="debian-7.0-x86" seems OK but all VM with OSTEMPLATE="debian-8.0-x86_64-minimal" or
"ubuntu-14.04-x86_64" send
Detected container architecture: amd64
###########################################################
Converting OpenVZ configuration to LXC.
Please check the configuration and reconfigure the network.
###########################################################
TASK ERROR: unable to detect OS distribution

Version:
pveversion -v
proxmox-ve: 4.2-49 (running kernel: 4.4.8-1-pve)
pve-manager: 4.2-4 (running version: 4.2-4/2660193c)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.8-1-pve: 4.4.8-49
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-74
pve-firmware: 1.1-8
libpve-common-perl: 4.0-60
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-16
pve-container: 1.0-63
pve-firewall: 2.0-26
pve-ha-manager: 1.0-31
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
 
CTID 101 cat /etc/debian -----> 8.4
CTID 105 cat /etc/issue -----> Ubuntu 14.04.4 LTS
CTID 106 cat /etc/debian -----> 8.4

I feel your answer (nothing > 8.0 or 14.04) but how can i do with this versions. I'm used to have the latest OS versions. :rolleyes:
 
On promox
proxmox:~# cat /etc/debian_version
8.4

On VM
CTID 101 cat /etc/debian_version -----> 8.4
CTID 105 cat /etc/issue -----> Ubuntu 14.04.4 LTS
CTID 106 cat /etc/debian_version -----> 8.4
 
Strange, that works for me. Looking at the source code, that error message is only triggered if /etc/debian_version file does not exist.
 
I found an issue. I re install a new version with appliance Proxmox.
My first installation was unpackaged on Debian 8

The software version appears earlier

proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
 
Wrong. All problems came from ploop disk.
I found in OpenVZ forum that "the need for converting ploop disks to simfs since proxmox does not support ploop yet (not considered as stable)."
You can convert ploop to simfs with a script here. Read all comments.
 
  • Like
Reactions: rcd

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!