| 2022-09-02 08:15:59 |
Paride Legovini |
bug |
|
|
added bug |
| 2022-09-02 08:33:42 |
Paride Legovini |
bug |
|
|
added subscriber Christian Ehrhardt |
| 2022-09-02 08:33:55 |
Frank Heimes |
tags |
|
ppc64el |
|
| 2022-09-02 08:34:18 |
Frank Heimes |
bug |
|
|
added subscriber Frank Heimes |
| 2022-09-05 08:12:51 |
Paride Legovini |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-09-05 08:12:51 |
Paride Legovini |
bug task added |
|
autopkgtest (Ubuntu Jammy) |
|
| 2022-09-05 08:36:59 |
Paride Legovini |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019189 |
|
| 2022-09-05 08:36:59 |
Paride Legovini |
bug task added |
|
autopkgtest (Debian) |
|
| 2022-09-07 14:27:02 |
Bug Watch Updater |
autopkgtest (Debian): status |
Unknown |
Fix Committed |
|
| 2022-09-07 15:24:15 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paride/ubuntu/+source/autopkgtest/+git/autopkgtest/+merge/429579 |
|
| 2022-09-07 17:11:11 |
Brian Murray |
autopkgtest (Ubuntu): importance |
Undecided |
High |
|
| 2022-09-07 17:11:13 |
Brian Murray |
autopkgtest (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-09-07 17:11:17 |
Brian Murray |
autopkgtest (Ubuntu): status |
New |
Triaged |
|
| 2022-09-07 17:11:20 |
Brian Murray |
autopkgtest (Ubuntu Jammy): status |
New |
Triaged |
|
| 2022-09-07 19:30:28 |
Paride Legovini |
autopkgtest (Ubuntu): assignee |
|
Paride Legovini (paride) |
|
| 2022-09-07 19:30:31 |
Paride Legovini |
autopkgtest (Ubuntu Jammy): assignee |
|
Paride Legovini (paride) |
|
| 2022-09-12 12:51:54 |
Launchpad Janitor |
autopkgtest (Ubuntu): status |
Triaged |
Fix Released |
|
| 2022-09-12 14:28:55 |
Paride Legovini |
autopkgtest (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2022-09-15 13:27:00 |
Paride Legovini |
description |
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected. The extreme slowness of the VMs made me think that something was off with the virtualization settings. I modified autopkgtest_qemu.py so that qemu-system-ppc64le is called with '-machine accel=kvm' (which I think is the same as '-machine pseries,accel=kvm' with pseries being the default machine type).
With this change everything is very fast and reliable. These warnings also went away:
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ccf-assist=on
indicating that we were using TCG emulation before.
I imagine that Qemu has good reasons not to default to accel=kvm or accel=kvm:tcg on ppc64, but think it's reasonable to assume it's available and enable it in autopkgtest.
We can fix this in autopkgtest upstream, but it would be nice to verify if this is an issue with Debian too before submitting a salsa MR.
[1] https://wiki.qemu.org/Documentation/TCG |
[ Impact ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected.
This happens because autopkgtest fails to detect the system architecture as KVM capable due to a typo in the architecture name (ppc64el instead of ppc64le). This upload fixes the typo.
Fixing this bug in Jammy will allow users and developers to manually run autopkgtests on ppc64el. This is useful for example in +1 maintenance.
[ Test Plan ]
Run:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
on an affected system.
Buggy package => the command takes hours to complete and prints lots of obscure errors.
Fixed package => the command completes in minutes.
[ Where problems could occur ]
Without this fix qemu based autopkgtest could in principle complete even when KVM is available (/dev/kvm exists) but broken, as it may be in some nested virtualization scenarios. This said, without KVM qemu based appears to be very broken due to timeouts caused by its extreme slowness, so I think the risk of causing a regression is marginal.
[ Original Description ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected. The extreme slowness of the VMs made me think that something was off with the virtualization settings. I modified autopkgtest_qemu.py so that qemu-system-ppc64le is called with '-machine accel=kvm' (which I think is the same as '-machine pseries,accel=kvm' with pseries being the default machine type).
With this change everything is very fast and reliable. These warnings also went away:
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ccf-assist=on
indicating that we were using TCG emulation before.
I imagine that Qemu has good reasons not to default to accel=kvm or accel=kvm:tcg on ppc64, but think it's reasonable to assume it's available and enable it in autopkgtest.
We can fix this in autopkgtest upstream, but it would be nice to verify if this is an issue with Debian too before submitting a salsa MR.
[1] https://wiki.qemu.org/Documentation/TCG |
|
| 2022-09-15 13:27:19 |
Paride Legovini |
bug |
|
|
added subscriber Canonical's Ubuntu QA |
| 2022-09-15 13:30:27 |
Paride Legovini |
description |
[ Impact ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected.
This happens because autopkgtest fails to detect the system architecture as KVM capable due to a typo in the architecture name (ppc64el instead of ppc64le). This upload fixes the typo.
Fixing this bug in Jammy will allow users and developers to manually run autopkgtests on ppc64el. This is useful for example in +1 maintenance.
[ Test Plan ]
Run:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
on an affected system.
Buggy package => the command takes hours to complete and prints lots of obscure errors.
Fixed package => the command completes in minutes.
[ Where problems could occur ]
Without this fix qemu based autopkgtest could in principle complete even when KVM is available (/dev/kvm exists) but broken, as it may be in some nested virtualization scenarios. This said, without KVM qemu based appears to be very broken due to timeouts caused by its extreme slowness, so I think the risk of causing a regression is marginal.
[ Original Description ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected. The extreme slowness of the VMs made me think that something was off with the virtualization settings. I modified autopkgtest_qemu.py so that qemu-system-ppc64le is called with '-machine accel=kvm' (which I think is the same as '-machine pseries,accel=kvm' with pseries being the default machine type).
With this change everything is very fast and reliable. These warnings also went away:
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ccf-assist=on
indicating that we were using TCG emulation before.
I imagine that Qemu has good reasons not to default to accel=kvm or accel=kvm:tcg on ppc64, but think it's reasonable to assume it's available and enable it in autopkgtest.
We can fix this in autopkgtest upstream, but it would be nice to verify if this is an issue with Debian too before submitting a salsa MR.
[1] https://wiki.qemu.org/Documentation/TCG |
[ Impact ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected.
This happens because autopkgtest fails to detect the system architecture as KVM capable due to a typo in the architecture name (ppc64el instead of ppc64le). This upload fixes the typo.
Fixing this bug in Jammy will allow users and developers to manually run autopkgtests on ppc64el. This is useful for example in +1 maintenance.
[ Test Plan ]
Run:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
on an affected system.
Buggy package => the command takes hours to complete and prints lots of obscure errors.
Fixed package => the command completes in minutes.
[ Where problems could occur ]
Without this fix qemu based autopkgtest could in principle complete even when KVM is available (/dev/kvm exists) but broken, as it may be in some nested virtualization scenarios. This said, without KVM qemu based appears to be very broken due to timeouts caused by its extreme slowness, so I think the risk of causing a regression is marginal.
[ Other Info ]
The very same fix has been submitted and merged upstream, and released to Kinetic via a clean cherry-pick.
[ Original Description ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected. The extreme slowness of the VMs made me think that something was off with the virtualization settings. I modified autopkgtest_qemu.py so that qemu-system-ppc64le is called with '-machine accel=kvm' (which I think is the same as '-machine pseries,accel=kvm' with pseries being the default machine type).
With this change everything is very fast and reliable. These warnings also went away:
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ccf-assist=on
indicating that we were using TCG emulation before.
I imagine that Qemu has good reasons not to default to accel=kvm or accel=kvm:tcg on ppc64, but think it's reasonable to assume it's available and enable it in autopkgtest.
We can fix this in autopkgtest upstream, but it would be nice to verify if this is an issue with Debian too before submitting a salsa MR.
[1] https://wiki.qemu.org/Documentation/TCG |
|
| 2022-09-15 13:38:06 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paride/ubuntu/+source/autopkgtest/+git/autopkgtest/+merge/429974 |
|
| 2022-09-16 16:21:32 |
Paride Legovini |
description |
[ Impact ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected.
This happens because autopkgtest fails to detect the system architecture as KVM capable due to a typo in the architecture name (ppc64el instead of ppc64le). This upload fixes the typo.
Fixing this bug in Jammy will allow users and developers to manually run autopkgtests on ppc64el. This is useful for example in +1 maintenance.
[ Test Plan ]
Run:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
on an affected system.
Buggy package => the command takes hours to complete and prints lots of obscure errors.
Fixed package => the command completes in minutes.
[ Where problems could occur ]
Without this fix qemu based autopkgtest could in principle complete even when KVM is available (/dev/kvm exists) but broken, as it may be in some nested virtualization scenarios. This said, without KVM qemu based appears to be very broken due to timeouts caused by its extreme slowness, so I think the risk of causing a regression is marginal.
[ Other Info ]
The very same fix has been submitted and merged upstream, and released to Kinetic via a clean cherry-pick.
[ Original Description ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected. The extreme slowness of the VMs made me think that something was off with the virtualization settings. I modified autopkgtest_qemu.py so that qemu-system-ppc64le is called with '-machine accel=kvm' (which I think is the same as '-machine pseries,accel=kvm' with pseries being the default machine type).
With this change everything is very fast and reliable. These warnings also went away:
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ccf-assist=on
indicating that we were using TCG emulation before.
I imagine that Qemu has good reasons not to default to accel=kvm or accel=kvm:tcg on ppc64, but think it's reasonable to assume it's available and enable it in autopkgtest.
We can fix this in autopkgtest upstream, but it would be nice to verify if this is an issue with Debian too before submitting a salsa MR.
[1] https://wiki.qemu.org/Documentation/TCG |
[ Impact ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected.
This happens because autopkgtest fails to detect the system architecture as KVM capable due to a typo in the architecture name (ppc64el instead of ppc64le). This upload fixes the typo.
Fixing this bug in Jammy will allow users and developers to manually run autopkgtests on ppc64el. This is useful for example in +1 maintenance.
[ Test Plan ]
Run:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
on an affected system (= a KVM-capable POWER machine running Jammy).
Buggy package => the command takes hours to complete and prints lots of obscure errors.
Fixed package => the command completes in minutes.
[ Where problems could occur ]
Without this fix qemu based autopkgtest could in principle complete even when KVM is available (/dev/kvm exists) but broken, as it may be in some nested virtualization scenarios. This said, without KVM qemu based appears to be very broken due to timeouts caused by its extreme slowness, so I think the risk of causing a regression is marginal.
[ Other Info ]
The very same fix has been submitted and merged upstream, and released to Kinetic via a clean cherry-pick.
[ Original Description ]
On Power9 the qemu based autopkgtest commands create VMs that are extremely slow and fail with obscure errors (partially discussed in LP: #1973628, comment 8). This can be reproduced for example by running:
autopkgtest-buildvm-ubuntu-cloud -v -r jammy --ram-size 1024
but autopkgtest-virt-qemu is also affected. The extreme slowness of the VMs made me think that something was off with the virtualization settings. I modified autopkgtest_qemu.py so that qemu-system-ppc64le is called with '-machine accel=kvm' (which I think is the same as '-machine pseries,accel=kvm' with pseries being the default machine type).
With this change everything is very fast and reliable. These warnings also went away:
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64le: warning: TCG doesn't support requested feature, cap-ccf-assist=on
indicating that we were using TCG emulation before.
I imagine that Qemu has good reasons not to default to accel=kvm or accel=kvm:tcg on ppc64, but think it's reasonable to assume it's available and enable it in autopkgtest.
We can fix this in autopkgtest upstream, but it would be nice to verify if this is an issue with Debian too before submitting a salsa MR.
[1] https://wiki.qemu.org/Documentation/TCG |
|
| 2022-09-20 23:19:11 |
Brian Murray |
autopkgtest (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-09-20 23:19:13 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-09-20 23:19:15 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2022-09-20 23:19:19 |
Brian Murray |
tags |
ppc64el |
ppc64el verification-needed verification-needed-jammy |
|
| 2022-09-22 08:01:13 |
Frank Heimes |
attachment added |
|
verification.txt https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1988527/+attachment/5618000/+files/verification.txt |
|
| 2022-09-22 08:02:38 |
Frank Heimes |
tags |
ppc64el verification-needed verification-needed-jammy |
ppc64el verification-done-jammy verification-needed |
|
| 2022-09-26 16:05:29 |
Bug Watch Updater |
autopkgtest (Debian): status |
Fix Committed |
Fix Released |
|
| 2022-10-05 03:45:06 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-10-05 03:45:27 |
Launchpad Janitor |
autopkgtest (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
