Hi,
El 12/05/16 a las 12:38, Albert Dengg escribió:
hi,
On Thu, May 12, 2016 at 08:45:30AM +0200, Eneko Lacunza wrote:
Hi Albert,
I just updated yesterday afternoon our cluster to PVE 4.2 non-subscrition
and migration works OK. Did so using your procedure.
I found migration problems about a month ago, you can search in the mailing
list the good advice I got from the developers.
i think i know wich thread you mean, and they advised you to upgrade
to
qemu-server 4.0-59
pve-qemu-kvm 2.5-7
however, i'm already running
qemu-server: 4.0-72
pve-qemu-kvm: 2.5-14
Yes, notice I had to upgrade also on migration-source machines:
qemu-server 4.0-59 . What version do you have in the to-be-upgraded
machines?
as for storage:
we are using ceph storage for the VMs
We too.
just for the record:
i reran some test just now:
* offline migration works (i have a test vm that i could use for
that
* even though i got an error yesterday, it worked just now for a
freshly booted VM
i still would like to find a way that does not involve shutting down
all VMs to get migration working again...the next possible time for
that would be at some point end of next week most likly...
I'm think you're hitting a bug in the qemu version running your VMs...
(as I did).
Not really related to this, but you should remove 2.6.32 and 3.10 kernels,
they're not able to boot PVE 4/Debian jessie as far as I've tested.
yes i know, i just saw it...however i really don't think non-running
kernels are the problem here...
Sure.
Cheers
Eneko
--
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943493611
943324914
Astigarraga bidea 2, planta 6 dcha., ofi. 3-2; 20180 Oiartzun (Gipuzkoa)
www.binovo.es
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
