| 2021-07-20 05:53:31 |
Christian Ehrhardt |
bug |
|
|
added bug |
| 2021-07-20 05:53:37 |
Christian Ehrhardt |
qemu (Ubuntu): status |
New |
Triaged |
|
| 2021-07-20 05:53:46 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server |
| 2021-07-20 05:54:42 |
Christian Ehrhardt |
description |
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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. |
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
|
| 2021-07-20 05:54:54 |
Christian Ehrhardt |
description |
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
|
| 2021-07-20 05:55:09 |
Christian Ehrhardt |
tags |
|
server-next |
|
| 2021-08-16 11:03:20 |
Christian Ehrhardt |
qemu (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2021-08-16 11:03:25 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-08-16 11:03:25 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Hirsute) |
|
| 2021-08-16 11:03:31 |
Christian Ehrhardt |
qemu (Ubuntu Hirsute): status |
New |
Triaged |
|
| 2021-08-19 09:31:48 |
Christian Ehrhardt |
description |
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
[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.
* The fix is trivial and ensures that the type is known when built
with meson
[Test Plan]
* Run this:
$ qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
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://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/)
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
|
| 2021-08-27 06:49:59 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/407766 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
qemu (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2020-35504 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2020-35505 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2020-35506 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2021-3527 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2021-3582 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2021-3607 |
|
| 2021-09-04 02:26:54 |
Launchpad Janitor |
cve linked |
|
2021-3608 |
|
| 2021-09-22 15:06:47 |
Christian Ehrhardt |
qemu (Ubuntu Hirsute): assignee |
|
Christian Ehrhardt (paelzer) |
|
| 2021-09-29 15:59:49 |
Christian Ehrhardt |
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.
* The fix is trivial and ensures that the type is known when built
with meson
[Test Plan]
* Run this:
$ qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
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://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/)
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
[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 loosing 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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
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://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/)
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
|
| 2021-09-29 16:00:31 |
Christian Ehrhardt |
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 loosing 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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
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://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/)
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
[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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
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://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/)
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-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386) (default)
Broken (Groovy and later)
root@i-kvm:~# qemu-system-x86_64-microvm -M ? | grep -e 'default' -e 'microvm'
microvm microvm (i386)
pc-i440fx-impish Ubuntu 21.10 PC (i440FX + PIIX, 1996) (default)
If you follow the guide
https://cpaelzer.github.io/blogs/009-microvm-in-ubuntu/
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 |
|
| 2021-09-30 10:35:41 |
Robie Basak |
qemu (Ubuntu Hirsute): status |
Triaged |
Fix Committed |
|
| 2021-09-30 10:35:43 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-09-30 10:35:44 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2021-09-30 10:35:47 |
Robie Basak |
tags |
server-next |
server-next verification-needed verification-needed-hirsute |
|
| 2021-10-04 08:58:37 |
Christian Ehrhardt |
tags |
server-next verification-needed verification-needed-hirsute |
server-next verification-done verification-done-hirsute |
|
| 2021-10-11 16:39:49 |
Launchpad Janitor |
qemu (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-10-11 16:39:56 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
