[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-08-21 Thread Launchpad Bug Tracker
This bug was fixed in the package qemu - 1:2.10~rc3+dfsg-0ubuntu1 --- qemu (1:2.10~rc3+dfsg-0ubuntu1) artful; urgency=medium * Merge with Debian unstable (2.8) and Upstream 2.10-rci3; This fixes a set of bugs - [FFE] Qemu 2.10 in Artful (LP: #1699968) - CPU hot unplug fa

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-08-07 Thread ChristianEhrhardt
** Tags added: virt-fixed-by-2.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677552 Title: CPU hot unplug fails after migrating a CPU hotplugged guest from source To manage notifications abou

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-08-07 Thread ChristianEhrhardt
I see the changed being part of qemu 2.10 release candidates and hope to Merge that if not big blocker shows up. ** Tags added: p9-virt-stack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677552 Tit

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-08-04 Thread bugproxy
** Tags removed: targetmilestone-inin1704 ** Tags added: targetmilestone-inin1710 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677552 Title: CPU hot unplug fails after migrating a CPU hotplugged g

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-07-06 Thread ChristianEhrhardt
Daniel, thanks for bringing those upstream. I haven't had any problems since I'll tackle them along with the qemu merge for Artful. Aligning those with other tasks and PTO means it will take a bit longer to get to them. OTOH adding the patches to current qemu just to throw them away a few weeks

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-04-28 Thread ChristianEhrhardt
Thanks for the Update Daniel, are you now looking into libvirt as well or what are the next steps. I don't want to loose sync with everybody expecting the ball is in the field of the other - so I thought I better ask. -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-04-25 Thread bugproxy
** Tags removed: severity-critical ** Tags added: severity-high -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677552 Title: CPU hot unplug fails after migrating a CPU hotplugged guest from source

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-04-04 Thread ChristianEhrhardt
** Changed in: qemu (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => ChristianEhrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677552 Title: CPU hot unplug fails afte

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-03-31 Thread ChristianEhrhardt
Thank you a lot for clarifying my questions! Ok, for now I'll keep an eye open and you ping the bug once there is an update on the upstreaming of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/16

[Bug 1677552] Re: CPU hot unplug fails after migrating a CPU hotplugged guest from source

2017-03-30 Thread ChristianEhrhardt
I agree to your statement: "So the fix for this is to get Jianjun's DRC migration patchset upstream and then to 1704". I checked and found that this has some pretty long history [1]. I looked at the context but you are so much more aware of the details that I have some questions for you below.