@Norman - Not a bad idea. The content is synced from the source already,
just the size allocation is what can mismatch - it happens so early that
it is local. It was suggested like 3 times (I'm sure you could find them
on the ML-archive somewhere) or so to transfer the source-size as part
of the
Hello, thank you very much for working on this and reverting to an older
ipxe package does solve the issue. but I am curious why qemu needs to
compare it with local romfile? why cannot rom be synced from source vm?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For the actual change, you'd want to do this:
in qemu's debian/contol.in there are a bunch of Recommends and Depends like
this:
ipxe-qemu (>= 1.0.0+git-2013.c3d1e78-1~)
change all those in UCA to
ipxe-qemu (>= 1.0.0+git-20180124.fbe8c52d-0ubuntu2.1~)
That should avoid further issues with
As discussed on IRC this would most likely be a Cloud Archive only patch on top.
Therefore we don't even need a new qemu bug for it, we can add a task here.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
--
@paelzer
"@James - does the UCA for B-to-X hold also a source of ipxe-qemu-256k-
compat-efi-roms?"
Yes
"@James - does the qemu in UCA for B-to-X has [1] and [2]?
https://salsa.debian.org/qemu-team/qemu/commit/7b917f26ac6a224195f68088dcd8e8f99d932675
@paelzer
"@James - does the UCA for B-to-X hold also a source of ipxe-qemu-256k-
compat-efi-roms?"
Yes
"@James - does the qemu in UCA for B-to-X has [1] and [2]?
https://salsa.debian.org/qemu-team/qemu/commit/7b917f26ac6a224195f68088dcd8e8f99d932675
Your guest already is pc-i440fx-bionic (because that is what the cloud archive
is based on).
That means that qemu expects it to already run with the newer ipxe.
The only case I can think of is that this guest was started with
- qemu 1:2.11+dfsg-1ubuntu... installed
- ipxe not yet at
And this is the virsh dump: http://paste.openstack.org/show/740502/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713490
Title:
error migrating blocked on virtio-net-pci.rom
To manage
@Christian E.
qemu version stayed the same:
ii qemu 1:2.11+dfsg-1ubuntu7.5~cloud0
amd64fast processor emulator
ii qemu-block-extra:amd64 1:2.11+dfsg-1ubuntu7.5~cloud0
amd64extra block backend modules for
I subscribed James and Corey as this might be special to Ubuntu Cloud Archive.
Maybe an upgrade path that we have missed?
@James/Corey - do you see that as well?
@Christian Z. - what version of qemu was installed when failing?
Overall this looks like the ipxe from Bionic in the cloud archive
We just upgraded an OpenStack compute from 16.04.4 to 16.04.5 and live
migration is broken for VMs running on a 16.04.4 host to a 16.04.5 host.
We see these error messages in nova-compute.log on a 16.04.4 host:
2019-01-08 07:43:56.117 100671 ERROR nova.virt.libvirt.driver [-] [instance:
** Changed in: qemu (Debian)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713490
Title:
error migrating blocked on virtio-net-pci.rom
To manage notifications
** Changed in: qemu (Debian)
Status: New => 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/1713490
Title:
error migrating blocked on virtio-net-pci.rom
To manage notifications
This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d-
0ubuntu2
---
ipxe (1.0.0+git-20180124.fbe8c52d-0ubuntu2) bionic; urgency=medium
* debian/copyright: update copyright information to satisfy lintian
dep5 checks (LP: #1747071)
* d/p/enable-https.patch:
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu1
---
qemu (1:2.11+dfsg-1ubuntu1) bionic; urgency=medium
* Merge with Debian testing, among other fixes this includes
- fix fatal error on negative maxcpus (LP: #1722495)
- fix segfault on dump-guest-memory on
qemu 2.11 is in proposed
** Changed in: qemu (Ubuntu Bionic)
Status: In Progress => 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/1713490
Title:
error migrating blocked on
I can't file a MIR for the new src:ipxe-qemu-256k-compat we need for this bug
1713490.
Only after new queue I can open up requests.
We discussed that via mail and the TL;DR is: src:ipxe-qemu-256k-compat is the
same as src:ipxe (xenial) and has the same timeline of support and therefore
should
Bonus: since the ipxe roms are reused arm64 and ppc64le are also
affected and need the compat code in qemu to map to the compat rom
files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713490
Title:
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/336609
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713490
Title:
error migrating blocked on
actually ipxe will get the new sizes and a bump, so yes there is also a
fix in src:ipxe so setting back to triaged on that package bug task.
** Changed in: ipxe (Ubuntu Bionic)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
change will need a new src package for the compat roms, so ipxe is not affected
(but the compat is).
Qemu will carry the machine type dependent link changes matching the compat
package.
** Tags added: ipxe-18.04 qemu-18.04
** Changed in: qemu (Ubuntu Bionic)
Status: Triaged => In
** Changed in: qemu (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713490
Title:
error migrating blocked on virtio-net-pci.rom
To manage notifications about
Reported it to Debian to agree on a solution which they can use in >=Buster and
we in >=Bionic.
=> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881263
** Bug watch added: Debian Bug tracker #881263
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881263
** Also affects: qemu (Debian)
This bug was fixed in the package ipxe -
1.0.0+git-20161027.b991c67+really20150424.a25a16d-1ubuntu1
---
ipxe (1.0.0+git-20161027.b991c67+really20150424.a25a16d-1ubuntu1) artful;
urgency=medium
* Revert to the former git snapshot 20150424.a25a16d to fix changed
rom sizes that
Related MP up in
https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/329820
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713490
Title:
error migrating blocked on
No changes to Qemu planned to auto-fixup the migration, that is too complex to
try so late in the cycle. Also due to Ubuntu Cloud Archive(s) not having ipxe
in it we would have to add there as well or otherwise qemu 2.10 wouldn't be
2.10.
On LTS releases it might be better to push ipxe changes
The test builds in [1] soon abandoned) are good now.
Moving it into the same ppa that has the qemu-rc4 tests [2] to do a full
regression test over night before uploading.
Along that preparing the changes for an extra review to get extra
confidence.
[1]:
To quote something comparable, best old example to match the current case seems
to be the following:
https://lists.ubuntu.com/archives/xenial-changes/2015-November/000988.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All base roms grow ~4-5k, the EFI addon grew 20-24k.
I discussed the "might need to go backward plan" (at least for now), and there
are examples of this like:
https://lists.ubuntu.com/archives/artful-changes/2017-August/007901.html
I'm currently working on various options from turning back the time via
an AA or some magic (unlikely :-) ), or patching back to the old version
(plus a few fixes that are needed for FTBFS) but also trying to shrink
size on the new versions if that is reasonable.
It is already built with -Os so
As a follow on for ipxe we certainly want to implement a size check post build
to catch changes out of a power-of-two bucket in advance next time.
Might even be worth to discuss on ipxe upstream.
Furthermore I checked that Pike (for Xenial as in sudo add-apt-repository
It is "just" the size that breaks it, as soon as I append a bunch of zero's to
the source of the migration it will allocate 0x8000 as well and work to
migrate then.
$ truncate --size=272384 /usr/lib/ipxe/qemu/efi-virtio.rom
Unfortunately this isn't much of a "solution" as:
- it needs to be
The dev is as expected the virtio network card
There is no explicit rom specified on the guest commandlines, so they pick
their defaults.
Trying to list what they load:
$ strace -e open /usr/bin/qemu-system-x86_64 -M pc-i440fx-trusty -device
virtio-net -S
qemu-ipxe:
Z: 1.0.0+git-20150424.a25a16d-1ubuntu2
A: 1.0.0+git-20161027.b991c67-1ubuntu1
Check diff in detail:
- List of files did not change
- content and md5 obviously changed due to the update
=> Downgrading the ipxe package on artful to the level it had before
resolves the issue.
We can not
34 matches
Mail list logo
