virsh maxvcpus throws "error: invalid argument: unable to find any emulator to serve 'ppc64le' architecture"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Undecided
|
Christian Ehrhardt |
Bug Description
== Comment: #0 - Satheesh Rajendran <email address hidden> - 2017-03-20 05:00:21 ==
---Problem Description---
virsh maxvcpus throws "error: invalid argument: unable to find any emulator to serve 'ppc64le' architecture"
Contact Information = <email address hidden>
---uname output---
Linux ltc-test-ci1 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = power 8 ppc64le
---Debugger---
A debugger is not configured
---Steps to Reproduce---
#virsh maxvcpus
error: invalid argument: unable to find any emulator to serve 'ppc64le' architecture
Userspace tool common name: libvirt
The userspace tool has the following bit modes: both
Userspace rpm: ii libvirt-bin 2.5.0-3ubuntu4 ppc64el programs for the libvirt library,ii qemu-kvm 1:2.8+dfsg-3ubuntu2 ppc64el QEMU Full virtualization
Userspace tool obtained from project website: na
*Additional Instructions for <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
-Attach ltrace and strace of userspace application.
== Comment: #1 - Satheesh Rajendran <email address hidden> - 2017-03-20 05:07:45 ==
#virsh capabilities
<capabilities>
<host>
<uuid>
<cpu>
<
<
<
<topology sockets='1' cores='5' threads='8'/>
<pages unit='KiB' size='64'/>
<pages unit='KiB' size='16384'/>
<pages unit='KiB' size='16777216'/>
</cpu>
...
...
...
....
<guest>
<os_
<arch name='ppc64le'>
<
<
<machine maxCpus=
<machine canonical=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<domain type='qemu'/>
<domain type='kvm'>
<machine maxCpus=
<machine canonical=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
<machine maxCpus=
</domain>
</arch>
<features>
<
<deviceboot/>
<disksnapshot default='on' toggle='no'/>
</features>
</guest>
...
...
~# arch
ppc64le
== Comment: #2 - VIPIN K. PARASHAR <email address hidden> - 2017-03-20 06:40:12 ==
$ git log bd4ae4f5e881276b -1
commit bd4ae4f5e881276
Author: Peter Krempa <email address hidden>
Date: Thu Dec 8 09:36:43 2016 +0100
virsh: maxvcpus: Always fall back to the old command if domain caps fail
1ec22be5 added code that detects the maximum cpu count according to
domain capabilities. The code fell back to the old command only if the
API was not supported. If the API fails for other reasons the command
would fail. There's no point in not trying the old API in such case.
https:/
$ git tag --contains bd4ae4f5e881276b0 | grep -v rc
v3.0.0
v3.1.0
$
Commit bd4ae4f5e881276b should fix this issue.
Its available in libvirt version 3.0 and above.
tags: | added: architecture-ppc64le bugnameltc-152716 severity-high targetmilestone-inin1704 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → libvirt (Ubuntu) |
Changed in libvirt (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → ChristianEhrhardt (paelzer) |
Jon,
Can someone from Server Team look at this bug?
Thanks.
Michael
On 03/20/2017 04:49 AM, bugproxy wrote: 091a-43b7- 9eff-c78858b179 ce</uuid> /arch> POWER8< /model> IBM</vendor> hvm</os_ type> 64</wordsize> /usr/bin/ qemu-system- ppc64le< /emulator> '255'>pseries- zesty</ machine> 'pseries- zesty' maxCpus= '255'>pseries< /machine> '1'>ref405ep< /machine> '1'>virtex- ml507</ machine> '2048'> powernv< /machine> '32'>ppce500< /machine> '15'>mpc8544ds< /machine> '1'>bamboo< /machine> '1'>g3beige< /machine> '1'>prep< /machine> '1'>mac99< /machine> '255'>pseries- 2.6</machine> '255'>pseries- 2.7</machine> '255'>pseries- 2.8</machine> '255'>pseries- 2.4</machine> '255'>pseries- 2.5</machine> '255'>pseries- 2.2</machine> '1'>taihu< /machine> '255'>pseries- 2.3</machine> '255'>pseries- xenial< /machine> '255'>pseries- yakkety< /machine> '255'>pse. ..
> Public bug reported:
>
> == Comment: #0 - Satheesh Rajendran <email address hidden> - 2017-03-20 05:00:21 ==
> ---Problem Description---
> virsh maxvcpus throws "error: invalid argument: unable to find any emulator to serve 'ppc64le' architecture"
>
> Contact Information = <email address hidden>
>
> ---uname output---
> Linux ltc-test-ci1 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
>
> Machine Type = power 8 ppc64le
>
> ---Debugger---
> A debugger is not configured
>
> ---Steps to Reproduce---
> #virsh maxvcpus
> error: invalid argument: unable to find any emulator to serve 'ppc64le' architecture
>
> Userspace tool common name: libvirt
>
> The userspace tool has the following bit modes: both
>
> Userspace rpm: ii libvirt-bin
> 2.5.0-3ubuntu4 ppc64el programs for the
> libvirt library,ii qemu-kvm 1:2.8
> +dfsg-3ubuntu2 ppc64el QEMU Full
> virtualization
>
> Userspace tool obtained from project website: na
>
> *Additional Instructions for <email address hidden>:
> -Post a private note with access information to the machine that the bug is occuring on.
> -Attach ltrace and strace of userspace application.
>
> == Comment: #1 - Satheesh Rajendran <email address hidden> - 2017-03-20 05:07:45 ==
> #virsh capabilities
> <capabilities>
>
> <host>
> <uuid>08424246-
> <cpu>
> <arch>ppc64le<
> <model>
> <vendor>
> <topology sockets='1' cores='5' threads='8'/>
> <pages unit='KiB' size='64'/>
> <pages unit='KiB' size='16384'/>
> <pages unit='KiB' size='16777216'/>
> </cpu>
> ...
> ...
> ...
> ....
> <guest>
> <os_type>
> <arch name='ppc64le'>
> <wordsize>
> <emulator>
> <machine maxCpus=
> <machine canonical=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=
> <machine maxCpus=