#993882 power64le: virt-manager refuses to start fresh install of FreeBSD 13.0 due to qemu issue on power8 host (safe cache missing)

Package:
virt-manager
Source:
virt-manager
Submitter:
Karel Gardas
Date:
2022-01-11 08:06:03 UTC
Severity:
normal
#993882#5
Date:
2021-09-07 18:44:58 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

An attempt to configure and run newly created FreeBSD 13.0 VM

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Select "Local install media"
Leave architecture options as they are (ppc64le/pseries)
Specify boot iso (FBSD 13.0 release powerpc-powerpc64-disc1.iso)
Specify OS as 'FreeBSD 13.0'
Set memory to 8129MB
Set CPUs to 4
Enable storage for this virtual machine
Leave 20GB as space for disk
Finish with provided option.
This starts install process which results in "Unable to complete install: 'internal error: qemu unexpectedly closed the monitor: <time>
 qemu-system-ppc64le: Requested saef cache capability level not supported by KVM Try appending -machine cap-cfpc=broken'

   * What was the outcome of this action?

On Close button click, the machine is destroyed hence there is no outcome.

   * What outcome did you expect instead?
i
Newly created and run FBSD 13.0 machine.

*** End of the template - remove these template lines ***
#993882#10
Date:
2021-09-07 19:19:52 UTC
From:
To:
Hi,

one addition. I've noticed that architecture options are probably wrong
for the pseries machine. By default it selects ppc64le where I believe
ppc64 is the right one.

I've tested both options here so the bug is not related to wrong default
value of architecture options. Just to let you know.

Thanks!
#993882#15
Date:
2021-09-07 20:37:58 UTC
From:
To:
Hello,

tested the same on Ubuntu 20.04 LTS up-to-date and it shows the same
issue although its qemu is probably somewhat older version.

Conclusion: not broken by debian, not broken recently. Probably general
issue on power8 (or general issue on my machine.)

Karel
#993882#20
Date:
2022-01-08 19:30:13 UTC
From:
To:
Hi Maintainer

The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].

This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.

Regards
Graham


[1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html
[2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi