From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: qemu gl changes are broken.
Date: Wed, 22 Aug 2012 01:38:11 +0100 [thread overview]
Message-ID: <7921445.r3rDbWunGC@helios> (raw)
In-Reply-To: <50341DD7.1000405@intel.com>
On Tuesday 21 August 2012 16:46:31 Scott Garman wrote:
> On 08/21/2012 10:45 AM, Scott Garman wrote:
> > On 08/21/2012 09:21 AM, Scott Garman wrote:
> >> Hello,
> >>
> >> I tried building some images overnight with the latest master, and could
> >> not get them to run this morning with qemu - I got an odd error that a
> >> VNC server was started instead?
> >>
> >> Just on a hunch, I reverted the following commits:
> >>
> >> qemu: Fix broken accidental path move
> >> qemu-git: Drop GL passthrough support
> >> qemu-0.15: Drop GL passthrough support
> >>
> >> rebuilt qemu-native, and now qemu works correctly.
> >>
> >> I have no idea why qemu is trying to fallback on a VNC server, as I did
> >> not have one running on my machine. I know we use VNC for our
> >> autobuilder sanity tests, but those haven't been integrated into the
> >> runqemu scripts as far as I can tell.
> >
> > This may need further research, I seem to have it working on another
> > machine. I'll report back once I've learned more.
>
> Ok, I can no longer reproduce this issue anymore, even on the original
> machine. Figures. :-/
Is this perhaps what happens when DISPLAY is not set? Just a guess...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-08-22 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 16:21 qemu gl changes are broken Scott Garman
2012-08-21 17:45 ` Scott Garman
2012-08-21 23:46 ` Scott Garman
2012-08-22 0:38 ` Paul Eggleton [this message]
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=7921445.r3rDbWunGC@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.com \
/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