Your message dated Wed, 12 Apr 2017 09:15:15 +0200 with message-id <20170412071515.brvf4cryhjd5b...@bogon.m.sigxcpu.org> and subject line Re: [Pkg-libvirt-maintainers] Bug#854125: libvirt0: could not find capabilities for arch=mips has caused the Debian Bug report #854125, regarding libvirt0: could not find capabilities for arch=mips to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 854125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libvirt0 Version: 3.0.0-2 Severity: important I am trying to create a mips based vm, but it seems that libvirt does not support this architecture in the current debian testing. If I run 'virsh capabilities', there is no mention of mips or variants like mipsel, mips64, mips64el. If I try to make a vm with virt-manager, mips is not an option in the architecture menu. If I try to make a vm from an xml file with 'virsh create vm.xml' I get the output error: Failed to create domain from vm.xml error: invalid argument: could not find capabilities for arch=mips I do have qemu-system-mips installed (also from package management) and I can start the machine with qemu directly, so at least this excludes qemu being the problem. Thank you. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libvirt0 depends on: ii libapparmor1 2.11.0-2 ii libaudit1 1:2.6.7-1 ii libavahi-client3 0.6.32-2 ii libavahi-common3 0.6.32-2 ii libc6 2.24-9 ii libcap-ng0 0.7.7-3 ii libdbus-1-3 1.10.14-1 ii libdevmapper1.02.1 2:1.02.137-1 ii libgnutls30 3.5.8-1 ii libnl-3-200 3.2.27-1 ii libnl-route-3-200 3.2.27-1 ii libnuma1 2.0.11-2.1 ii libsasl2-2 2.1.27~101-g0780600+dfsg-2 ii libselinux1 2.6-3 ii libssh2-1 1.7.0-1 ii libxen-4.8 4.8.1~pre.2017.01.23-1 ii libxml2 2.9.4+dfsg1-2.2 ii libyajl2 2.1.0-2 Versions of packages libvirt0 recommends: ii lvm2 2.02.168-1 libvirt0 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: libvirt/3.0.0-4 Hi Niels, On Tue, Apr 11, 2017 at 04:05:00PM +0000, Niels Thykier wrote: > On Wed, 15 Mar 2017 05:44:20 +0100 Guido =?iso-8859-1?Q?G=FCnther?= > <a...@sigxcpu.org> wrote: > > control: severity -1 grave > > > > Hi, > > On Sat, Feb 04, 2017 at 12:36:42PM +0100, Alexandru Geana wrote: > > > Package: libvirt0 > > > Version: 3.0.0-2 > > > Severity: important > > > > > > I am trying to create a mips based vm, but it seems that libvirt does > > > not support this architecture in the current debian testing. > > > > > > If I run 'virsh capabilities', there is no mention of mips or variants > > > like mipsel, mips64, mips64el. If I try to make a vm with virt-manager, > > > mips is not an option in the architecture menu. If I try to make a vm > > > from an xml file with 'virsh create vm.xml' I get the output > > > > > > error: Failed to create domain from vm.xml > > > error: invalid argument: could not find capabilities for arch=mips > > > > > > I do have qemu-system-mips installed (also from package management) and > > > I can start the machine with qemu directly, so at least this excludes > > > qemu being the problem. > > > > The problem is that libvirt fails to probe CPU definitions on mips. I'll > > have a look. Taggig as grave since this breaks a lot of existing VM > > configurations. > > Cheers, > > -- Guido > > > > > > Hi Guido, > > Do you have any news for us on this bug? :) Fixed with the upload in march but a typo in the changelog prevented the close on upload. Sorry. -- Guido
--- End Message ---
