Package: virt-manager
Version: 1:5.1.0-1
Severity: normal
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
User: [email protected]
Usertags: amd64
User: [email protected]
Usertags: s390x
Dear Maintainer,
* What led up to the situation?
I wanted to use virt-manager to install a debian s390x guest on an amd64 host
* What exactly did you do (or not do) that was effective (or
ineffective)?
I used virt-manager in the ordinary way, and selected the s390x architecture
* What was the outcome of this action?
virt-manager got as far as attempting to boot the guest but then indicated that
the guest was not running.
* What outcome did you expect instead?
A dialogue with the debian installer resulting in a viable s390x installation.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 7.0.13+deb14-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages virt-manager depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.49.0-4+b1
ii gir1.2-gtk-3.0 3.24.52-1
ii gir1.2-gtk-vnc-2.0 1.5.0-1+b2
ii gir1.2-gtksource-4 4.8.4-9+b1
ii gir1.2-libosinfo-1.0 1.12.0-3+b2
ii gir1.2-libvirt-glib-1.0 5.0.0-4
ii gir1.2-vte-2.91 0.84.0-2
ii python3 3.13.9-3+b1
ii python3-gi 3.56.3-1
ii python3-gi-cairo 3.56.3-1
ii python3-libvirt 12.4.0-1
ii virt-install 1:5.1.0-1
Versions of packages virt-manager recommends:
ii gir1.2-ayatanaappindicator3-0.1 0.5.94-1.1
ii gir1.2-spiceclientglib-2.0 0.42-4+b1
ii gir1.2-spiceclientgtk-3.0 0.42-4+b1
ii libvirt-daemon-system 12.4.0-1
Versions of packages virt-manager suggests:
ii gir1.2-secret-1 0.21.7-2+b1
ii gnome-keyring 50.0-1
pn python3-guestfs <none>
pn ssh-askpass <none>
pn virt-viewer <none>
Versions of packages virt-manager is related to:
ii libvirt-clients 12.4.0-1
ii libvirt-daemon 12.4.0-1
ii libvirt0 12.4.0-1
ii osinfo-db 0.20250606-1
-- no debconf information
