Re: KVM on 440GP

[Corey Minyard <minyard@acm.org>]

Alexander Graf wrote:
> On 22.01.2010, at 19:29, Corey Minyard wrote:
>
>   
>> Alexander Graf wrote:
>>     
>>>  
>>>       
>>>> I'm using the qemu at git://git.savannah.nongnu.org/qemu.git, not the one at git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git, because the latter wouldn't build.  I suppose those are the build problems you speak of.  I'll see if I can get the latter working.
>>>>    
>>>>         
>>> That's the correct one.
>>>  
>>>       
>> I assume you mean git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git is the correct one.
>>
>> There's lots of problems getting it to compile.  There's no support in target-ppc for KVM_CAP_MP_STATE, so I'm currently backing up kernels until I find one that doesn't have that capability.
>>     
>
> I mean git://git.savannah.nongnu.org/qemu.git is the correct one. The KVM support in qemu-kvm is broken. Same as for S390 :-).
>
> Alex
>   
Ah, ok, then I am using the right one.

I tried using telnet for the console, and it worked for a little while:

root@ebony:~# ./qemu-system-ppcemb --enable-kvm -nographic -m 128 -M bamb
oo -kernel uImage.bamboo -L . -append "" -m 64 -serial tcp::4444,server
QEMU waiting for connection on: tcp:0.0.0.0:4444,server
Truncating memory to 64 MiB to fit SDRAM controller limits.
QEMU 0.12.50 monitor - type 'help' for more information
(qemu) info kvm
kvm support: enabled
(qemu)

So things are getting closer, but there's no output on the telnet screen.

Doing an "info registers" causes qemu to abort.

Now, nothing should have changed, but it's crashing at startup:

root@ebony:~# ./qemu-system-ppcemb -nographic -m 128 -M bamboo -kernel uI
mage.bamboo -L . -append "" -m 64 -serial tcp::4444,server
QEMU waiting for connection on: tcp:0.0.0.0:4444,server
Truncating memory to 64 MiB to fit SDRAM controller limits.
QEMU 0.12.0 monitor - type 'help' for more information
(qemu) qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000

NIP 00000000   LR 00000000 CTR 00000000 XER 00000000
MSR 00000000 HID0 00000300  HF 00000000 idx 0
Segmentatio

backtrace show the invalid memory address, and the segfault is due to 
something happening while printing out the information.

Still poking around.

-corey