Re: [Qemu-devel] Problem with qemu on Ubuntu Gutsy ...

[Anthony Liguori <anthony@codemonkey.ws>]

andrzej zaborowski wrote:
> On 21/11/2007, dara burke <daraburke78@yahoo.com> wrote:
>   
>> Hi Guys,
>>
>> I've been looking around for a solution to this problem that I've been
>> having with qemu on ubuntu Gutsy. It seemed to work fine on Feisty, but I
>> haven't been able to find anyone else with a similar complaint in the ubuntu
>> forums or on google or on irc, so maybe a simple upgrade problem isn't the
>> issue. I hope it's OK to post to the dev mailing list ?
>>     
>
> It is quite clearly an SDL issue, rather than qemu.
>
>   
>> The system seems to have a problem locating the framebuffer, also SDL
>> doesn't get initialized.
>>
>> babo@eire:/home/babo/qemu_dir# qemu -localtime -cdrom /dev/cdrom -m 384
>> -boot d c.img
>> Warning: No DNS servers found
>>
>>        ---------------------- DirectFB v0.9.25 ---------------------
>>              (c) 2000-2002  convergence integrated media GmbH
>>              (c) 2002-2004  convergence GmbH
>>
>> -----------------------------------------------------------
>>
>> (*) DirectFB/Core: Single Application Core. (2007-08-07 19:21)
>> (*) Direct/Memcpy: Using linux kernel memcpy()
>> (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
>>     --> No such file or directory
>> (!) DirectFB/FBDev: Error opening framebuffer device!
>> (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
>> variable.
>> (!) DirectFB/Core: Could not initialize 'system' core!
>>     --> Initialization error!
>> Could not initialize SDL - exiting
>>
>> I'd try to start the system from X, but there doesn't seem to be any method
>> of doing that. Obviously there is a framebuffer somewhere, but the command
>> line qemu can't seem to find it.
>>     
>
> Your SDL may be built with no X support, if you're sure it supports X
> then try forcing it with SDL_VIDEODRIVER. The message above actually
> indicates there's no framebuffer.
>   

DISPLAY isn't set.  This often happens when you 'sudo su -'.  If you 
instead 'sudo su' or just 'sudo qemu ...' then DISPLAY will remain set 
and things will work as expected.

Regards,

Anthony Liguori

> Regards
>
>
>
>