From: Alon Levy <alevy@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-ppc@nongnu.org, Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PPC: VGA broken in git master
Date: Mon, 5 Mar 2012 20:50:51 +0200 [thread overview]
Message-ID: <20120305185051.GD20937@garlic.tlv.redhat.com> (raw)
In-Reply-To: <4F54E6F6.4060701@ilande.co.uk>
On Mon, Mar 05, 2012 at 04:16:54PM +0000, 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 -vnc :1
> >>
> >>What you'll see is that the framebuffer remains black in your VNC
> >>client, as opposed to displaying the OpenBIOS startup banner.
> >>
> >>Note that de58ac72b6a062d1a61478284c0c0f8a0428613e (and the previous
> >>commit) have a qdev bug which segfaults qemu-system-ppc on startup,
> >>however the attached patch will resolve this for you.
> >>
> >>I've also confirmed over the weekend that the bug also affects
> >>SPARC64, although testing shows that SPARC32 still seems to work okay.
> >
> >
> >Turned out that -vga std was broken cross-target. Please check
> >
> > git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/urgent
> >
> >for a fix.
>
> Hi Avi,
>
> I've just tested your patchset against git master and it looks good
> here - VGA for both PPC and SPARC64 now works again.
>
And x86_64-softmmu (just two last patches from memory/urgent).
>
> Many thanks,
>
> Mark.
>
next prev parent reply other threads:[~2012-03-05 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 18:06 [Qemu-devel] PPC: VGA broken in git master Mark Cave-Ayland
2012-03-05 9:51 ` Avi Kivity
2012-03-05 10:29 ` Mark Cave-Ayland
2012-03-05 15:48 ` Avi Kivity
2012-03-05 16:16 ` Mark Cave-Ayland
2012-03-05 18:50 ` Alon Levy [this message]
2012-03-05 10:29 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120305185051.GD20937@garlic.tlv.redhat.com \
--to=alevy@redhat.com \
--cc=avi@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).