From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU + -std-vga + XFree86
Date: Sun, 25 Mar 2007 19:41:23 -0500 [thread overview]
Message-ID: <460716B3.4060803@codemonkey.ws> (raw)
In-Reply-To: <9a158e2e0703251636p2209eed0u5e1b8f736343a8e6@mail.gmail.com>
Kyle Hubert wrote:
> Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
> having 1600x1200 working in the virtual machine, so I looked at using
> the -std-vga option with the "vesa" X driver.
You probably have to increase your hsync and vrefresh ranges.
Regards,
Anthony Liguori
> While initializing X, I get the following:
>
> (II) VESA(0): Primary V_BIOS segment is: 0xc000
> (II) VESA(0): VESA BIOS detected
> (II) VESA(0): VESA VBE Version 0.0
> (II) VESA(0): VESA VBE Total Mem: 0 kB
> (II) VESA(0): VESA VBE OEM: ^A
>
> The log continues on to say:
>
> (II) VESA(0): Total Memory: 0 64KB banks (0kB)
> (II) VESA(0): Generic Monitor: Using hsync range of 28.00-51.00 kHz
> (II) VESA(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
> (II) VESA(0): Not using mode "1600x1200" (no mode of this name)
> (II) VESA(0): Not using mode "1280x1024" (no mode of this name)
> (II) VESA(0): Not using mode "1024x768" (no mode of this name)
> (II) VESA(0): Not using mode "800x600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x480" (insufficient memory
> given virtual size)
>
> I'm not positive this is my problem, but it looks like it isn't
> reporting the vram size correctly, does this sound correct?
>
> Thanks for the time.
>
> -Kyle
>
>
>
next prev parent reply other threads:[~2007-03-26 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 23:36 [Qemu-devel] QEMU + -std-vga + XFree86 Kyle Hubert
2007-03-26 0:41 ` Anthony Liguori [this message]
2007-03-26 6:37 ` Christian MICHON
2007-03-26 7:12 ` Kyle Hubert
2007-03-26 7:16 ` Kyle Hubert
2007-03-26 7:40 ` Christian MICHON
2007-03-26 8:32 ` Kyle Hubert
2007-03-26 8:53 ` Christian MICHON
2007-03-26 9:22 ` Kyle Hubert
-- strict thread matches above, loose matches on Subject: below --
2007-03-26 0:44 Ben Taylor
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=460716B3.4060803@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@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).