microvm is not the default type for qemu-system-x86_64-microvm >=qemu5.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Christian Ehrhardt |
Bug Description
[Impact]
* A change of the build system has caused a configuration change
to be ignored. Due to that the defaults of the machine type are
no more correct.
* With the default set (in hirsute) you no more needed -M microvm as an
argument as this was the default. But by losing this default upgrades
from there will fail to start the microvm now.
* The fix is trivial and ensures that the type is known when built
with meson
[Test Plan]
* Run this:
$ qemu-system-
That is the special reduced build for microvms. It currently reports
microvm microvm (i386)
pc-i440fx-hirsute Ubuntu 21.04 PC (i440FX + PIIX, 1996) (default)
But it should report
microvm microvm (i386) (default)
[Where problems could occur]
* Of the many things that qemu does this only affects qemu-system-x86_64-
microvm which is a special build
(https:/
So the use cases of that could be affected.
[Other Info]
* Usually examples list to specify the type explicitly, and everyone
doing so did not have a problem due to that missed default type.
---
In Focal microvm worked and it was a fine addition for those that wanted to try this approach (mature solution of qemu/kvm reduced for a specific use case) to minimal VMs compared to the new projects (very use-case dedicated, but therefore missing quite some features) that spawned.
But it turns out the configuration to make it a default is broken since qemu 5.2.
Correct (Focal)
root@f:~# qemu-system-
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https:/
It is still usable and that might explain why - even not being the prime use case - we had zero reports of this so far.
The reason for the latter is that explicitly stating -M microvm (common) overcomes the issue and so do a few combinations with -nodefaults.
Thanks to Michael Torkaev for spotting and also fixing this.
But we should backport this as an SRU.
TODOs to call this bug fixed:
- add a testcase to the regression tests
- SRU the fix
Related branches
- Utkarsh Gupta (community): Approve
- Dan Streetman (community): Abstain
- Ubuntu Stable Release Updates Team: Pending requested
- Canonical Server packageset reviewers: Pending requested
- Canonical Server: Pending requested
-
Diff: 77 lines (+30/-6)2 files modifieddebian/changelog (+10/-0)
debian/rules (+20/-6)
CVE References
Changed in qemu (Ubuntu): | |
status: | New → Triaged |
description: | updated |
description: | updated |
tags: | added: server-next |
description: | updated |
Changed in qemu (Ubuntu Hirsute): | |
assignee: | nobody → Christian Ehrhardt (paelzer) |
description: | updated |
description: | updated |
Fixed by 8f23f50ea45f988 37204c597e
commit 3f9e518010693a9
Author: Michael Tokarev <email address hidden>
Date: Tue Jul 20 08:56:48 2021 +0300
fix microvm default machine type for a new build system (LP#1936894)