@james-page, Any ETA on this package arriving in mitaka-updates ? It is
already in mitaka-proposed. Some other fixes are waiting on this SRU to
be completed for UCA. I'm afraid that some other SRU preempts, again,
the qemu fix for LP: #1626972. Thank you!
--
You received this bug notification
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique (depend on the
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique
This bug was fixed in the package qemu - 1:2.3+dfsg-5ubuntu9.4~cloud4
---
qemu (1:2.3+dfsg-5ubuntu9.4~cloud4) trusty-liberty; urgency=medium
.
* Fix ambiguous machine types (LP: #1641532)
- make utopic a true 2.1 type (was floating with qemu version)
- drop duplicate
This bug was fixed in the package qemu - 1:2.3+dfsg-5ubuntu9.4~cloud4
---
qemu (1:2.3+dfsg-5ubuntu9.4~cloud4) trusty-liberty; urgency=medium
.
* Fix ambiguous machine types (LP: #1641532)
- make utopic a true 2.1 type (was floating with qemu version)
- drop duplicate
Verified that with the fix "on both ends" we can not properly migrate from
Liberty onwards.
The Vivid default type won't migrate post Xenial but that is expected as we
only kept Trusty.
I also spawned a Trusty type on UCA-L and it migrated through up to Zesty as it
should.
** Tags removed:
Uploaded to liberty-staging ppa for the cloud archive. That'll need to
be promoted to liberty-proposed once it builds successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641532
Title:
Uploaded to liberty-staging ppa for the cloud archive. That'll need to
be promoted to liberty-proposed once it builds successfully.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.9
---
qemu (1:2.5+dfsg-5ubuntu10.9) xenial; urgency=medium
* fix ambiguous machine trusty and utopic machine types (LP: #1641532)
- d/p/ubuntu/define-ubuntu-machine-types.patch update type definitions
-
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu5.3
---
qemu (1:2.6.1+dfsg-0ubuntu5.3) yakkety; urgency=medium
* fix ambiguous machine trusty and utopic machine types (LP: #1641532)
- d/p/ubuntu/define-ubuntu-machine-types.patch update type definitions
-
Hi,
I contacted smoser who was hacking on open-iscsi recently due to related
reasons.
I'll quote his mail for the record, but the TL;DR is - we should be fine
ignoring the fail results of open-iscsi in yakkety.
Reasons:
- Test known to be unreliable
- works when reproduced in local ADT
- Xenial
Locally in adt the test works just fine - I contacted a few people I thought I
heard discussing about something very similar.
I think we are safe considering the update good, but I'll wait the weekend for
replies on my inquiry on known-issues of that testcase.
--
You received this bug
Full chain is working fine as expected.
But I'm still holding back to mark v-d too early as I hit an autopkgtest of
open-iscsi on yakkety (only there).
I'm 98% sure it is unrelated, but I want to make sure first.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
FYI - testing of the full chain T/X/Y/Z in proposed for verification is
in progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique
Hello Mehdi, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: cloud-archive
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique
** Changed in: cloud-archive
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique (depend on the
I uploaded the fixes to the unapproved queue, waiting for an SRU pass to
come by now.
The plan is to run the full multi-arch test suite once more against proposed
for verification then.
@corey-bryant: you might then run (part of) your matrix as well once in
proposed right?
But now waiting for
** Description changed:
+ [Impact]
+
+ * Guests that were created with the Trusty (or Utopic) machine type are
+not unique. Due to that on migrations between the qemu versions of
+multiple Ubuntu releases migrations fail
+
+ * Many migrations work just by luck, one that fails is the
These are the log of the full path tests using ppas for UCA and
Xenial/Yakkety as well as the now migrated qemu of Zesty.
** Attachment added: "logs of the full path testing"
Since Zesty now is ready we have opened a window where migrations of a
Trusty Type guest on Xenial can not be migrated to Zesty (expected). Yet
the zesty fix was a prereq for the SRU itself.
Lets put the Xenial and Yakkety fixes into SRU queue now.
@corey.bryant - the same it true for the
Full path tests were done along the qemu 2.8 merge that now passed.
I'm uploading the test logs - with those in place I can finally again migrate
all combinations from T or T+UCA through X->Y->Z and back til X (note back
working bur not supported).tar -czf.
--
You received this bug
This bug was fixed in the package qemu - 1:2.8+dfsg-2ubuntu1
---
qemu (1:2.8+dfsg-2ubuntu1) zesty; urgency=medium
* Merge with Debian; remaining changes:
- add qemu-kvm init script and defaults file
(d/qemu-system-common.qemu-kvm.*)
- d/rules, d/qemu-kvm-init: add and
Testing of migrations from liberty with the following patch were
successful. However we may need to hold off on uploading to liberty
until later releases are fixed. http://paste.ubuntu.com/23827800/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Testing of migrations from liberty with the following patch were
successful. However we may need to hold off on uploading to liberty
until later releases are fixed. http://paste.ubuntu.com/23827800/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu (Ubuntu Yakkety)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cloud-archive/liberty
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
** Changed in: cloud-archive/liberty
Status: New => In Progress
** Changed in: cloud-archive/liberty
Importance: Undecided => Critical
--
** Also affects: cloud-archive/liberty
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
** Changed in: cloud-archive/liberty
Status: New => In Progress
** Changed in: cloud-archive/liberty
Importance: Undecided => Critical
--
Note: restart ~ start/stop in this context. If you keep a QEMU process
alive it is not going to change the machine type. It is clear from the
comments but just to make sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Zesty)
Importance: Critical
Status: Confirmed
** Also affects: qemu-kvm (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Yakkety)
Sorry it took so long, but I'm happy that I finally found the right
people to talk about it, summarizing the issue once more and then
subscribing a bunch of people to make the right call for the UCA on
this.
Affected:
- Trusty type guests in Liberty/Mitaka/Xenial/Yakkety/Zesty
- Utopic type
I still got the same error with the ppa:
2016-11-14T13:11:15.479395Z qemu-system-x86_64: Unknown ramblock
"/rom@etc/acpi/rsdp", cannot accept migration
2016-11-14T13:11:15.479419Z qemu-system-x86_64: error while loading state for
instance 0x0 of device 'ram'
2016-11-14T13:11:15.479613Z
I prepped a ppa with the "correct" fix (utopic type being 2.1) at:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-1641532-tu-machine-type-ambiguous
All three Releases (Xenial, Yakkety, Zesty) are building right now in the ppa
and should be available in about an hour.
Note @ UCA Team - if
I'll create a ppa for the reporter to check on his case but before
getting closer to a real upload we need not only this test but extend
the current migration tests to more UCA combinations.
I can do the latter but it needs a bit of time to run and sort out
potential unrelated issues.
--
You
Luckly the compat function on Trusty was correct on pc_compat_2_0 which
might be the reason this works for the trusty type in my tests so far.
Notes for testing:
- extend to all T-UCA versions
- Spawn the native T-UCA guest version in those cases to migrate
- Spawn at least the faulty case
35 matches
Mail list logo
