[pve-devel] Fatal bug in migration

Fabian Gr├╝nbichler f.gruenbichler at proxmox.com
Wed Jan 4 10:15:22 CET 2017


On Tue, Jan 03, 2017 at 10:12:27PM +0100, Michael Rasmussen wrote:
> On Tue, 3 Jan 2017 21:43:15 +0100 (CET)
> Dietmar Maurer <dietmar at proxmox.com> wrote:
> 
> > 
> > Do you talk about a specific patch?
> > 
> No, only official releases.
> Previous was before:
> The following updates are available:
> 
> libpve-common-perl: 4.0-84 ==> 4.0-85
> libpve-storage-perl: 4.0-70 ==> 4.0-71
> lxc-pve: 2.0.6-2 ==> 2.0.6-5
> lxcfs: 2.0.5-pve1 ==> 2.0.5-pve2
> proxmox-ve: 4.4-76 ==> 4.4-77
> pve-container: 1.0-89 ==> 1.0-90
> pve-kernel-4.4.35-1-pve: 4.4.35-76 ==> 4.4.35-77
> pve-manager: 4.4-2 ==> 4.4-5
> pve-qemu-kvm: 2.7.0-9 ==> 2.7.0-10
> 
> And current is after.
> 
> I have been doing some more in-depth tests which have revealed this
> pattern:
> 
> previous -> previous ----> fail
> previous -> current  ----> fail
> current  -> previous ----> fail
> current  -> current  ----> success
> 
> BTW. I have tested snapshot/rollback on current and it is working
> again but in the log I see this out:
> 
> kvm_apic_post_load: Yeh
> kvm_apic_post_load: Yeh
> TASK OK
> 
> Is that intended or some leftover debug info? ;-)

that is left-over debug info in an upstream qemu patch, we simply didn't
cherry-pick the follow-up patch removing this debug output (yet).



More information about the pve-devel mailing list