Hi,
I've encounter few instances where guests continue to run on a different blade after they have been migrated so, when starting the guest from its new location we have all kings of strange issues, including sporadic disconnection due to conflicting IP addresses
The only solution I found so far was to reboot the server with the ghost
Not sure what kind of info I can provide to help troubleshooting this issues but here it is something
Ghost machine: 333
migrated from blh02-11 to blh02-08 - currently stopped
The MAC table on the switch still bind on blh02-11 - the guest is running
PTCOM-DEV-OSS 1e:f0:2a:b4:c4:92 Learn 0 ae11.0
qm config 333 boot: cdn
bootdisk: virtio1
cores: 1
ide2: none,media=cdrom,size=354604K
memory: 4096
name: nms.oss.dev
net0: virtio=1E:F0:2A:B4:C4:92,bridge=vmbr4077
ostype: l26
sockets: 1
virtio0: cluster-vm:vm-333-disk-1,size=5124M
virtio1: cluster-vm:vm-333-disk-3,size=5G
clustat
Cluster Status for bl02-cluster01 @ Thu Nov 22 18:55:19 2012
Member Status: Quorate
Member Name ID Status
------ ---- ---- ------
blh02-14 1 Online, rgmanager
blh02-13 2 Online, rgmanager
blh02-10 3 Online, rgmanager
blh02-11 4 Online, rgmanager
blh02-12 5 Online, rgmanager
blh02-08 6 Online, Local, rgmanager
blh02-07 7 Online, rgmanager
Service Name Owner (Last) State
------- ---- ----- ------ -----
pvevm:333 (blh02-08) disabled
pveversion -v
pve-manager: 2.2-31 (pve-manager/2.2/e94e95e9)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-82
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
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-33
qemu-server: 2.0-69
pve-firmware: 1.0-21
libpve-common-perl: 1.0-39
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1
I've encounter few instances where guests continue to run on a different blade after they have been migrated so, when starting the guest from its new location we have all kings of strange issues, including sporadic disconnection due to conflicting IP addresses
The only solution I found so far was to reboot the server with the ghost
Not sure what kind of info I can provide to help troubleshooting this issues but here it is something
Ghost machine: 333
migrated from blh02-11 to blh02-08 - currently stopped
The MAC table on the switch still bind on blh02-11 - the guest is running
PTCOM-DEV-OSS 1e:f0:2a:b4:c4:92 Learn 0 ae11.0
qm config 333 boot: cdn
bootdisk: virtio1
cores: 1
ide2: none,media=cdrom,size=354604K
memory: 4096
name: nms.oss.dev
net0: virtio=1E:F0:2A:B4:C4:92,bridge=vmbr4077
ostype: l26
sockets: 1
virtio0: cluster-vm:vm-333-disk-1,size=5124M
virtio1: cluster-vm:vm-333-disk-3,size=5G
clustat
Cluster Status for bl02-cluster01 @ Thu Nov 22 18:55:19 2012
Member Status: Quorate
Member Name ID Status
------ ---- ---- ------
blh02-14 1 Online, rgmanager
blh02-13 2 Online, rgmanager
blh02-10 3 Online, rgmanager
blh02-11 4 Online, rgmanager
blh02-12 5 Online, rgmanager
blh02-08 6 Online, Local, rgmanager
blh02-07 7 Online, rgmanager
Service Name Owner (Last) State
------- ---- ----- ------ -----
pvevm:333 (blh02-08) disabled
pveversion -v
pve-manager: 2.2-31 (pve-manager/2.2/e94e95e9)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-82
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
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-33
qemu-server: 2.0-69
pve-firmware: 1.0-21
libpve-common-perl: 1.0-39
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1