vm not migrating to another local node

kasulstyls

New Member
Jul 13, 2010
11
0
1
version 2.3 fully updated. I choose a vm to migrate to another node, it will show that it completed in .04secs.... the migrated vm will not start as the vm.qcow is not being transfered but the configs are. I can not migrate the configs back due to it not having the attached qcow file. to migrate the configs back i delete the virtualhdd and then migrate, it will then see the unused hdd and i can reattach it.


Could I have something wrong on my local prox storage, as this is not on an attached NAS or SAN.


My 3 node configuration in my other datacenter does not experience this issue as the vm's configuration files and virtual hdd's do migrate together.



root@proxmox:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-6-pve: 2.6.32-53
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1

root@Dev-Prox3:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-6-pve: 2.6.32-53
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
 
Thanks for the quick reply udo.


---vm----
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 16384
name: avicast-web-prod
net0: virtio=6E:6E:B6:4D:2D:A2,bridge=vmbr0
ostype: l26
sockets: 2
virtio0: local:147/vm-147-disk-1.qcow2,size=48G
bootdisk: virtio0
cores: 4
ide2: local:iso/CentOS-6.2-x86_64-netinstall.iso,media=cdrom,size=227M
memory: 16384
name: avicast-web-prod
net0: virtio=6E:6E:B6:4D:2D:A2,bridge=vmbr0
ostype: l26
sockets: 2
virtio0: local:147/vm-147-disk-1.qcow2,size=48G

----storage---
dir: local
path /var/lib/vz
content images,iso,vztmpl,rootdir
maxfiles 0

dir: mylocal1
path /var/lib/vz/ISO
content iso
maxfiles 1
nodes dev-prox2

dir: Backups
path /var/lib/vz
content backup
maxfiles 2
 
closing ---

I rebooted all nodes and took off sharing. vm hdd's are syncing now. Thanks udo....
 

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!