Error on "Clone from LVM to img (qcow2-raw)"

dea

Renowned Member
Feb 6, 2009
243
87
68
Hi all !

On very last Proxmox 3.4 I've a problem to full clone a VM:

On clone from qcow2 to img (raw, qcow2) all ok.
On clone from LVM to img:

***************
Use of uninitialized value in string eq at /usr/share/perl5/PVE/QemuServer.pm line 6014.
Use of uninitialized value $ready in concatenation (.) or string at /usr/share/perl5/PVE/QemuServer.pm line 6010.
***************

Any idea ?

Luca
 
Hi,
I tried it in a current version of PVE and it worked!
What pveversion you are using?
# pveversion -v
 
proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-29-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-39-pve: 2.6.32-156
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-31-pve: 2.6.32-132
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
can you describe exactly how you clone!
 
proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-29-pve)
...


you run a quite old kernel - you installed latest pve-kernel-2.6.32-39-pve: 2.6.32-156 but it seems you did not boot into this one.
 
Yes.

On server 1: storage on local LVM formatted in EXT3, target storage VM: QCOW2. Source datastore on NFS, VM storage type source QCOW2: ALL OK !!!

On server 2: storage on local LVM, VG storage as datastore source, target NFS datastore, format out QCOW2 (format in LVM): these errors....

How I clone .. by gui or by command line: full clone.
 
Hi,
this work at 2 difference system perfectly.
try it locally, may be you have an nfs permission problem.
 
Hmmm , no.
The only difference from server 1 and 2 is the kernel. Server 1 use the last kernel, server 2 is run on an old kernel (but the last is installed).
Now is not possible to reboot server 2 and I cannot test it.

Is possibile that the problem is the old kernel that run on server 2 ?

Thanks
 
Normally not but I would not bet :)
I would try and you should anyway run the last one.
 
Infact,

usually I upgrade servers and reboot when is possible. But in this case, the only difference from server 1 and server 2 (the NFS storage is the same) is the kernel version that run on server 2 (and the type of datastore).

I try to reboot server 2 when is possible.

Thanks !!!!
 

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!