[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display

From: Cédric Le Goater
Subject: Re: [Qemu-ppc] [Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected
Date: Fri, 24 Mar 2017 11:46:52 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

Hello Luigi,

I have some difficulty sorting out what is going on and what 
could be considered a regression :/ you are reporting many 
issues at the same time with a home made kernel. 

Could you please use the kernel shipped with the distro to 
start with ? 

> yes usually with 2.8 i  boot  the VM without issue on G5 Quad  with the 
> option 
> -M  pseries from 2.1 to 2.5 with kvm-pr enabled.
> i did the tests and with all pseries now on 2.9 i have the same issue.
> example:
> qemu-system-ppc64 --enable-kvm -cpu 970fx_v2.0 -m 1024 -M pseries-2.1
> qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel 

This error message is because your host kernel lacks in-kernel XICS, 
but you are saying that was not an issue with QEMU-2.8. Correct ? 
If so, that is a first thing to look at. May be the changes I made
introduced some regression in that case. 

Here is the command line I used on a 17.04 host :

        qemu-system-ppc64 -M pseries-2.[1-8],accel=kvm,kvm-type=PR -cpu 
970fx_v2.0 -m 1024 -nographic

I get this message with QEMU 2.9, for all pseries

        qemu-system-ppc64: Unable to find sPAPR CPU Core definition

with QEMU 2.8, the guest starts for pseries-2.[1-6] and fails the same
way for pseries-2.[7-8].

I tried with '-cpu 970_v2.2' and there are no issues but that is a 
defined sPAPR CPU Core. 

Did we introduce a regression in compatibility in QEMU 2.9 ?  or 
was it bogus before ? That needs a little digging. I did not work
on that part.



> but no issue if i run with -M mac99 before 2.9 was not possible use it on 
> qemu-system-ppc64
> It means it will no possible anymore in future release of qemu use open 
> firmware on powermacs 
> any moore?
>>I admit the message is not very clear, but the host kernel is
>>using a dev config.
> Im so sorry, i learn English by my self reading ml and on irc 
> chatting is too difficult where no one speak English  around.
>>> On Qoriq if i pass the -cpu e500 (normal thing) all is working right qemu 
>>> 2.9rc1
>>> all boot and so and so.
>>but you must be changing the machine right ?
> not on Qoriq because it is book3e and is not so flexible like the G5 Quad who 
> is book3s machine.
> i can run qemu kvm only with emb hardware on Qoriq
>>>On G5 the -cpu variable dont fix the issue.
>>with which machine ?
> On PowerMac G5 Quad 970MP it have similar hardware configuration of IBM 
> intellistation power 285
>> >I can build a new kernel release , usually mine dont have xics enabled 
>> >because G5
>>> dont have that feature, if needed i can enable it for testing.**
>>Yes that would be interesting.
> I will do ASAP just the time to build it .
> Thank you really much for your time and patience.
> Luigi
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

reply via email to

[Prev in Thread] Current Thread [Next in Thread]