On Mon, Mar 05, 2012 at 04:16:54PM +, Mark Cave-Ayland wrote:
> On 05/03/12 15:48, Avi Kivity wrote:
>
> >>>Can you provide the command line needed to reproduce the problem?
> >>
> >>Sure. I can reproduce it here using something as simple as:
> >>
> >>./qemu-system-ppc -cdrom /dev/null -boot d
On 05/03/12 15:48, Avi Kivity wrote:
Can you provide the command line needed to reproduce the problem?
Sure. I can reproduce it here using something as simple as:
./qemu-system-ppc -cdrom /dev/null -boot d -vnc :1
What you'll see is that the framebuffer remains black in your VNC
client, as o
On 03/05/2012 12:29 PM, Mark Cave-Ayland wrote:
> On 05/03/12 09:51, Avi Kivity wrote:
>
>> On 03/04/2012 08:06 PM, Mark Cave-Ayland wrote:
>>> Hi all,
>>>
>>> I've just done a git pull to update my local repository, and it now
>>> appears that the VGA device is broken in QEMU - rather than display
On 05/03/12 09:51, Avi Kivity wrote:
On 03/04/2012 08:06 PM, Mark Cave-Ayland wrote:
Hi all,
I've just done a git pull to update my local repository, and it now
appears that the VGA device is broken in QEMU - rather than displaying
the OpenBIOS banner in my VNC client, the framebuffer remains
On 03/04/2012 08:06 PM, Mark Cave-Ayland wrote:
> Hi all,
>
> I've just done a git pull to update my local repository, and it now
> appears that the VGA device is broken in QEMU - rather than displaying
> the OpenBIOS banner in my VNC client, the framebuffer remains
> constantly black.
>
> A git bi
Hi all,
I've just done a git pull to update my local repository, and it now
appears that the VGA device is broken in QEMU - rather than displaying
the OpenBIOS banner in my VNC client, the framebuffer remains constantly
black.
A git bisect shows that the problem is caused by the following co
