G
Géraud Tillit
Guest
Hello,
I've setup a non HA cluster of two servers, with two DRBD device in primary/primary mode
From an OS point of view, the DRBD devices are fine :
When I try an online migration from the web interface, the task finish with an "OK" status :
But then suddenly the VM has a very strange behaviour like :
I issue a stop on the VM via the web interface and when I try to restart it, grub doesn't find the boot disk... I have to migrate back to the first node, restart the VM (and fsck the disk).
Here is the pveversion output :
It was working without any problem on proxmox 1.9
I've setup a non HA cluster of two servers, with two DRBD device in primary/primary mode
From an OS point of view, the DRBD devices are fine :
Code:
root@proxmox2-02:/var/lib/vz/dump# cat /proc/drbd
version: 8.3.10 (api:88/proto:86-96)
GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b build by phil@fat-tyre, 2011-01-28 12:17:35
1: cs:Connected ro:Primary/Primary ds:UpToDate/UpToDate C r-----
ns:520496 nr:172484 dw:172788 dr:549816 al:20 bm:180 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
2: cs:Connected ro:Primary/Primary ds:UpToDate/UpToDate C r-----
ns:11123304 nr:522864 dw:11125976 dr:1097638 al:3053 bm:165 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
When I try an online migration from the web interface, the task finish with an "OK" status :
Code:
Apr 14 20:52:54 starting migration of VM 102 to node 'proxmox2-02' (88.190.39.127)
Apr 14 20:52:54 copying disk images
Apr 14 20:52:55 starting VM 102 on remote node 'proxmox2-02'
Apr 14 20:52:56 starting migration tunnel
Apr 14 20:52:56 starting online/live migration on port 60000
Apr 14 20:53:02 migration status: completed
Apr 14 20:53:02 migration speed: 170.67 MB/s
Apr 14 20:53:05 migration finished successfuly (duration 00:00:11)
TASK OK
But then suddenly the VM has a very strange behaviour like :
Code:
bash: /usr/bin/vi : cannot execute binary file
I issue a stop on the VM via the web interface and when I try to restart it, grub doesn't find the boot disk... I have to migrate back to the first node, restart the VM (and fsck the disk).
Here is the pveversion output :
Code:
root@proxmox2-01:/var/lib/vz# pveversion -v
pve-manager: 2.0-59 (pve-manager/2.0/18400f07)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-38
pve-firmware: 1.0-15
libpve-common-perl: 1.0-26
libpve-access-control: 1.0-18
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1
It was working without any problem on proxmox 1.9