Comment 7 for bug 1737211
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: [Bug 1737211] Re: ipxe-qemu is missing support for devices since qemu 2.7 | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
> I'm already of why the prebuilt ones were removed,
great
> but that doesnt't
> actually answer how they were missed when updating qemu to 2.7 (vmxnet3
> PXE is mentioned in the changelog).
Updating qemu is distinct from updating ipxe.
So when we moved what was I think qemu 2.6.1 -> 2.8 that did not
affect ipxe at all.
And at least I didn't catch the vmxnet3 change to take action on it.
IPXE only recently got to my attention to be so outdated by not being
a sync as I'd have thought.
Which triggered all my tests finding the migration issues, so we
wouldn't have been able to "just update" the last cycles anyway.
> Part of the problem is that on
> updating, all the PXE roms are blindly removed without checking for any
> new ones since the last release.
It is an explicit packaging, new built artifacts/binaries when moving
to a newer source are not automatically included in the package.
This is rather common approach in many packages - although usually
there are warnings that you have to explicitly ignore.
I didn't check the details on the Debian package build why this didn't
trigger there, but our reasons was that we were too outdated.
TL;DR you are right with everything you suggest to add and I hope to
address it when doing the coming qemu/libvirt move - this time
ensuring ipxe (and other roms as well actually) have a better match.