Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

virt-manager uses the emulator path for xen at /usr/lib/xen/bin/qemu-
system-i386. This stops any installation of new images through virt-manager. I
worked around it by making the xen/bin folder and symlinking the qemu-
system-i386 binary.

This is still broken.  For reference, Red Hat fixed this 1 and 1/2 years ago:

https://bugzilla.redhat.com/show_bug.cgi?id=1334554

Cheers.

Just to report that this is still an issue on Buster. Apparently
creating the links (ln -s) helps, just like RH did as shown in
that bugzilla.

Thanks!

Confirming this is still a problem in 10.2. Also, virt-manager appears
to specify the wrong emulator in its optional configuration page. It
says it's going to use qemu-system-i386, even though the architecture to
be installed is x86_64. However, it will use a softlink to
/usr/bin/qemu-system-x86_64 to create a new vm.


On Wed, 13 Mar 2019 12:32:36 +0100 Dejan Muhamedagic
<dejanmm@fastmail.fm> wrote:> Package: virtinst

 > Version: 1:2.0.0-3
 > Followup-For: Bug #830307
 >
 > Just to report that this is still an issue on Buster. Apparently
 > creating the links (ln -s) helps, just like RH did as shown in
 > that bugzilla.
 >
 > Thanks!
 >
 >
 > -- System Information:
 > Debian Release: buster/sid
 > APT prefers testing
 > APT policy: (500, 'testing')
 > Architecture: amd64 (x86_64)
 > Foreign Architectures: i386
 >
 > Kernel: Linux 4.19.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
 > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
 > Shell: /bin/sh linked to /usr/bin/dash
 > Init: systemd (via /run/systemd/system)
 > LSM: AppArmor: enabled
 >
 > Versions of packages virtinst depends on:
 > ii e2fsprogs 1.44.5-1
 > ii genisoimage 9:1.1.11-3+b2
 > ii gir1.2-libosinfo-1.0 1.2.0-1
 > ii python3 3.7.2-1
 > ii python3-distutils 3.7.2-3
 > ii python3-gi 3.30.4-1
 > ii python3-libvirt 5.0.0-1
 > ii python3-libxml2 2.9.4+dfsg1-7+b3
 > ii python3-requests 2.20.0-2
 >
 > Versions of packages virtinst recommends:
 > ii qemu-utils 1:3.1+dfsg-4
 > ii virt-viewer 7.0-1
 >
 > virtinst suggests no packages.
 >
 > -- no debconf information
 >
 >

Further to my previous message, it appears that the nominal architecture
makes no difference to qemu, as it emulates no CPU instructions:
https://wiki.xen.org/wiki/QEMU_Upstream#Why_is_qemu-system-i386_used_even_on_x86_64_and_even_non-x86.3F

The qemu-system-i386 emulator is always used, regardless of the
architecture being installed. So, while confusing, virt-manager's
emulator specification is actually correct.