[Bug 1398718] Re: Live migration locks up Linux 3.2-based guests
Apologies for the delay. I can't even seem to reproduce the original issue on the affected hardware before upgrading, so I can't confirm the fix in vivid or wily. I'd be fine with closing this "can (no longer) reproduce"—maybe my recollection is playing funny tricks on me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1398718 Title: Live migration locks up Linux 3.2-based guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1398718/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1061665] Re: Filter scheduler not respecting the force_hosts hint
I ran into the same problem. It seems that HostState.passes_filters gets called with different data in filter_properties than it expects. The attached patch makes it work, but I doubt it's a completely correct solution, since I don't handle more than one host in the force_hosts list. ** Patch added: "nova_1061665.patch" https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1061665/+attachment/3412340/+files/nova_1061665.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1061665/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1061665] Re: Filter scheduler not respecting the force_hosts hint
Then perhaps this is a documentation bug instead. "--hint force_hosts" is the currently-documented method in the Compute Administration Manual: http://docs.openstack.org/trunk/openstack-compute/admin/content/specify- host-to-boot-instances-on.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1061665/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
This is also blocking a precise -> trusty migration for me. Would it be possible / feasible to provide a "pc-1.0-precise" machine type in qemu for trusty and an updated libvirt for precise that allows you to change the machine attribute on the element for migration, so I could specify a migration-compatible domain configuration? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
That's awesome. I just got a chance to test it out, and with a couple hiccups (below), I seem to have successfully migrated a guest from a precise host to a new trusty one. It looks like qemu failed to build in Serge's PPA due to the spice that also lives in that PPA. I built the qemu from the source in that PPA, and it built without modification. I also got 'pci_add_option_rom: failed to find romfile "pxe- virtio.rom.12.04"' the first time I did the migration with libvirt; a symlink seems to have papered over that problem. libvirt is passing "virtio-net-pci.romfile=pxe-virtio.rom.12.04", but nothing provides that file. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1398718] [NEW] Live migration locks up Linux 3.2-based guests
Public bug reported: In the thread at http://thread.gmane.org/gmane.comp.emulators.kvm.devel/127042/focus=129294, three commits were identified to fix live migration for qemu 2.0 (at least), which I am using on trusty. I would like to get these pulled-in by the package maintainer. I have cherry-picked those three commits (with some considerable fix-up for the first , which may or may not be correct; the others apply cleanly) and built packages locally. Installing that on the migration- receiver seems to fix my guest lockups after live-migrating. I can attach the patches I'm using if someone is able to review my fix-ups to the first one. My original problem description was: Somewhere between kernel 3.2 and 3.11 on my VM hosts (yes, I know that narrows it down a /whole lot/ ...), live migration started killing my Ubuntu precise (kernel 3.2.x) guests, causing all of their vcpus to go into a busy loop. Once (and only once) I've observed the guest eventually becoming responsive again, with a clock nearly 600 years in the future and a negative uptime. I haven't been able to dig up any previous threads about this problem, so my gut instinct is that I've configured something wonky. Any pointers toward /what/ I may have done wrong are appreciated. It only seems to happen if I've given the guests Nehalem-class CPU features. My longest-running VMs, from before I started passing-through the CPU capabilities into the guest, seem to migrate without issue. It also seems to happen reliably when the guest has been running for a while; it's easily reproducible with guests that have been up ~1 day, and I've reproduced it in VMs with an uptime of ~20 hours. I haven't yet figured out a lower-bound, which makes the testing cycle a little longer for me. The guests that I reliably reproduce this on are Ubuntu 12.04 guests running the current 3.2 kernel that Canonical distributes. Recent Fedora kernels (3.14+, IIRC) don't seem to busy-spin this way, though I haven't tested this case exhaustively, and I haven't written down very good notes for the tests I have done with Fedora. The hosts are dual-socket Nehalem Xeons (L5520), currently running Ubuntu 14.04 and the associated 3.13 kernel. I had previously reproduced this with 12.04 running a raring-backport 3.11 kernel as well, but I (seemingly erroneously) assumed it may have been a qemu userspace discrepancy. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1398718 Title: Live migration locks up Linux 3.2-based guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1398718/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
