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 libvirt-clients
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: libvirt-clients
Version: 3.0.0-3
Severity: normal
Dear Maintainer,
`virsh capabilities` does not report <guest> section for some non-native
qemu-system-$arch.
libvirt api (https://libvirt.org/drvqemu.html#prereq) describes that
"
Deployment pre-requisites
QEMU emulators: The driver will probe /usr/bin for the presence of qemu,
qemu-system-x86_64, qemu-system-microblaze, qemu-system-microblazeel,
qemu-system-mips,qemu-system-mipsel, qemu-system-sparc,qemu-system-ppc.
The results of this can be seen from the capabilities XML output "
However, qemu-system-sparc nor qemu-system-mips are not reported.
qemu-system-x86, qemu-system-arm, qemu-system-ppc are reported however.
(Host is x86_64 debian sid)
This makes creating guest domain from XML impossible for sparc* and
mips* guests:
virsh -c qemu:///system define debian-sid-sparc64.xml
error: Failed to define domain from debian-sid-sparc64.xml
error: invalid argument: could not find capabilities for arch=sparc64
Regards,
Adrian
--- 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 ---
