The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: qemu (Ubuntu Groovy)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since this has been dormant since my soft-reject I think we need to mark
it accordingly to be fair on expectations for this case.
** Changed in: qemu (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: qemu (Ubuntu Focal)
Status: In Progress => Incomplete
** Changed
** Changed in: qemu (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch removed: "lp1894772_ussuri.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409659/+files/lp1894772_ussuri.debdiff
** Patch removed: "lp1894772_focal.debdiff"
###
Scenario 4
###
Focal <-> Focal
->
Focal( patched ) OK
###
and
-> Focal -> Focal(patched) OK
###
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks for uncovering just another bug on the case (it is four now, so
we can already see that it is complex and comes back in different
aspects).
>From looking at the debdiffs a few formalities:
- origin, please point to some place you go this from "based on a patch by Len
" is nothing you can
** Patch added: "lp1894772_ussuri.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409659/+files/lp1894772_ussuri.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1894772_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409640/+files/lp1894772_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1894772_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409639/+files/lp1894772_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
workaround
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389/comments/15
didnt work.
I worried that if we patch this to over Q,
I assume that live migration current running instances from current Q to
patched Q
so I've tested some scenario
###
Scenario 1
** Changed in: qemu (Ubuntu Groovy)
Status: Fix Released => In Progress
** Changed in: qemu (Ubuntu Groovy)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI I think this bug is the same as 1647389
In that LP,
Dave also mentioned commit 4eae2a657d1ff5ada56eb9b4966eae0eff333b0b is needed
but it is too large and changes a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tested above patch on queens qemu. and it works fine.
I don't have to fix Mitaka anymore.
if this patch is viable, we need to put this to every release since
Queens. if not, migration from patched one to unpatched one will not
work as I saw between Mitaka and Queens.
--
You received this
** Patch added: "lp1894772_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409318/+files/lp1894772_bionic.debdiff
** Changed in: qemu (Ubuntu Bionic)
Status: New => In Progress
** Changed in: qemu (Ubuntu Bionic)
Assignee: (unassigned) =>
** Patch removed: "lp1894772_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/qemu/+bug/1894772/+attachment/5408515/+files/lp1894772_xenial.debdiff
** Patch removed: "lp1894772_mitaka.debdiff"
I think below commit is included inside 2.5 qemu in Xenial but not in
2.11
and I tested it with upstream commit build with migration. but I haven't
tested it yet
I'm going to test them with ubuntu releases as well.
If it is correct, we need patch > queens instead of mitaka
Description: make
Hey Christian
Unfortunately, I found an issue between below steps
X(not patched) -> X(patched) -> Q- is working fine
X(not patched) -> X(not patched) -> Q(error)
-> X(patched) -> Q - has the same error as
original
The customer is in the
Great, thanks!
That makes sense as the guest driver is part of the equation here.
So if you are willing to also verify this then (with the guests that
trigger the issue on X->X->B) I think there is nothing against this
anymore.
Do you want me to re-eval in depth and sponsor?
On Wed, Sep 9, 2020
and the customer said that
windows 2012r2, 2016 has issue but 2019 ( from their image ) is fine.
but we don't know what setting is there actually inside those images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
usually X->X->B is reproducer here. X->B is working fine basically.
Windows guest should have virtio balloon driver.
and I think below setting is needed ( as the customer's xml has it )
virsh dommemstat --domain win2k12r2 --period 10 --config
--
You received this bug notification because you
Thanks for the testing already.
Glad we could rule out the other issue you found.
In comment #7 you said "UCA X -> X -> B" triggers it, but why don't I see it
with "X -> B" usually?
Does it trigger just for "X -> B" for you as well?
Or is there any config needed in the guest to trigger (balloon
hey paelzer,
ah sorry
libvirt on Bionic was 4.0.0
I installed them libvirt-bin but I missed it is changed to libvirt-
daemon-system
I re-installed libvirt-daemon-system and it is 6.0.0 now,
then M -> M -> Q -> U migration is working fine.
--
You received this bug notification because you
On Wed, Sep 9, 2020 at 3:20 AM Seyeong Kim <1894...@bugs.launchpad.net> wrote:
...
> but Q -> U has issue below.
>
> error: internal error: qemu unexpectedly closed the monitor:
> qemu-system-x86_64: -realtime mlock=off: warning: '-realtime mlock=...' is
> deprecated, please use '-overcommit
With M-M-Q-U, and I faced issue described above, instance in Q crashed without
special log in qemu
only found msg is below from syslog
Sep 9 04:50:53 colt libvirtd[1311]: 2020-09-09 04:50:53.224+: 1311: error
: qemuMonitorIO:719 : internal error: End of file from qemu monitor
I tried to
Test M M Q U
M M Q is ok
but Q -> U has issue below.
error: internal error: qemu unexpectedly closed the monitor:
qemu-system-x86_64: -realtime mlock=off: warning: '-realtime mlock=...' is
deprecated, please use '-overcommit mem-lock=...' instead
2020-09-09T00:56:27.768574Z
Quick test with non UCA X -> X -> B, I can reproduce this the same way
as description and patch fixed issue.
I'm going to test further
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894772
Title:
ah I missed one thing is that
I was able to reproduce this issue with xenial (non UCA, 2.5 ) to
queens-staging. I'll test above case
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894772
Title:
Hi.
I tested yakkety(2.6.1) -> yakkty -> queens(2.11) and it worked.
so I did bisect then found those commits.
But I didn't test xenial->bionic,
but I'll update case after testing them as well.
Xenial -> Bionic
Mitaka -> Queens -> Ussuri
--
You received this bug notification because you are
Hi, the same doesn't seem to trigger for Xenial->Bionic which should be what
matches Mitaka-Queens right?
Did you find a way to reproduce it on Xenial->Bionic as well to justify the
change to (non UCA) Xenial users?
The Error you reported sounded familiar, for just the error you report there
The further reasons this a bit sounded known to me are:
https://bugs.launchpad.net/qemu/+bug/1838569
https://bugs.launchpad.net/cloud-archive/+bug/1848497
https://bugs.launchpad.net/cloud-archive/+bug/1882416
They ended up fixing a similar baloon migration issue around "Bad config data"
but the
** Patch added: "lp1894772_mitaka.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5408516/+files/lp1894772_mitaka.debdiff
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification
** Patch added: "lp1894772_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5408515/+files/lp1894772_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
livemigration of windows 2012 r2 instance with virtio balloon driver
from qemu 2.5(mitaka) to qemu 2.11(queens) is not working properly.
Especially instance keep moving e.g 2.5 -> 2.5 -> 2.11
Then It shows below msg from the 2nd mitaka node.
** Description changed:
[Impact]
- livemigration of windows 2012 r2 instance with virtio balloon driver
+ livemigration of windows 2012 r2 instance with virtio balloon driver
from qemu 2.5(mitaka) to qemu 2.11(queens) is not working properly.
Especially instance keep moving e.g
34 matches
Mail list logo
