KVM Migration

[briankwest]

Is it me or is the latest build broken when migrating offline KVM guests? It all appears ok but never copies over the disk image.

Or are my expectations wrong?

pve-manager: 2.0-57 (pve-manager/2.0/ff6cd700)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-65
pve-kernel-2.6.32-10-pve: 2.6.32-64
pve-kernel-2.6.32-11-pve: 2.6.32-65
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-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-37
pve-firmware: 1.0-15
libpve-common-perl: 1.0-25
libpve-access-control: 1.0-17
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

/b

 

[briankwest]

Apr 09 19:34:33 starting migration of VM 111 to node 'proxmox00' (192.168.1.252)
Apr 09 19:34:33 copying disk images
Apr 09 19:34:34 migration finished successfuly (duration 00:00:02)
TASK OK

But it never actually copies the images.

/b

 

[dietmar]

But it never actually copies the images.

Please can you post the VM config:

# cat /etc/pve/qemu-server/111.conf

 

[briankwest]

bootdisk: virtio0
cores: 2
cpu: core2duo
ide2: local:iso/ubuntu-11.10-server-amd64.iso,media=cdrom
memory: 4096
name: ldap
net0: virtio=E6:73:20:04:246,bridge=vmbr0
ostype: l26
sockets: 1
virtio0: local:111/vm-111-disk-1.raw

/b

 

[dietmar]

and what is the output of:

# cat /etc/pve/storage.cfg

 

[briankwest]

dir: local
path /var/lib/vz
shared
content images,iso,vztmpl,rootdir
maxfiles 5


dir: backup
path /var/lib/vz/backup
shared
content backup
maxfiles 2


/b

 

[tom]

you cannot mark local storage "shared". remove the shared flag and it will work.

 

[briankwest]

Thats very interesting... I don't think mark it as shared either way It also shouldn't fail gracefully leaving the VM in an unusable state.

/b

 

[tom]

Thats very interesting... I don't think mark it as shared either way It also shouldn't fail gracefully leaving the VM in an unusable state.

/b

if you did not marked it as shared someone else did it. the installer does not do this.

 

[briankwest]

if you did not marked it as shared someone else did it. the installer does not do this.

I may have. Doesn't dismiss the bug. I'll file it in bugzilla.

/b

 

[dietmar]

I may have. Doesn't dismiss the bug. I'll file it in bugzilla.

Sorry, but what bug do you talk about?

 

[briankwest]

The bug where the local storage on both machines is marked shared and it blindly migrates the VM to the other machine without copying the disk image. Leaving the VM unusable unless you go manually move the disk image. It even says its moving the disk images and doesn't throw a single error.

/b

 

[dietmar]

The bug where the local storage on both machines is marked shared and it blindly migrates the VM to the other machine without copying the disk image.

This is expected behavior if you mark a storage as shared.

 

[briankwest]

Maybe this is just a simple documentation issue. I'll dig thru and see if this can be clarified on the wiki. I understand now what that flag is for it wasn't clear before.

/b

 

[briankwest]

OK one way to make this more usable is to just fail the migration if the disk image isn't visible from the target node when using storage marked shared?

/b

 

[dietmar]

OK one way to make this more usable is to just fail the migration if the disk image isn't visible from the target node when using storage marked shared?

YEs. Please can you file a bug at bugzilla.proxmox.com?

 

[briankwest]

Done. As I get more into the code I'll be able to give more back in patches... Right now I can test test test.

Thanks you guys.

/b