IBM KVM on P8 saga: FreeBSD-11.0-ALPHA1-powerpc-powerpc64-20160528-r300895 won't boot

[Nathan Whitehorn]

You may need to run ppc64_cpu --smt=off on the KVM host first. I can 
reproduce hangs in late boot without the threads option and am working 
on it. It would be great if you could file a PR.
-Nathan

On 06/07/16 08:55, Luciano Mannucci wrote:
> On Thu, 2 Jun 2016 13:45:07 -0700
> Nathan Whitehorn <nwhitehorn at freebsd.org> wrote:
>
>> Interesting. Can you tell me what happens if you add -threads 8 to the
>> QEMU command line to expose all the threads?
> Yes.
> It says:
>
> Error starting domain: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option
>
> Details:
>
> Error starting domain: internal error: process exited while connecting to
> monitor: qemu-system-ppc64: -threads: invalid option
>
>
> Traceback (most recent call last):
>    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
>      callback(asyncjob, *args, **kwargs)
>    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
>      callback(*args, **kwargs)
>    File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
>      ret = fn(self, *args, **kwargs)
>    File "/usr/share/virt-manager/virtManager/domain.py", line 1437, in startup
>      self._backend.create()
>    File "/usr/local/lib/python2.7/site-packages/libvirt.py", line 1035, in create
>      if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option
>
> I've added:
> <qemu:commandline>
>      <qemu:arg value='-threads'/>
>      <qemu:arg value='8'/>
> </qemu:commandline>
>
> to the xml domain.
>
> Luciano.